154. SUT junction traversal evaluation scenario

In the sut_junction_traversal evaluation scenario, the Ego drives through a junction.

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

154.1 Actors

The actors associated with this scenario are as follows:

Actor	Description	Type	Depiction
`ego`	Vehicle under test	`vehicle`

154.2 Scenario phases

The phase descriptions are as follows:

154.2.1 `sut_junction_traversal`

Ego: The Ego is within the junction.

154.3 Configuration parameters

There are no input parameters

154.4 Metrics

154.4.1 Coverage

Item	Description	Values	Unit/Type
`time_in_junction`	Time the Ego spent in the junction	[0..40), every: 1.0	s
`traffic_light_color_change`	Color of the traffic light in the beginning and end of the traversal		string
`ego_traversal_type`	Determines the traversal type through the junction, classified as protected, unprotected, protected-to-unprotected, or unprotected-to-protected	protected, unprotected, protected_to_unprotected, unprotected_to_protected, missing_traffic_light_state	traversal_type
`planned_path_complexity_index`	Number of the overlapping lanes with the Ego's lane inside the junction	0, 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15, [16..30)	int
`max_number_of_lanes_in_oncoming_legs`	Maximum number of lanes across all oncoming roads at the junction, treating multiple roads as a single oncoming leg	0, 1, 2, 3, 4, 5, 6, 7	int
`max_number_of_lanes_in_incoming_legs`	Maximum number of lanes across all incoming roads at the junction, treating multiple roads as a single incoming leg	0, 1, 2, 3, 4, 5, 6, 7	int
`max_number_of_lanes_in_crossing_legs`	Maximum number of lanes across all crossing roads at the junction, treating multiple roads as a single crossing leg	0, 1, 2, 3, 4, 5, 6, 7	int
`number_of_junction_legs`	Number of unique legs at the junction	2, 3, 4, 5, 6, 7, 8	int
`traffic_control_device`	Type of traffic control device at the junction start	none, traffic_light, stop_sign, yield_sign	traffic_control
`ego_traversal_direction`	Direction of the traversal through the junction	other, straight, slight_right, right, sharp_right, backwards, sharp_left, left, slight_left	direction

[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

154.4.2 KPI

[Click] The KPIs inherited from the sut.logiq_base_scenario scenario are as follows:

Item	Description	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

154.5 Log and Error Messages

No scenario-specific log messages.

154.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_junction_traversal post-match scenario usage

import "$FTX/logiq/scenario_library_post_match/junctions/sut_junction_traversal/sut_junction_traversal_top.osc"

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

match:
    sut_junction_traversal: sut.sut_junction_traversal()