Ego approach congestion
Scenario location: $FTX_PACKAGES/base_scenarios/scenarios/traffic/ego_approach_congestion/
In the Ego approach congestion scenario, the Ego travels and approaches the traffic vehicles.
Actors
The actors associated with this scenario are as follows:
| Name | Description | Type | Depiction |
|---|---|---|---|
ego |
Vehicle under test | vehicle |
 |
vehicle_1,vehicle_2,vehicle_3 |
Vehicles aahead of ego which creates a congestion | vehicle |
 |
Figure 1 shows the Ego approaching the congestion scenario.
Prerequisites
Environmental requirements: A road with at least three lanes.
Scenario essence
phase_essence
Ego: The Ego approaches the congestion and maintains a relative speed to the traffic.
vehicle_1, vehicle_2 and vehicle_3: These vehicles drive ahead of the Ego and slow down.
Scenario Main phases
The ego_approach_congestion_main scenario is structured into three distinct phases.
phase_ego_warm_up
The phase_ego_warm_up invokes the ego_approach_congestion_ego_warm_up scenario.
phase_essence
The phase_essence invokes the phase_essence.
phase_post
The phase_post invokes the ego_approach_congestion_post scenario.
Parameters
The paths to the CSV file and the main CSV file are as follows:
$FTX_PACKAGES/base_scenarios/test_suites/test_suite_definitions/traffic/ego_approach_congestion.csv
$FTX_PACKAGES/base_scenarios/test_suites/test_suite_definitions/traffic/ego_approach_congestion_main.csv
| Parameter | Description | Range |
|---|---|---|
gen_traffic_speed |
Input traffic speed | [0..150]kph |
gen_ego_speed_at_start |
Input speed of the Ego at the start of the scenario | [0..150]kph |
Events
No events are defined in this scenario.
Metrics
Metrics collected during test execution are given below.
Coverage
The coverage metrics are given below.
Coverage items
The multi-dimensional situations captured during the test execution are as follows:
| Item | Description | Range | Unit/Type |
|---|---|---|---|
vehicle_1_speed_at_start |
vehicle_1 speed at start | [0..150), every: 10.0 | kph |
vehicle_2_speed_at_start |
vehicle_2 speed at start | [0..150), every: 10.0 | kph |
vehicle_3_speed_at_start |
vehicle_3 speed at start | [0..150), every: 10.0 | kph |
gen_traffic_speed |
Input traffic speed | [0..150), every: 10.0 | kph |
traffic_speed |
Actual traffic speed | [0..150), every: 10.0 | kph |
[Click] The coverage items inherited from the sut.traffic_family_base scenario are as follows:
| Item | Description | Range | Unit/Type |
|---|---|---|---|
| -- | -- | -- | -- |
[Click] The coverage items inherited from the sut.generic_base scenario are as follows:
| Item | Description | Range | Unit/Type |
|---|---|---|---|
gen_ego_speed_at_start |
Input speed of the Ego at the start of the scenario | [0..150), every: 10.0 | kph |
ego_speed_at_start |
Actual speed of the Ego at the start of the scenario | [0..150), every: 10.0 | kph |
Cross coverage items
The test execution data for the combination of multiple coverage items is as follows:
| Item | Description | Referred coverage items |
|---|---|---|
| -- | -- | -- |
[Click] The cross coverage items inherited from the sut.traffic_family_base scenario are as follows:
| Item | Description | Referred coverage items |
|---|---|---|
| -- | -- | -- |
[Click] The cross coverage items inherited from the sut.generic_base scenario are as follows:
| Item | Description | Referred coverage items |
|---|---|---|
| -- | -- | -- |
KPI
The key performance indicators are given below.
Record items
The performance metrics and the data items captured during the test execution are as follows:
| Item | Description | Range | Unit/Type |
|---|---|---|---|
| -- | -- | -- | -- |
[Click] The KPIs inherited from the sut.traffic_family_base scenario are as follows:
| Item | Description | Range | Unit/Type |
|---|---|---|---|
| -- | -- | -- | -- |
[Click] The KPIs inherited from the sut.generic_base scenario are as follows:
| Item | Description | Range | Unit/Type |
|---|---|---|---|
| -- | -- | -- | -- |