Page History
...
A scenario can be chosen similarly to the script selection in Setup. Either use the Open button or edit the path text field and hit Enter.
| Info | ||
|---|---|---|
| ||
We have not (yet) implemented the whole commonroad specification. Intersections, crossings, traffic lights, traffic signs and signals are currently being ignored and print warnings visible in the LCC Errors Tab. We also do not (yet) have a consistent handling of inexact positional values (we currently use the average) and rotations for shapes. The assumed default value for positions is (0,0) (origin). |
Transforming the Scenario
...
Obstacles and IDs
The loaded commonroad Commonroad scenario may define obstacles. The obstacle ID set in commonroad Commonroad is interpreted as the ID of the vehicle in the scenario. This is especially important if you choose to use the movement defined for the obstacle to be used as trajectory for a real vehicle. In this case, the real vehicle with the same ID will respond to the message.
...
| Info |
|---|
We only allow for obstacle IDs up to 256 due to the message types in use (uint8_t for ID) (TODO?), thus the ID is taken mod 256 if it is higher than that - we do not expect that you need to use more than 256 obstacles within one scenario (this might also have bad consequences for the performance of a simulation). |
| Info | ||
|---|---|---|
| ||
(TODO - Link?) To actually see / use the obstacle simulation, you need to:
As this is rather unintuitive, we will change this in the future. |
Overview
Content Tools