Skip to content

161. SUT Approach Junction evaluation scenario

In the sut_approach_junction evaluation scenario, the Ego drives towards a junction.

Scenario location: $FTX/logiq/scenario_library_post_match/junctions/sut_approach_junction

161.1 Actors

The actors associated with this scenario are as follows:

Actor Description Type Depiction
ego Vehicle under test vehicle
Figure 1: SUT approach junction

161.2 Scenario phases

The phase descriptions are as follows:

161.2.1 sut_approach_junction

Ego: The Ego drives towards the junction start at a distance in the range of max_distance_from_junction_start to 0m.

161.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_junction_start length m Distance from the junction where the scenario starts -45m

161.4 Metrics

161.4.1 Coverage

Item Description Values Unit/Type
traffic_control_device Type of traffic control device at the junction start none, traffic_light, stop_sign, yield_sign traffic_control
[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

161.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

161.5 Log and Error Messages

No scenario-specific log messages.

161.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_approach_junction post-match scenario usage
import "$FTX/logiq/scenario_library_post_match/junctions/sut_approach_junction/sut_approach_junction_top.osc"

# The following example imports the top file and overrides one parameter:

match:
    sut_approach_junction: sut.sut_approach_junction(max_distance_from_junction_start: -45m)