Euro NCAP provides descriptions of collision scenarios to test active safety systems of vehicles. Prior to conducting these tests on a test track, virtual test drives can provide valuable insights during the development of new driver assistance systems. Therefore, the scenarios must be described in a machine-readable format. ASAM OpenSCENARIO XML and ASAM OpenDRIVE are open standards defining such formats. Scenario descriptions based on these standards serve as input to standard-compliant simulators like Vector DYNA4. As the Euro NCAP scenarios are widely used, Vector decided to contribute the implementation of these scenarios using the ASAM standards. The goal is to foster the community trend for shift left testing with virtual test drives and ultimately make roads safer.
The following protocols have served as a basis for the implementation of the scenarios:
ASAM OpenSCENARIO XML defines an XML-based file format for the description of the dynamic part of scenarios like the movement of traffic participants or environmental conditions such as weather. Using parameters instead of concrete values, ASAM OpenSCENARIO XML enables the automatic variation of scenarios, a vital feature for the modelling of the Euro NCAP scenarios as similar scenarios are performed at different speeds etc. Scenarios within a parameter space are often referred to as 'logical scenarios' in contrast to 'concrete scenarios' that use a specific set of concrete parameter values.
ASAM OpenDRIVE defines an XML-based file format for the description of the static part of scenarios including the road network and nearby objects such as traffic signals or buildings. OpenDRIVE files are referenced by the OpenSCENARIO files. Although the road networks used for the Euro NCAP scenarios are rather simple, they have been auto-generated using the Python 'scenariogeneration' package for better maintainability.
You only need to clone the repository to get the OpenSCENARIO XML and OpenDRIVE files and essentially you're ready to start simulating with your preferred standard-compliant simulator. However, the following notes on the usage should be considered:
| NCAP Scenario | NCAP Protocol | XOSC Base Scenario |
|---|---|---|
| Car-to-Pedestrian Farside Adult 50% (CPFA-50) | AEB/LSS VRU systems v4.5.1 | CPNA-25 |
| Car-to-Pedestrian Nearside Adult 25% (CPNA-25) | AEB/LSS VRU systems v4.5.1 | CPNA-25 |
| Car-to-Pedestrian Nearside Adult 75% (CPNA-75) | AEB/LSS VRU systems v4.5.1 | CPNA-25 |
| Car-to-Pedestrian Nearside Child Obstructed 50% (CPNCO-50) | AEB/LSS VRU systems v4.5.1 | CPNCO-50 |
| Car-to-Pedestrian Longitudinal Adult 25% (CPLA-25) | AEB/LSS VRU systems v4.5.1 | CBLA-50 |
| Car-to-Pedestrian Longitudinal Adult 50% (CPLA-50) | AEB/LSS VRU systems v4.5.1 | CBLA-50 |
| Car-to-Pedestrian Turning Adult 50% (CPTA-50) | AEB/LSS VRU systems v4.5.1 | CPTA-50 |
| Car-to-Bicyclist Nearside Adult 50% (CBNA-50) | AEB/LSS VRU systems v4.5.1 | CBNA-50 |
| Car-to-Bicyclist Nearside Adult Obstructed 50% (CBNAO-50) | AEB/LSS VRU systems v4.5.1 | CBNAO-50 |
| Car-to-Bicyclist Farside Adult 50% (CBFA-50) | AEB/LSS VRU systems v4.5.1 | CBFA-50 |
| Car-to-Bicyclist Longitudinal Adult 25% (CBLA-25) | AEB/LSS VRU systems v4.5.1 | CBLA-50 |
| Car-to-Bicyclist Longitudinal Adult 50% (CBLA-50) | AEB/LSS VRU systems v4.5.1 | CBLA-50 |
| Car-to-Car Rear Stationary (CCRs) | AEB Car-to-Car systems v4.3.1 | CCRs |
| Car-to-Car Rear Moving (CCRm) | AEB Car-to-Car systems v4.3.1 | CCRs |
| Car-to-Car Rear Braking (CCRb) | AEB Car-to-Car systems v4.3.1 | CCRs |
If you want to refer to this work in publications, please cite "Automated NCAP tests with ASAM OpenSCENARIO"; Jakob Kaths, Benedikt Schott, Hannah Bernauer, Markus Pielmeier, André Pinnel. AutoTest Technical Conference, 2024 [In Press].
The OpenSCENARIO XML and OpenDRIVE files have been licensed under MPL-2.0 and are hereby made publicly available.
The scenarios have been implemented by Vector with great care based on the textual descriptions in the Euro NCAP protocols to our best knowledge. However, Vector is not liable for the correctness and completeness of the OpenSCENARIO XML and OpenDRIVE files.
The XSD schemas of OpenSCENARIO XML and OpenDRIVE are under the license of ASAM, which can be found within the respective standard document.
At the moment, we do not accept external contributions until we have established a contribution process, see CONTRIBUTING.md for further details.