139. Vehicle Lane Hugger Right evaluation scenario
In the vehicle_lane_hugger_right evaluation scenario, a vehicle (vehicle_actor) that is driving in the right lane adjacent to the Ego and is hugging the lane line. The scenario involves both vehicles driving in parallel, with vehicle_actor maintaining a close lateral distance to the lane's left boundary.
Scenario location: $FTX/logiq/scenario_library_post_match/adjacent_vehicles/vehicle_lane_hugger_right
139.1 Actors
The actors associated with this scenario are as follows:
| Actor | Description | Type | Depiction |
|---|---|---|---|
ego |
Vehicle under test | vehicle |
 |
vehicle_actor |
vehicle actor | vehicle |
 |
139.2 Scenario phases
The phase descriptions are as follows:
139.2.1 vehicle_lane_hugger
Ego: The Ego drives in one lane and maintains its lane.
vehicle_actor: The vehicle drives in the right lane adjacent to the Ego vehicle and is hugging the lane line. vehicle_actor maintains a close lateral distance to the line on its left side and a longitudinal distance between a minimum of min_longitudinal_distance and a maximum of max_longitudinal_distance from the Ego.
139.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 |
|---|---|---|---|---|
scenario_maximal_duration |
time | s | Maximum duration of the scenario | 10s |
max_longitudinal_distance |
length | m | Maximum longitudinal distance between the Ego and the NPC during the entire scenario | 10m |
min_longitudinal_distance |
length | m | Minimum longitudinal distance between the Ego and the NPC during the entire scenario | -10m |
min_lateral_distance |
length | m | Minimum lateral distance between the NPC and the left boundary line of the lane | -0.3m |
[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 | — |
139.4 Metrics
139.4.1 Coverage
[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 |
139.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 |
139.5 Log and Error Messages
No scenario-specific log messages.
139.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/vehicle_lane_hugger_right/vehicle_lane_hugger_right_top.osc"
# The following example imports the top file and overrides five parameters:
match:
vehicle_lane_hugger_right: sut.vehicle_lane_hugger_right(scenario_maximal_duration: 10s,
max_longitudinal_distance: 10m,
min_longitudinal_distance: -10m,
min_lateral_distance: -0.3m,
kinds: [vehicle, cyclist, truck, emergency_vehicle, bus, motorcycle])