Tab Environment Simulation¶
For the testing of complex driver assistance systems and autonomous driving, new requirements arise for test methodologies and test tools. Thereby the importance of the simulation of the vehicle environment continues to increase. With environment simulation tools the environment can be modeled and used within tests.
The environment usually consists of:
the route (road geometry, road surface, road signs, traffic lights, trees,…)
the involved actors (ego vehicle, other vehicles, pedestrians, etc.)
the concrete actions or manoeuvres of the actors (e.g. a cutin scenario)
These three components are modeled in all environment simulation tools. To facilitate the use of the different environment simulation tools, there is an uniform concept within ecu.test for working with environmental simulations. This is explained below.
The following tool connections currently support the uniform concept:
Further supported environment simulation tools, which use own concepts:
Basic Concept¶
The environment describes the context of the test case. In this simulation context, the test case gets executed. The context is also called a scenario.
A list of all scenarios can be found in the tab Environment simulation. In order for the context to become active, you have to load a scenario using the test step Load element. Once you have loaded a scenario, you can test it using context-specific test steps such as Start simulation.
Furthermore, parameters and signals can be found in the tree under a scenario.
Parameters are set before simulation start and influence the course of the scenario.
Signals allow access to the model quantities of the scenario.
The corresponding test steps such as “read/write signals” and “read/write parameters” now refer to the currently loaded scenario. This means, for example, that the test step “Read signal” accesses a signal from the currently loaded scenario. Without the previous test step Load element these test steps are invalid.
The context-specific test steps contain a placeholder in the mapping path for the context-specific part. The placeholder is resolved at runtime by the loaded context. The placeholder makes it possible to perform the test steps in several packages and reuse them across scenarios, so you can copy them easily.
Test case creation¶
Ideally, the test case should be created with an active tool connection. This preselects the system identifier automatically.
A minimal test case consists of three test steps:
Optionally, the test step Check Simulation Status can be used to compare the simulation end status with an expected value.
The test steps can be found under the tab Test steps in the folder Environment simulation. A detailed explanation of all environmental simulation test steps can be found under Environment Simulation.
Offline file creation¶
A right click on the model tree`s root opens a context menu by which the sytem can be stored in an offline file. A dialog opens to specify the directory and name for the offline file to be stored. Since dynamic reload is activated, only the actually existing data in the data view is stored in the offline file. This generated offline file can be selected as a offline data source in Tab Environment.
Refresh data¶
A right click on the tree`s root opens a context menu by which the loaded system can be refreshed. The system is therefore read in again. The context menu entry is only available if the underlying tool supports online query.
Scenario database access¶
ecu.test can access scenarios stored in test.guide and execute them. For IPG CarMaker these scenarios are test run files, for Hexagon VTD they are OpenScenario and XML files. All dependencies (roads, 3D objects, …) required by these scenarios must already exist in the tool workspaces. The test.guide instance configured as standard in ecu.test is used as the data source.
The functionality can be activated by right-clicking the “Scenarios” node in the environment simulation tab. The scenarios of the selected depository can be displayed, filtered and selected in the displayed dialog. Upon confirmation, these scenarios are downloaded from test.guide and transferred to the scenarios folder of the respective environment simulation. These scenarios are then available in the scenario tree and can be used as usual.