175. Object on ego lane evaluation scenario
In the object_on_ego_lane evaluation scenario, an object is located close to the Ego, on the Ego lane.
Scenario location: $FTX/logiq/scenario_library_post_match/plain_objects/object_on_ego_lane
| Actor | Description | Type | Depiction |
|---|---|---|---|
ego |
Vehicle under test | vehicle |
 |
object |
Object that is on Ego lane | plain_object |
 |
175.1 Scenario phases
The phase descriptions are as follows:
175.1.1 object_ahead_of_ego
Ego: The Ego is driving and maintains a distance of at least minimal_distance_away_from_junction_start from the start of any junction.
object: The object is located on the Ego lane with a maximal distance of max_distance_ahead_of_ego from the Ego.
175.2 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_ahead_of_ego |
length | m | Maximum distance of the object from the Ego during the scenario | 10m |
minimal_distance_away_from_junction_start |
length | m | A negative offset from the start of the junction. If the Ego is within this offset (e.g., -5 meters indicates 5 meters before the junction start), the scenario will not be captured | -5m |
175.3 Metrics
175.3.1 Coverage
| Item | Description | Values | Unit/Type |
|---|---|---|---|
min_distance_from_object |
Minimum closest-to-closest euclidean distance between the Ego and the object throughout the match interval | [0..2), every: 0.5 | m |
object_max_speed |
Maximum speed of the object throughout the match interval | [0..20), every: 5.0 | mph |
object_conflict_mode |
Object conflict mode is determined by the object's classification and its interaction with the Ego's path | UNDEFINED, VRU_LD_nearside, VRU_LD_farside, LF_SDLI, LF_ODLI, moving_fod_LD_farside, SCP_MFCRD, animal_LD_farside, animal_LD_nearside, fod_in_lane, animal_in_lane | object_conflict_mode |
[Click] The coverage items inherited from the sut.logiq_base_object_scenario scenario are as follows:
| Item | Description | Values | Unit/Type |
|---|---|---|---|
object_kind |
Object kind of object, as derived from Foretify |
object, person, cyclist, vehicle, truck, trailer, fod, animal, sign, bus, motorcycle, emergency_vehicle, stationary_vehicle | evaluation_object_kind |
[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 |
175.3.2 KPI
[Click] The KPIs inherited from the sut.logiq_base_object_scenario scenario are as follows:
| Item | Description | Values | Unit/Type |
|---|---|---|---|
object_tracking_id |
Tracking id of the object as described in the object list data. If the data comes from a generative run, the UID will be used | string |
[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 |
175.4 Log and Error Messages
No scenario-specific log messages.
175.5 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/plain_objects/object_on_ego_lane/object_on_ego_lane_top.osc"
# The following example imports the top file and overrides two parameters:
match:
object_on_ego_lane: sut.object_on_ego_lane(max_distance_ahead_of_ego: 10m,
minimal_distance_away_from_junction_start: -5m)