| ComponentController | ComponentController | 200 | ADAS | Manages vehicle component states with regard to other vehicle component states and conditions and in response to events. |
...
...
@@ -179,6 +182,8 @@ With corresponding defined indices :
| ComponentController | Special | 83 |
| OpenScenarioActions | Special | 84 |
| Parameter_Vehicle | Sensor | 92 |
| SensorAggregation | Sensor | 93 |
| SensorFusion | Sensor | 94 |
| Sensor_Driver | Sensor | 95 |
**Ids for Signals (last two digits)**
...
...
@@ -206,6 +211,7 @@ With corresponding defined indices :
@@ -188,7 +188,7 @@ Although OpenSCENARIO also states other ways for defining a position, we current
Unlike OpenSCENARIO we also allow some of these values to be stochastic.
This is marked by adding a subtag <Stochasticsvalue="valuetype"stdDeviation="value"lowerBound="value"upperBound="value"/> to the <LanePosition> or <SpeedAction> tag.
The stochastics tag is intended to be used as NormalDistribution, but it is up to each module using it to define the actual usage.
The valuetype can either be s, offset, velocity or rate.
The valuetype can either be s, offset (if inside LanePosition), velocity or rate (if inside SpeedAction).
The value defined as attribute of the LanePosition/SpeedActionDynamics/AbsoluteTargetSpeed tag is then taken as mean value.
The VisibilityAction is optional.
If VisibilityAction is not defined the agent will be spawned.