141. Cyclist Overtake In Lane evaluation scenario
In the cyclist_overtake_in_lane evaluation scenario, the vehicle actor (cyclist) overtakes the Ego while they are both in the same lane.
Scenario location: $FTX/logiq/scenario_library_post_match/adjacent_vehicles/cyclist_overtake_in_lane
141.1 Actors
The actors associated with this scenario are as follows:
| Actor | Description | Type | Depiction |
|---|---|---|---|
ego |
Vehicle under test | vehicle |
 |
vehicle_actor |
Overtaking cyclist | cyclist |
 |
141.2 Scenario phases
The phase descriptions are as follows:
141.2.1 init_drive
Ego: The Ego drives ahead of the vehicle actor in the same lane.
vehicle_actor: The vehicle actor drives behind the Ego in the same lane, maintaining a distance within
the range of max_distance_from_sut during the entire phase.
141.2.2 overtake
Ego: The Ego drives behind the vehicle actor in the same lane.
vehicle_actor: The vehicle actor drives ahead of the Ego in the same lane, maintaining a distance within
the range of max_distance_from_sut during the entire phase.
141.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 |
|---|---|---|---|---|
max_distance_from_sut |
length | m | Maximum distance from the Ego to the vehicle actor during the entire scenario | 15m |
min_init_drive_phase_duration |
time | s | Minimum time of the init_drive phase |
0.1s |
max_init_drive_phase_duration |
time | s | Maximum time of the init_drive phase |
5s |
min_overtake_phase_duration |
time | s | Minimum time of the overtake phase |
0.1s |
max_overtake_phase_duration |
time | s | Maximum time of the overtake phase |
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 | — |
141.4 Metrics
141.4.1 Coverage
| Item | Description | Values | Unit/Type |
|---|---|---|---|
overtake_side |
Overtake side relative to Ego | left, right | av_side |
[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 |
141.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 |
141.5 Log and Error Messages
No scenario-specific log messages.
141.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).
import "$FTX/logiq/scenario_library_post_match/adjacent_vehicles/cyclist_overtake_in_lane/cyclist_overtake_in_lane_top.osc"
# The following example imports the top file and overrides six parameters:
match:
cyclist_overtake_in_lane: sut.cyclist_overtake_in_lane(max_distance_from_sut: 15m,
min_init_drive_phase_duration: 0.1s,
max_init_drive_phase_duration: 5s,
min_overtake_phase_duration: 0.1s,
max_overtake_phase_duration: 5s,
kinds: [cyclist])