Driving Scenarios for Analysis and Testing

Find the Scenarios You Need

Search and analyze recorded traffic, then retrieve concrete scenarios from scenario.database. If no suitable scenario is available, create one with scenario.generator. Use scenario.quality.checker whenever you want to assess a scenario.

Scenarios, Data & Methods

One Consistent Ecosystem for Working with Scenarios

scenario.center combines access to real-world scenarios with data workflows, concepts, optional scenario creation and independent quality assessment.

database Find & retrieve

scenario.database

Find real-world scenarios and retrieve concrete scenario files.

Search recorded traffic, analyze and compare scenario distributions, select relevant scenarios and export them for your application.

  • Real-world scenario data
  • Search and analysis
  • Concrete OpenSCENARIO / OpenDRIVE files
Open the database arrow_outward
Create on demand

scenario.generator

Create a scenario when the database does not contain a suitable one.

Create prototype highway scenarios through a graphical user interface and generate matching OpenSCENARIO and OpenDRIVE files.

  • Interactive graphical interface
  • Configuration-based creation
  • OpenSCENARIO + OpenDRIVE
Open the generator arrow_outward
Assess

scenario.quality.checker

Assess structural, consistency and motion properties of scenarios.

Validate individual OpenSCENARIO files or entire batches and create repeatable PDF and CSV quality reports.

  • Schema and structure validation
  • Consistency and dynamics checks
  • PDF and CSV reports
Explore the quality checker arrow_outward
The Database Workflow

From Observations to Simulation-Ready Scenarios

Process steps
account_tree
Workflow overview

Our Way of Abstracting Reality

  • use our or your data
  • automatic processing
  • analyze and compare on the dashboard
  • search easily for complex combinations
  • get concrete OpenSCENARIO/DRIVE files
01

Input

  • automatic processing
  • private data or on-premise solutions
  • data compatibilitity through omega-prime
  • request any LevelXData dataset
  • LevelXData available (inD dataset)
  • converters for Lanelet2, ASAM OpenDRIVE, …

Already running with

bar_chart 7.538 Envelopes
directions_car 602 Driven km
hourglass_top 84.702 Elapsed s
02

Analysis

  • compare number of scenarios
  • get scenario parameter distribution
  • get a sample out of a logical scenario
  • compare data sources
03

Selection

  • search for relevant scenarios
  • get concrete scenarios from distribution
  • visualize scenario
04

Simulation

  • sampled from logical scenarios
  • behavior encoded in actions
  • get concrete OpenSCENARIO and OpenDRIVE files
  • compatible with ESMINI
  • CARLA OpenX enhancements under development
  • experience in Highly Dynamic Driving Simulator
The Scenario Concept

Concepts

info About the Concepts

For efficient structuring, storing and handling, an underlying scenario concept is developed for the database. It follows the categoriation of the 6 layer model and describes scenarios relatively to an ego road user. Thereby, scenarios are described and modeled on different abstraction layers to suit the users accordingly to its use case. A scenario is thereby defined as a sequence of scenes which can include actions and triggers and has an assigned ego road user. A scenario has a duration of typically 10 seconds and includes e.g. an intersection, a roundabout or a usual street.

layers Levels of Abstraction

For systematic description and easy usage, scenarios are described on different abstraction layers.

  • Functional/ abstract scenarios: On the highest level scenarios are described verbally for easy searches.
  • Logical scenario classes: Derived from abstract scenarios, logical scenario classes serves as a blueprint for parameters, attributes and relations to detail the abstract scenario and to generate concrete scenarios.
  • Logical scenario instances: Filled with actual data, distributions within a logical scenario class are modeled.
  • Concrete scenarios: Sampling logical scenario classes, concrete scenarios arise and can be used for simulations in OpenX format.

tune Attributes and Parameters

Scenarios are described by attributes and parameters for optimized seach and generation.

  • Attributes are used to describe scenarios comprehensively including positioning, timetoX metrics (e.g. THW, TTC, PET, timegap), occlusion, events and many more. So, for scenario can be searched via multiple attributes according to the actual use case. So, attributes aim to make every important aspect of a scenario searchable.
  • Parameters are dedicated to describe a scenario for generation. Inspite of attributes, parameters are thereby distinct or relations a re made explicit to prevent meaningless constellations and parametrizations. Thereby, different parametrizations are possible to describe the same scenario according to the actual needs.

hub Base and Focus Scenarios

How much complexity is needed? We describe all traffic relations between ego and object in any structured environment in less than 300 base scenarios. Easy to search - easy to generate. Thereby, those scenarios are build on a comprehensive ontology, so that scenarios used are derived systematically from given concepts. To allow for more complexity, combinations of those are called focus scenarios and can be used for more complex modeling. Within focus scenarios, multiple base scenarios are combined sequentially, in parallel or are adapted from the original base scenario to serve the dedicated use case.

replay Replay and Advanced Replay to Sim

Next to parametrizations of scenarios which abstract the reality, highest accuracy to simulate scenarios is done in a seperate branch without parameters for abstraction with replays of real-world data. Thereby, all components behave as they did in real-world. To still account for flexibility of scenarios according to potential ego behaviors, an advanced replay to sim is developed. This accounts for changes and adapts it to improve the realisticness of the new situation in OpenX standard.

verified Coverage and Completeness

How many scenarios are enough for sufficient testing? And is a proper set of scenarios chosen? For this, a method for proving the completeness of the scenario concept is used and applied to our scenario concept. Furthermore, coverage based on real-world data in the database can be approximated based on the limitations of input data.

menu_book References

Our scenario concept was developed and aligned in the safety assurance research project VVMethods. Learn more in our publications:

Who We Are

The Team

Christoph Glasmacher

Christoph Glasmacher

Research Scientist at ika

Janina Fichtner

Janina Fichtner

Research Scientist at ika

Sven Tarlowski

Sven Tarlowski

Research Scientist at ika

Dr.-Ing. Timo Woopen

Dr.-Ing. Timo Woopen

Manager Research Area Vehicle Intelligence & Automated Driving at ika

Univ.-Prof. Dr.-Ing. Lutz Eckstein

Univ.-Prof. Dr.-Ing. Lutz Eckstein

Director of the Institute for Automotive Engineering (ika) & President of VDI

Get In Touch

Contact