Background and Implementation Sample Clauses

Background and Implementation. Koç et al. [11] proposed Coarsely Integrated Operate Operand Scanning (CIOS) and Finely Integrated Operate Operand Scanning (FIOS) algorithms as an optimization for Xxxxxxxxxx multiplication targeting word size processors or multiplication units. The CIOS algorithm, as shown in Algorithm 1 computes one entire partial product, lines 2– 6, before performing a reduction, lines 8–12. FIOS on the other hand, computes the multiplication of a word of each input, lines 2 and 6, and then proceeds with the reduction, lines 4, 7 and 9. While the CIOS algorithm operates directly on partial products, the iterative word-based structure of the FIOS algorithm allows for a design with two parallel units, one doing the multiplication, line 6, and the other one the reduction, line 7. In the proposed implementations, the IGLOO 2 FPGA family from Microsemi is targeted. These FPGAs include Algorithm 1 CIOS Xxxxxxxxxx multiplication algo- rithm [11] ≤ Require: a, b 2n, r = 2()()log2 (n)+2¶/word size)¶·word size), − [ | n′ = n—1 (mod r), w = 2word size, l = log2(r/w) · Ensure: o = a b/r (mod n) ←
AutoNDA by SimpleDocs
Background and Implementation. Koç et al. [11] proposed Coarsely Integrated Operate Operand Scanning (CIOS) and Finely Integrated Operate Operand Scanning (FIOS) algorithms as an optimization for Xxxxxxxxxx multiplication targeting word size processors or multiplication units. The CIOS algorithm, as shown in Algorithm 1 computes one entire partial product, lines 2– 6, before performing a reduction, lines 8–12. FIOS on the other hand, computes the multiplication of a word of each input, lines 2 and 6, and then proceeds with the reduction, lines 4, 7 and 9. While the CIOS algorithm operates directly on partial products, the iterative word-based structure of the FIOS algorithm allows for a design with two parallel units, one doing the multiplication, line 6, and the other one the reduction, line 7. In the proposed implementations, the IGLOO 2 FPGA family from Microsemi is targeted. These FPGAs include Algorithm 1 CIOS Xxxxxxxxxx multiplication algo- rithm [11] ≤

Related to Background and Implementation

  • BACKGROUND AND INTRODUCTION The Federal-aid Highway Program (FAHP) is a federally-assisted program of State-selected projects. The Federal Highway Administration (FHWA) and the State Departments of Transportation have long worked as partners to deliver the FAHP in accordance with Federal requirements. In enacting 23 U.S.C. 106(c), as amended, Congress recognized the need to give the States more authority to carry out project responsibilities traditionally handled by FHWA. Congress also recognized the importance of a risk-based approach to FHWA oversight of the FAHP, establishing requirements in 23 U.S.C. 106(g). This Stewardship and Oversight (S&O) Agreement sets forth the agreement between the FHWA and the State of Florida Department of Transportation (FDOT) on the roles and responsibilities of the FHWA and the State DOT with respect to Title 23 project approvals and related responsibilities, and FAHP oversight activities. The scope of FHWA responsibilities, and the legal authority for State DOT assumption of FHWA responsibilities, developed over time. The U.S. Secretary of Transportation delegated responsibility to the Administrator of the FHWA for the FAHP under Title 23 of the United States Code, and associated laws. (49 CFR 1.84 and 1.85) The following legislation further outlines FHWA’s responsibilities: • Intermodal Surface Transportation Efficiency Act (ISTEA) of 1991; • Transportation Equity Act for the 21st Century (TEA-21) of 1998; • Safe, Accountable, Flexible, Efficient Transportation Equity Act: A Legacy for Users (SAFETEA-LU) of 2005; and • Moving Ahead for Progress in the 21st Century Act (MAP-21) of 2012 (P.L. 112-141). The FHWA may not assign or delegate its decision-making authority to a State Department of Transportation unless authorized by law. Xxxxxxx 000 xx Xxxxx 00, Xxxxxx Xxxxxx Code (Section 106), authorizes the State to assume specific project approvals. For projects that receive funding under Title 23, U.S.C., and are on the National Highway System (NHS) including projects on the Interstate System, the State may assume the responsibilities of the Secretary of the U.S. Department of Transportation under Title 23 for design, plans, specifications, estimates, contract awards, and inspections with respect to the projects unless the Secretary determines that the assumption is not appropriate. (23 U.S.C. 106(c)(1)) For projects under Title 23, U.S.C. that are not on the NHS, the State shall assume the responsibilities for design, plans, specifications, estimates, contract awards, and inspections unless the State determines that such assumption is not appropriate. (23 U.S.C. 106(c)(2)) For all other project activities which do not fall within the specific project approvals listed in Section 106 or are not otherwise authorized by law, the FHWA may authorize a State DOT to perform work needed to reach the FHWA decision point, or to implement FHWA’s decision. However such decisions themselves are reserved to FHWA. The authority given to the State DOT under Section 106(c)(1) and (2) is limited to specific project approvals listed herein. Nothing listed herein is intended to include assumption of FHWA’s decision-making authority regarding Title 23, U.S.C. eligibility or Federal-aid participation determinations. The FHWA always must make the final eligibility and participation decisions for the Federal-aid Highway Program. Section 106(c)(3) requires FHWA and the State DOT to enter into an agreement relating to the extent to which the State DOT assumes project responsibilities. This Stewardship and Oversight Agreement (S&O Agreement), includes information on specific project approvals and related responsibilities, and provides the requirements for FHWA oversight of the FAHP (Oversight Program), as required by 23 U.S.C. 106(g).

  • Project Background 6.1.1. Brief description of Contracting Agency’s project background and/or situation leading to this Project

  • COOPERATION IN IMPLEMENTATION On demand of the other Spouse and without undue delay or expense, each Spouse shall execute, acknowledge, or deliver any instrument, furnish any information, or perform any other acts reasonably necessary to carry out the provisions of this Agreement. If a Spouse fails to execute any document as required by this provision, the court may appoint the court clerk or his or her authorized designee to execute the document on that Xxxxxx’s behalf.

  • PURPOSE AND IMPLEMENTATION This Umbrella Agreement (hereinafter referred to as the "Agreement" or "Umbrella Agreement") shall be for the purpose of collaborative research, development, and testing opportunities on various topics of mutual interest to enable advanced understanding of aeronautics, science, and space systems research and development and to provide workforce development in Science, Technology, Engineering, and Mathematics (STEM) while furthering NASA’s research and development goals. The Parties shall execute one (1) Annex Agreement (hereinafter referred to as the "Annex") concurrently with this Umbrella Agreement. The Parties may execute subsequent Annexes under this Umbrella Agreement consistent with the purpose and terms of this Umbrella Agreement. This Umbrella Agreement shall govern all Annexes executed hereunder; no Annex shall amend this Umbrella Agreement. Each Annex will detail the specific purpose of the proposed activity, responsibilities, schedule and milestones, and any personnel, property, or facilities to be utilized under the task. This Umbrella Agreement takes precedence over any Annexes. In the event of a conflict between the Umbrella Agreement and any Annex concerning the meaning of its provisions, and the rights, obligations and remedies of the Parties, the Umbrella Agreement is controlling.

  • Access Rights for implementation Access Rights to Results and Background Needed for the performance of the own work of a Party under the Project shall be granted on a royalty-free basis, unless otherwise agreed for Background in Attachment 1.

  • Joint Network Implementation and Grooming Process Upon request of either Party, the Parties shall jointly develop an implementation and grooming process (the “Joint Grooming Process” or “Joint Process”) which may define and detail, inter alia:

  • Background and/or Criminal History Investigation Prior to commencement of any services, background and/or criminal history investigation of the Vendor’s employees and subcontractors who will be providing services to the Customer under the Contract may be performed by the Customer. Should any employee or subcontractor of the Vendor who will be providing services to the Customer under the Contract not be acceptable to the Customer as a result of the background and/or criminal history check, then Customer may immediately terminate its Purchase Order and related Service Agreement or request replacement of the employee or subcontractor in question.

  • Background Investigations OSC policy requires that background investigations be conducted on Contractor Staff who will have access to OSC’s IT systems, access to OSC confidential information/data, or routine access to any OSC facility. For purposes of this policy, “routine access” is defined as access to an OSC facility for five consecutive business days or 10 business days over the annual term of the engagement. Accordingly, with the signing of this Agreement, the Contractor certifies that it has or will conduct a background investigation on Staff to whom the policy applies within the 12 months prior to the Staff commencing Services under this Agreement. The Contractor agrees to undertake a background investigation of any new/replacement Staff during the term of the Agreement. At a minimum, background investigations shall include a review/evaluation of the following: • identity verification, including Social Security Number search; • employment eligibility, including verification of U.S. citizenship or legal immigration status where appropriate; • criminal history/court records (Federal, State and local for the past five years); • work experience/history for the past five years; • pertinent skills, qualifications, and education/professional credentials; and • references. The Contractor must obtain the consent of its Staff to allow OSC, upon request: (i) to review the background investigation records, including all supporting documentation, and (ii) to conduct its own background investigation. Only Staff who have passed the background investigation, and provided such consent shall be assigned to provide Services to OSC under this Agreement. During the term of the Agreement, and in accordance with Appendix A (Section 10, Records), the Contractor must maintain records related to the background investigations performed.

  • Access Toll Connecting Trunk Group Architecture 9.2.1 If CBB chooses to subtend a Verizon access Tandem, CBB’s NPA/NXX must be assigned by CBB to subtend the same Verizon access Tandem that a Verizon NPA/NXX serving the same Rate Center Area subtends as identified in the LERG.

  • Background Data The Disclosing Party's Background Data, if any, will be identified in a separate technical document.

Time is Money Join Law Insider Premium to draft better contracts faster.