145. SUT Cut Out evaluation scenario
In the sut_cut_out evaluation scenario, the Ego follows behind a vehicle in the same lane and then cuts out to an adjacent lane.
Scenario location: $FTX/logiq/scenario_library_post_match/ego_cut_out/sut_cut_out
145.1 Actors
The actors associated with this scenario are as follows:
| Actor | Description | Type | Depiction |
|---|---|---|---|
ego |
Vehicle under test | vehicle |
 |
vehicle_actor |
Cut out vehicle | vehicle |
 |
145.2 Scenario phases
The phase descriptions are as follows:
145.2.1 ego_on_same_lane
Ego: The Ego is driving in the same lane as the vehicle_actor, following behind it.
vehicle_actor: The vehicle_actor drives ahead of the Ego in the same lane and remains in the range of
min_distance_from_sut_in_time_units to max_distance_from_sut_in_time_units.
145.2.2 ego_side_of_npc
Ego: The Ego changes lanes and continues driving in the lane adjacent to the vehicle_actor.
vehicle_actor: The vehicle_actor continues driving in the same lane.
145.3 Configuration parameters
Use these parameters to constrain the scenario. If you do not set a specific value, the default value will be used.
| Parameter | Type | Unit | Description | Default value |
|---|---|---|---|---|
min_ego_on_same_lane_phase_duration |
time | s | Minimum time of the ego_on_same_lane phase |
1s |
max_ego_on_same_lane_phase_duration |
time | s | Maximum time of the ego_on_same_lane phase |
3s |
min_ego_on_side_of_npc_phase_duration |
time | s | Minimum time of the ego_side_of_npc phase |
1s |
max_ego_on_side_of_npc_phase_duration |
time | s | Maximum time of the ego_side_of_npc phase |
3s |
[Click] The input items inherited from the sut.logiq_base_lane_following_scenario scenario are as follows:
| Parameter | Type | Unit | Description | Default value |
|---|---|---|---|---|
min_distance_from_sut_in_time_units |
time | s | Minimum headway distance between the Ego and the vehicle actor | 0s |
max_distance_from_sut_in_time_units |
time | s | Maximum headway distance between the Ego and the vehicle actor | 5s |
[Click] The input items inherited from the sut.logiq_base_vehicle_scenario scenario are as follows:
| Parameter | Type | Unit | Description | Default value |
|---|---|---|---|---|
kinds |
list of evaluation_object_kind | — | Possible kinds of vehicle_actor in the scenario | — |
145.4 Metrics
145.4.1 Coverage
| Item | Description | Values | Unit/Type |
|---|---|---|---|
speed_at_change_lane |
Speed of the vehicle_actor at the lane change |
[0..180), every: 10.0 | kph |
distance_at_change_lane |
Distance between the vehicle_actor and the Ego at the lane change |
[0..200), every: 10.0 | meter |
side_of_npc_relative_to_ego_at_lane_change |
Side of the vehicle_actor relative to the Ego at the lane change |
left, right | av_side |
[Click] The coverage items inherited from the sut.logiq_base_lane_following_scenario scenario are as follows:
| Item | Description | Values | Unit/Type |
|---|---|---|---|
ego_min_distance_to_vehicle |
Minimum distance gap throughout the scenario | [0..200), every: 20.0 | m |
[Click] The coverage items inherited from the sut.logiq_base_vehicle_scenario scenario are as follows:
| Item | Description | Values | Unit/Type |
|---|---|---|---|
vehicle_speed_at_start |
Agent speed at start of the scenario | [0..150), every: 10.0 | mph |
[Click] The coverage items inherited from the sut.logiq_base_scenario scenario are as follows:
| Item | Description | Values | Unit/Type |
|---|---|---|---|
ego_speed_at_start |
Ego longitudinal speed at the start of the scenario | [0..160), every: 10.0 | mph |
145.4.2 KPI
[Click] The KPIs inherited from the sut.logiq_base_vehicle_scenario scenario are as follows:
| Item | Description | Values | Unit/Type |
|---|---|---|---|
vehicle_object_kind |
Object kind as derived from Foretify | object, person, cyclist, vehicle, truck, trailer, fod, animal, sign, bus, motorcycle, emergency_vehicle, stationary_vehicle | evaluation_object_kind |
vehicle_tracking_id |
Tracking id of the agent as described in the object list data. If the data comes from a generative run, the UID will be used | string | |
vehicle_avg_speed |
Agent average longitudinal speed throughout the scenario | mph | |
vehicle_max_speed |
Agent maximum speed throughout the scenario | mph | |
vehicle_min_speed |
Agent minimum speed throughout the scenario | mph | |
vehicle_max_lon_acceleration |
Agent maximum longitudinal acceleration throughout the scenario | mpsps | |
vehicle_min_lon_acceleration |
Agent minimum longitudinal acceleration throughout the scenario | mpsps | |
ego_min_ttc_to_vehicle |
Minimum time to collision with the reference vehicle throughout the scenario | s | |
ego_min_mttc_to_vehicle |
Minimum modified time to collision with the reference vehicle throughout the scenario | s |
[Click] The KPIs inherited from the sut.logiq_base_scenario scenario are as follows:
| Item | Description | Values | Unit/Type |
|---|---|---|---|
ego_max_lon_acceleration |
Ego maximum acceleration throughout the scenario | mpsps | |
ego_min_lon_acceleration |
Ego minimum acceleration throughout the scenario | mpsps | |
ego_min_speed |
Ego minimum longitudinal speed throughout the scenario | mph | |
ego_avg_speed |
Ego average longitudinal speed throughout the scenario | mph | |
ego_max_speed |
Ego maximum longitudinal speed throughout the scenario | mph | |
ego_distance_traveled_during_interval |
Total distance traveled by the Ego during the interval | m | |
interval_duration |
Interval duration of the scenario | s |
145.5 Log and Error Messages
No scenario-specific log messages.
145.6 Usage
Import the post-match scenario top file and register the matcher in a match: block, overriding only the parameters you need. Any omitted parameters use the defaults listed in Configuration parameters.
The matcher is also available through the shared post-match import bundle:
$FTX/logiq/customers/base/osc/post_match_scenarios.osc$FTX/evaluate/library/scenarios/scenario_library_post_match.osc(evaluation builds).
OSC2 code: sut_cut_out post-match scenario usage
import "$FTX/logiq/scenario_library_post_match/ego_cut_out/sut_cut_out/sut_cut_out_top.osc"
# The following example imports the top file and overrides seven parameters:
match:
sut_cut_out: sut.sut_cut_out(min_ego_on_same_lane_phase_duration: 1s,
max_ego_on_same_lane_phase_duration: 3s,
min_ego_on_side_of_npc_phase_duration: 1s,
max_ego_on_side_of_npc_phase_duration: 3s,
min_distance_from_sut_in_time_units: 0s,
max_distance_from_sut_in_time_units: 5s,
kinds: [vehicle, cyclist, truck, emergency_vehicle, bus, motorcycle])