Planned demonstrators Sample Clauses

Planned demonstrators. After the first 12 month (April 2015) the first prototype will demonstrate a working HW platform to be used for FPGA based implementation of Video Algorithms. In addition the first implementations of video algorithms for the different use cases will be available. At m33 (Dec 2016) the design process shall be complete and integrate the algorithmic work together with the design process. The purpose of the m33 demonstrator is to show that the example algorithms can be deployed to the proposed platform. At month 20 (Nov 2015) the first prototype will demonstrate the capabilities of the middleware to xxxxxx the use-case “Passenger Tracking” by monitoring the system. The system will consist of a limited number of processing and sensor units. The middleware will be able to cope with some dynamic changes. The prototype will be demonstrated in the first EMC2 workshop held in or after month 20.
Sample 1
AutoNDA by SimpleDocs
Planned demonstrators. The healthcare demonstration applies the EMC² technology in several healthcare situations involving medical images. The healthcare applications, served by the demonstrator, cover medical diagnostic and intervention support systems. In interventional situations real-time processing is crucial. For efficiency reasons we need to be able to host several applications, with diverse latency and performance requirements on a single chip or board solution. This means co-location of real-time and non-real-time processing on a single chip/board. The algorithms that will run on the EMC² many-core execution platform involve massive image processing of different kinds (like noise reduction, image segmentation, image fusion etc.), but the background processing of the same piece of hardware deals amongst others with user interface, workflow support, decision support, administrative tasks, and (image) data storage and transfer. To ease portability, the demonstrators are built using domain-specific abstractions of the image processing algorithms.
Sample 1
Planned demonstrators. A single demonstrator will illustrate all the results obtained in the current task. The demonstrator will describe the development of the mentioned application with the support of an open tool chain addressing tool independence and multi core design space exploration.
Sample 1
Planned demonstrators. The planned demonstrators intend to visualize and showcase the research results gained in this use case. In particular three main topics are addressed:  Safety concept for multi-core usage in the railway domain  Novel Programming Paradigms  Virtualization with PikeOS
Sample 1

Related to Planned demonstrators

  • Service Reports GRANTEE shall submit service delivery reports, programmatic performance reports and other reports to the extent requested by OAG, in a format and on a timely basis, as established by the OAG. XXXXXXX will submit other reports as requested by the OAG.

  • Program Narrative All restricted xxxxxx courses which are taught for the purpose of qualifying an individual for restricted xxxxxx license to practice barbering shall consist of a minimum of 1200 hours of training to prepare each restricted xxxxxx to service their communities.

  • Ongoing Trunk Forecast Requirements Where the Parties have already established interconnection in a LATA, Onvoy shall provide a new or revised traffic forecast that complies with the Frontier Interconnection Trunking Forecast Guide when Xxxxx develops plans or becomes aware of information that will materially affect the Parties’ interconnection in that LATA. Instances that require a new or revised forecast include, but are not limited to: (a) Onvoy plans to deploy a new switch; (b) Onvoy plans to implement a new POI or network architecture; (c) Onvoy plans to rearrange its network; (d) Onvoy plans to convert a One-Way Interconnection Trunk group to a Two-Way Interconnection Trunk group; (e) Onvoy plans to convert a Two-Way Interconnection Trunk group to a One-Way Interconnection Trunk group; or (f) Onvoy expects a significant change in interconnection traffic volume. In addition, upon request by either Party, the Parties shall meet to: (i) review traffic and usage data on End Office and Tandem Interconnection Trunk groups and (ii) determine whether the Parties should establish new Interconnection Trunk groups, augment existing Interconnection Trunk groups, or disconnect existing Interconnection Trunks.

  • Agreement Exceptions/Deviations Explanation If the proposing Vendor desires to deviate form the Vendor Agreement language, all such deviations must be listed on this attribute, with complete and detailed conditions and information included. TIPS will consider any deviations in its proposal award decisions, and TIPS reserves the right to accept or reject any proposal based upon any deviations indicated below. In the absence of any deviation entry on this attribute, the proposer assures TIPS of their full compliance with the Vendor Agreement. No response

  • Performance Reports None Specified

  • Justification and Anticipated Results The Privacy Act requires that each matching agreement specify the justification for the program and the anticipated results, including a specific estimate of any savings. 5 U.S.C. § 552a(o)(1)(B).

  • System Upgrade Facilities and System Deliverability Upgrades Connecting Transmission Owner shall design, procure, construct, install, and own the System Upgrade Facilities and System Deliverability Upgrades described in Appendix A hereto. The responsibility of the Developer for costs related to System Upgrade Facilities and System Deliverability Upgrades shall be determined in accordance with the provisions of Attachment S to the NYISO OATT.

  • Maintenance and Warranty Service Reports The report shall include the name of the Authorized User and all of the information in Section 2.24.1 and be submitted electronically in Microsoft Excel 2010 or newer version unprotected, via e-mail to the attention of the OGS Contract Administrator.

  • Loop Testing/Trouble Reporting 2.1.6.1 Think 12 will be responsible for testing and isolating troubles on the Loops. Think 12 must test and isolate trouble to the BellSouth portion of a designed/non- designed unbundled Loop (e.g., UVL-SL2, UCL-D, UVL-SL1, UCL-ND, etc.) before reporting repair to the UNE Customer Wholesale Interconnection Network Services (CWINS) Center. Upon request from BellSouth at the time of the trouble report, Think 12 will be required to provide the results of the Think 12 test which indicate a problem on the BellSouth provided Loop.

  • Technical Standards Applicable to a Wind Generating Plant i. Low Voltage Ride-Through (LVRT) Capability A wind generating plant shall be able to remain online during voltage disturbances up to the time periods and associated voltage levels set forth in the standard below. The LVRT standard provides for a transition period standard and a post-transition period standard.

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