Skip to content

150. Ego Merge At Highway evaluation scenario

In the ego_merge_at_highway evaluation scenario, the Ego is merging onto the highway.

Scenario location: $FTX/logiq/scenario_library_post_match/ego_merge/ego_merge_at_highway

150.1 Actors

The actors associated with this scenario are as follows:

Actor Description Type Depiction
ego Vehicle under test vehicle
Figure 1: Ego Merge At Highway

150.2 Scenario phases

The phase descriptions are as follows:

150.2.1 on_highway_entry

ego: The Ego is driving on the highway_entry.

150.2.2 on_highway

ego: The Ego has finished merging and is driving on the highway.

150.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_on_highway_phase_duration time s Maximum time of the on_highway phase 4s
max_on_highway_entry_phase_duration time s Maximum time of the on_highway_entry phase 7s
distance_from_highway_entry_end length m Maximum distance from the end of the highway entry to the Ego in the on_highway_entry phase 5m

150.4 Metrics

150.4.1 Coverage

[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

150.4.2 KPI

[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

150.5 Log and Error Messages

No scenario-specific log messages.

150.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: ego_merge_at_highway post-match scenario usage
import "$FTX/logiq/scenario_library_post_match/ego_merge/ego_merge_at_highway/ego_merge_at_highway_top.osc"

# The following example imports the top file and overrides three parameters:

match:
    ego_merge_at_highway: sut.ego_merge_at_highway(max_on_highway_phase_duration: 4s,
                                                   max_on_highway_entry_phase_duration: 7s,
                                                   distance_from_highway_entry_end: 5m)