198. Ego traverse junction
Scenario location: $FTX_PACKAGES/base_scenarios/scenarios/junction_family/ego_traverse_junction/
In the ego_traverse_junction scenario, the Ego traverses a junction from the in-road, passes through the junction, and exits from the out-road.
198.1 Actors
The actors associated with this scenario are as follows:
| Name | Description | Type | Depiction |
|---|---|---|---|
ego |
Vehicle under test | vehicle |
 |
198.2 Prerequisites
Environmental requirements: A road with a junction ahead.
198.3 Scenario essence
198.3.1 phase_essence
The ego_traverse_junction scenario invokes the Vehicle traverse junction scenario.
198.4 Scenario Main phases
The ego_traverse_junction_main scenario is structured into three distinct phases.
198.4.1 phase_ego_warm_up
The phase_ego_warm_up invokes the ego_traverse_junction_ego_warm_up scenario.
198.4.2 phase_essence
The phase_essence invokes the phase_essence.
198.4.3 phase_post
The phase_post invokes the ego_traverse_junction_post scenario.
198.5 Parameters
The paths to the CSV file and the main CSV file are as follows:
$FTX_PACKAGES/base_scenarios/test_suites/test_suite_definitions/junction_family/ego_traverse_junction.csv
$FTX_PACKAGES/base_scenarios/test_suites/test_suite_definitions/junction_family/ego_traverse_junction_main.csv
The parameters you can constrain to create tests with the ego_traverse_junction.csv file are as follows:
| Parameter | Description | Range |
|---|---|---|
gen_ego_distance_to_junction_at_start |
Generated distance between the Ego and the junction when Ego is at the in-road | [20..50]m |
gen_ego_traversal_direction |
Generated traversal direction of the Ego at the junction | right, left, straight |
gen_ego_speed_at_start |
Input speed of the Ego at the start of the scenario | [5..70]kph |
198.6 Events
| Event | Description |
|---|---|
198.7 Metrics
Metrics collected during test execution are given below.
198.7.1 Coverage
The coverage metrics are given below.
198.7.1.1 Coverage items
The multi-dimensional situations captured during the test execution are as follows:
| Item | Description | Range | Unit/Type |
|---|---|---|---|
gen_ego_distance_to_junction_at_start |
Generated distance between the Ego and the junction when Ego is at the in-road | [20..50), every: 5.0 | m |
gen_ego_traversal_direction |
Generated traversal direction of the Ego at the junction | right, left, straight | drive_direction |
ego_distance_to_junction_at_start |
Distance between the Ego and the junction when the Ego is at the in-road | [20..50), every: 5.0 | m |
ego_traversal_direction |
The drive direction of the Ego at the junction | right, left, straight | drive_direction |
[Click] The coverage items inherited from the sut.junction_family_base scenario are as follows:
| Item | Description | Range | Unit/Type |
|---|---|---|---|
ego_junction_leg_sign_type |
The sign type of the Ego junction leg | stop, yield, other, no_sign | path_sign_type |
number_of_lanes_at_ego_leg |
The number of lanes present in the in-road of the Ego | [1..6), every: 1.0 | uint |
[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 | [5..70), every: 5.0 | kph |
ego_speed_at_start |
Actual speed of the Ego at the start of the scenario | [5..70), every: 5.0 | kph |
[Click] The scenario sut.vehicle_traverse_junction is included in the scenario sut.ego_traverse_junction, with the following coverage items:
| Item | Description | Range | Unit/Type |
|---|---|---|---|
| -- | -- | -- | -- |
198.7.1.2 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.junction_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 |
|---|---|---|
| -- | -- | -- |
[Click] The scenario sut.vehicle_traverse_junction is included in the scenario sut.ego_traverse_junction, with the following cross coverage items:
| Item | Description | Referred coverage items |
|---|---|---|
| -- | -- | -- |
198.7.2 KPI
The key performance indicators are given below.
198.7.2.1 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.junction_family_base scenario are as follows:
| Item | Description | Range | Unit/Type |
|---|---|---|---|
junction_type |
Type of junction the Ego is traversing | other, urban, highway | junction_type |
ego_deceleration_record |
Ego deceleration at junction drive | mpsps |
[Click] The KPIs inherited from the sut.generic_base scenario are as follows:
| Item | Description | Range | Unit/Type |
|---|---|---|---|
| -- | -- | -- | -- |
[Click] The scenario sut.vehicle_traverse_junction is included in the scenario sut.ego_traverse_junction, with the following KPIs:
| Item | Description | Range | Unit/Type |
|---|---|---|---|
| -- | -- | -- | -- |
198.8 Checks
| Default Severity | Description | Issue kind | Threshold |
|---|---|---|---|