List of figures
Figure | Description |
---|---|
Levels of scenario abstraction (Source: [24]) |
|
From abstract to concrete |
|
From concrete to abstract |
|
An illustration of a set of traces accepted by an ASAM OpenSCENARIO model |
|
An illustration of how the set of traces accepted by a scenario is a subset of the composition of the traces accepted by the scenario invocations, which themselves are subsets of the traces accepted by their type scenario. |
|
Different behavior invocation overlappings allowed by overlap kinds equal, start, end, initial, and final |
|
Different behavior invocation overlappings allowed by overlap kinds inside, full, and any |
|
An illustration of minimum and maximum start-to-start offsets |
|
An illustration of an ASAM OpenSCENARIO scenario execution state showing scenario instances and field bindings. |
|
Entity overview |
|
Yaw, pitch, and roll angle in an ISO 8855:2011 compliant coordinate system |
|
Route-based s/t-coordinate system with origin at the beginning of the route |
|
Vehicle coordinate system |
|
Entity overview |
|
Entity overview |
|
Entity overview |
|
Entity overview |
|
Basic junction |
|
Junction routes |
|
A typical crossing |
|
A crossing |
|
Entity overview |
|
Actions that prioritize exact reproduction |
|
Actions that prioritize respecting physical movement constraints |
|
A remain_stationary action |
|
Crossing with line from free space points |
|
Picture of crossing with specified start_angle |
|
Understanding product testing |
|
Recommending scenarios and parameter |
|
Understanding AV/ADAS developer scenarios |
|
Specifying regulation scenarios |
|
Tracing back requirements |
|
Sharing scenarios with other companies |
|
Scenario sharing with auditors and regulators |
|
Sharing scenarios with customers |
|
Including traffic models and agents |
|
Describing real world with scenarios |
|
Creating self-checking scenarios |
|
Creating abstract scenarios for documentation purposes |
|
Re-utilizing scenarios for research |
|
Deriving a simulation scenario from findings of a SOTIF analysis |
|
Deriving new hazardous events, system insufficiencies or triggering conditions for SOTIF from findings during a simulation run |
|
Replaying different variants of a critical scenario observed on the road in simulation, to derive new SOTIF insights from it. |
|
Evaluating of residual risk because of unknown scenario |
|
Integrating tools from other vendors |
|
Processing and comparing results |
|
Creating natural language scenarios without technical details |
|
Tracing back verification |
|
Workflow for cross-company scenario testing |
|
Creating platform independent scenarios |
|
Tracing back requirements |
|
Specifying a driving mission |
|
Accomplishing driving missions |
|
Converting abstract test descriptions into scenarios |
|
Reuse/combine of scenario elements to avoid copy-paste |
|
Specifying test aspects |
|
Converting between abstraction levels |
|
Using real-world data for scenarios |
|
Performing automated scenario execution |
|
Using different tool chains |
|
Converting abstract to concrete scenarios |
|
Running tests in different environments |
|
Describing test track scenarios |
|
Measuring the verification progress |
|
Re-using constructs, artifacts and libraries |
|
Migrating from OpenSCENARIO 1.x to OpenSCENARIO 2.0 |
|
Migrating from OpenSCENARIO 1.x to OpenSCENARIO 2.0 |
|
Executing simulations randomly |