90 likes | 186 Views
SafeSpot WP2.5. Test & Validation. Objectives of WP2.5. Overall objective : evaluate actual performance and validate them against system specification and requirement. Test and validate the performance of systems for the identification of safety-related events
E N D
SafeSpot WP2.5 Test & Validation
Objectives of WP2.5 • Overall objective : evaluate actual performance and validate them against system specification and requirement. • Test and validate the performance of systems for the identification of safety-related events • Test and validate the integration of roadside basic components with applications (SP4, SP5) and equipment • Test and validate the robustness and reliability of detection models in real operating conditions • Test and validate vehicle-infrastructure co-operation for mutual benefit in sensing hazardous events • Collect and document guidelines and best practice for infrastructure based sensing
Issues • Availability of components ? • Availability of applications ? (link with SP4-5) • Integration : some unknowns : Risk ? components interoperability, required time for integration ?
Task 2.5.1 Validation criteria • Methodologies for test and validation, • Possible test tracks and/or a very comprehensive open road network, • Different kinds of test: friendly vehicles or instrumented vehicles, simulators, test beds which allows a high level of reproducibility, calibration areas etc. • The kind of measurements required, • Accurate and synchronized data logging means for any kind of sensors and video camera,
T2.5.2 Test and validation • Innovative method of detection • False alarm and non-detection rate in different context • Multi-source data fusion • Reliability comparison mono versus multi source • Safety related traffic modeling and Incident response systems • Latency time between event and notification to driver • Swarming behavior and driver persuasion technologies • Evaluation on numeric or driving simulator : impact on traffic and on driver behavior
Tasks and partners involvement NB: BME is interesting to participate to the validation phase, even if they do not have MM in WP2.5. Total effort : 48.5 MM
Planning Important milestone Very short time !!!
Proposed action plan • Methodology • Dec 2007 Inventory of status and planned availability of components and application (LCPC) • Jan 2008 Definition of overall validation procedures : laboratory based, simulator based, test site based (ALL) • Fev-Mar 2008 Detailed methodology (ALL) : • Component level : procedures, performance indicator (responsible for each module shall make proposal for component evaluation) • System level (component integration, data fusion) : scenarios, indicators (evaluation based upon consensus toward all partners) • Application level (link with SP4 and SP5) : scenarios, indicators • Test means requirements : infra, vehicle, synchronization (data logger) • Organization : Who do what ? role of each partners. • Test and validation • Mar-June 2008 Test means construction • Jun-Sep 2008 Test execution (Milestone 2.4.1 !!!!!) • Analysis and evaluation results • Sep-Dec 2008 Analysis and evaluation results
Deliverables • D2.5.1 Plan for Testing and Validation of INFRASENS components (M27) • D2.5.1 Final Report : Guidelines and best practice for infrastructure sensing (M36)