BSP PERFORMANCE AND TESTING Sample Clauses

BSP PERFORMANCE AND TESTING. 7.2.1 Flat compilation flow There are two compilation flows for OpenCL designs. The first is the regular flow where the IP components such as memories, PCIe and IO connections are locked down in a fixed location. This guarantees that the OpenCL designs will work regardless of how low the compiled kernel clock frequency is. This ensures the critical components such as the PCIe and DDR memories always meet timing. For a flat flow, no components are locked down and therefore there is no guarantee that the critical components always meet timing. A flat flow has advantages in that extra functionality can be added to the BSP without a major rework to the BSP floor planning. Given that the OPERA BSP is to be continuously improved over the course of the project a flat flow will be used for initial OpenCL design and MICMAC port. Compilation of existing software using a flat flow have proven that critical components of the design still meet timing with a flat flow, if the PCIe is de-rated to Gen2. De-rating of the PCIe to Gen2 has no significant impact (see 7.2.4). Figure 17: Example flat build showing the base IP (PCIe, etc) in red (Arria 10 660-SOC) With the flat flow, there is no base region and the Altera tools can place the kernel logic amongst the board logic. So, whilst not all logic can be used, there are no floor planned regions where the kernel logic cannot be placed. This leads to a lower board resource usage than for a fixed floor planned BSP. The resource of the flat BSP is given below. FPGA resource type: FPGA Prototype Board Total Resource (10AS066H3F34E2SG) opera_ax066 Built with 16.1.1 ALMS FFs DSPs RAMs 251680 1006720 1687 2131 23483 (9.33%) 93932 (9.33%) 231 (10.84%) Table 10 : FPGA prototype BSP resource use
Sample 1
AutoNDA by SimpleDocs

Related to BSP PERFORMANCE AND TESTING

  • CONTRACTOR PERFORMANCE AUDIT The Contractor shall allow the Authorized User to assess Contractor’s performance by providing any materials requested in the Authorized User Agreement (e.g., page load times, response times, uptime, and fail over time). The Authorized User may perform this Contractor performance audit with a third party at its discretion, at the Authorized User’s expense. The Contractor shall perform an independent audit of its Data Centers, at least annually, at Contractor expense. The Contractor will provide a data owner facing audit report upon request by the Authorized User. The Contractor shall identify any confidential, trade secret, or proprietary information in accordance with Appendix B, Section 9(a), Confidential/Trade Secret Materials.

  • Acceptance/Performance Test 4.7.1 Prior to synchronization of the Power Project, the SPD shall be required to get the Project certified for the requisite acceptance/performance test as may be laid down by Central Electricity Authority or an agency identified by the central government to carry out testing and certification for the solar power projects.

  • PERFORMANCE OUTCOMES 8 A. CONTRACTOR shall achieve performance objectives, tracking and reporting Performance 9 Outcome Objective statistics in monthly programmatic reports, as appropriate. ADMINISTRATOR 10 recognizes that alterations may be necessary to the following services to meet the objectives, and,

  • Performance Testing 7.2.1 The Design-Builder shall direct and supervise the tests and, if necessary, the retests of the Plant using Design-Builder’s supervisory personnel and the Air Emissions Tester shall conduct the air emissions test, in each case, in accordance with the testing procedures set forth in Exhibit A (the “Performance Tests”), to demonstrate, at a minimum, compliance with the Performance Guarantee Criteria. Owner is responsible for obtaining Air Emissions Tester and for ensuring Air Emissions Tester’s timely performance. Design-Builder shall cooperate with the Air Emissions Tester to facilitate performance of all air emissions tests. Design-Builder shall not be held responsible for the actions of Owner’s employees and third parties involved in the Performance Testing, including but not limited to Air Emissions Tester.

  • Ongoing Performance Measures The Department intends to use performance-reporting tools in order to measure the performance of Contractor(s). These tools will include the Contractor Performance Survey (Exhibit H), to be completed by Customers on a quarterly basis. Such measures will allow the Department to better track Vendor performance through the term of the Contract(s) and ensure that Contractor(s) consistently provide quality services to the State and its Customers. The Department reserves the right to modify the Contractor Performance Survey document and introduce additional performance-reporting tools as they are developed, including online tools (e.g. tools within MFMP or on the Department's website).

  • Contractor Performance Evaluations The Contract Administrator will evaluate Contractor’s performance as often as the Contract Administrator deems necessary throughout the term of the contract. This evaluation will be based on criteria including the quality of goods or services, the timeliness of performance, and adherence to applicable laws, including prevailing wage and living wage. City will provide Contractors who receive an unsatisfactory rating with a copy of the evaluation and an opportunity to respond. City may consider final evaluations, including Contractor’s response, in evaluating future proposals and bids for contract award.

  • Covenants of Performance Measurement No interference. Registry Operator shall not interfere with measurement Probes, including any form of preferential treatment of the requests for the monitored services. Registry Operator shall respond to the measurement tests described in this Specification as it would to any other request from an Internet user (for DNS and RDDS) or registrar (for EPP). ICANN testing registrar. Registry Operator agrees that ICANN will have a testing registrar used for purposes of measuring the SLRs described above. Registry Operator agrees to not provide any differentiated treatment for the testing registrar other than no billing of the transactions. ICANN shall not use the registrar for registering domain names (or other registry objects) for itself or others, except for the purposes of verifying contractual compliance with the conditions described in this Agreement. PUBLIC INTEREST COMMITMENTS Registry Operator will use only ICANN accredited registrars that are party to the Registrar Accreditation Agreement approved by the ICANN Board of Directors on 27 June 2013 in registering domain names. A list of such registrars shall be maintained by ICANN on ICANN’s website. (Intentionally omitted. Registry Operator has not included commitments, statements of intent or business plans provided for in its application to ICANN for the TLD.) Registry Operator agrees to perform the following specific public interest commitments, which commitments shall be enforceable by ICANN and through the Public Interest Commitment Dispute Resolution Process established by ICANN (posted at xxxx://xxx.xxxxx.xxx/en/resources/registries/picdrp), which may be revised in immaterial respects by ICANN from time to time (the “PICDRP”). Registry Operator shall comply with the PICDRP. Registry Operator agrees to implement and adhere to any remedies ICANN imposes (which may include any reasonable remedy, including for the avoidance of doubt, the termination of the Registry Agreement pursuant to Section 4.3(e) of the Agreement) following a determination by any PICDRP panel and to be bound by any such determination. Registry Operator will include a provision in its Registry-Registrar Agreement that requires Registrars to include in their Registration Agreements a provision prohibiting Registered Name Holders from distributing malware, abusively operating botnets, phishing, piracy, trademark or copyright infringement, fraudulent or deceptive practices, counterfeiting or otherwise engaging in activity contrary to applicable law, and providing (consistent with applicable law and any related procedures) consequences for such activities including suspension of the domain name. Registry Operator will periodically conduct a technical analysis to assess whether domains in the TLD are being used to perpetrate security threats, such as pharming, phishing, malware, and botnets. Registry Operator will maintain statistical reports on the number of security threats identified and the actions taken as a result of the periodic security checks. Registry Operator will maintain these reports for the term of the Agreement unless a shorter period is required by law or approved by ICANN, and will provide them to ICANN upon request. Registry Operator will operate the TLD in a transparent manner consistent with general principles of openness and non-discrimination by establishing, publishing and adhering to clear registration policies.

  • Criteria for Performance Assessment A. A teacher’s performance shall be assessed based on the criteria set forth in the evaluation instrument, Appendix D.

  • Annual Performance Evaluation On either a fiscal year or calendar year basis, (consistently applied from year to year), the Bank shall conduct an annual evaluation of Executive’s performance. The annual performance evaluation proceedings shall be included in the minutes of the Board meeting that next follows such annual performance review.

  • Key Performance Indicators 10.1 The Supplier shall at all times during the Framework Period comply with the Key Performance Indicators and achieve the KPI Targets set out in Part B of Framework Schedule 2 (Goods and/or Services and Key Performance Indicators).

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