Adjacent VRUs family base
Location: $FTX_PACKAGES/base_scenarios/scenarios/adjacent_vrus_family/adjacent_vrus_family_base/
The adjacent_vrus_family_base consists of common input variables, coverage, and KPIs common across all Adjacent VRUs scenarios.
Adjacent VRUs family ego_warm_up and post scenarios
The Adjacent VRUs family scenarios use these ego_warm_up and post scenarios.
ego_drive
ego_drive_ego_warm_up
Ego: The Ego starts driving and attempts to maintain its lane for the duration of gen_duration_at_ego_warm_up.
ego_drive_post
Ego: The Ego continues driving, maintaining its lane for the duration of gen_duration_at_post.
ego_drive_with_motorcycle_and_vehicles
ego_drive_with_motorcycle_and_vehicles_ego_warm_up
Ego: The Ego starts driving and attempts to maintain its lane for the duration of gen_duration_at_ego_warm_up.
lead_vehicle: The lead_vehicle starts driving and attempts to maintain its lane for the duration of gen_duration_at_ego_warm_up.
adjacent_vehicle_1: The adjacent_vehicle_1 starts driving and attempts to maintain its lane for the duration of gen_duration_at_ego_warm_up.
adjacent_vehicle_2: The adjacent_vehicle_2 starts driving and attempts to maintain its lane for the duration of gen_duration_at_ego_warm_up.
motorcycle: The motorcycle starts driving and attempts to maintain its lane for the duration of gen_duration_at_ego_warm_up.
ego_drive_with_motorcycle_and_vehicles_post
Ego: The Ego continues driving, maintaining its lane for the duration of gen_duration_at_post.
lead_vehicle: The lead_vehicle continues driving, maintaining its lane for the duration of gen_duration_at_post.
adjacent_vehicle_1: The adjacent_vehicle_1 continues driving, maintaining its lane for the duration of gen_duration_at_post.
adjacent_vehicle_2: The adjacent_vehicle_2 continues driving, maintaining its lane for the duration of gen_duration_at_post.
motorcycle: The motorcycle continues driving, maintaining its lane for the duration of gen_duration_at_post.
ego_drive_with_traffic_group
ego_drive_with_traffic_group_ego_warm_up
Ego: The Ego starts driving and attempts to maintain its lane for the duration of gen_duration_at_ego_warm_up.
vru_group: The vru_group starts driving and attempts to maintain its lane for the duration of gen_duration_at_ego_warm_up.
neighbor_vehicle: The neighbor_vehicle starts driving and attempts to maintain its lane for the duration of gen_duration_at_ego_warm_up.
ego_drive_with_traffic_group_post
Ego: The Ego continues driving, maintaining its lane for the duration of gen_duration_at_post.
vru_group: The vru_group continues driving, maintaining its lane for the duration of gen_duration_at_post.
neighbor_vehicle: The neighbor_vehicle continues driving, maintaining its lane for the duration of gen_duration_at_post.
Parameters
| Parameter | Description | Range |
|---|---|---|
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 |
|---|---|---|---|
| -- | -- | -- | -- |
[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.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.generic_base scenario are as follows:
| Item | Description | Range | Unit/Type |
|---|---|---|---|
| -- | -- | -- | -- |
Checks
The captured problematic behavior or conditions are as follows:
| Default Severity | Description | Issue kind | Threshold |
|---|---|---|---|