157. SUT yield to NPC with crossing paths evaluation scenario

In the sut_yield_to_npc_with_crossing_paths evaluation scenario, the Ego yields to the NPC from a different junction entry, with a shared area between their paths inside the junction.

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

157.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`

Phase 1: Ego yield to NPC with crossing paths

Phase 2: Ego yield to NPC with crossing paths

Phase 3: Ego yield to NPC with crossing paths

Phase 4: Ego yield to NPC with crossing paths

157.2 Scenario phases

The phase descriptions are as follows:

157.2.1 `sut_stops_and_gives_the_right_of_way`

Ego: The Ego stops near the same junction as the vehicle_actor, positioned between min_offset_from_junction_start and max_offset_from_junction_start from the junction start and gives the right of way to the vehicle_actor. Its speed ranges from 0 kph up to stopping_car_speed_limit, and it is outside the no_traffic_light_ahead_distance from any traffic light.

vehicle_actor: The vehicle_actor is within the junction. The Ego has entered the same junction and comes from a different junction entry. The vehicle_actor has not yet entered the shared area where its path intersects with the Ego's path inside the junction.

157.2.2 `npc_in_encroachment_area_and_sut_yields`

Ego: The Ego has not yet entered the shared area where its path intersects with the vehicle_actor's path inside the junction.

vehicle_actor: The vehicle_actor is in the shared area where its path intersects with the Ego's path inside the junction.

157.2.3 `encroachment_area_is_clear`

Ego: The Ego has not yet entered the shared area where its path intersects with the vehicle_actor's path inside the junction.

vehicle_actor: The vehicle_actor has finished crossing the shared area where its path intersects with the Ego's path inside the junction.

157.2.4 `sut_in_encroachment_area`

Ego: The Ego is in the shared area where its path intersects with the vehicle_actor's path inside the junction.

157.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
`no_traffic_light_ahead_distance`	length	m	Forward distance within which no traffic lights should be detected ahead of the vehicle_actor	20m

[Click] The input items inherited from the sut.logiq_crossing_path_scenario scenario are as follows:

Parameter	Type	Unit	Description	Default value
`encroachment_start_buffer`	float	5	Specify a part from the beginning of the encroachment area that will be excluded from it (i.e. in this area, the modifier will still return false). For example: start_buffer 0.25 means only the last 75% of the encroachment will be considered as part of the encroachment	0.25
`encroachment_end_buffer`	float	5	Specify a part from the end of the the encroachment area that will be excluded from it(i.e. in this area, the modifier will still return false). For example: end_buffer 0.25 means only the first 75% of the encroachment will be considered as part of the encroachment	0.25

[Click] The input items inherited from the sut.logiq_yield_scenario scenario are as follows:

Parameter	Type	Unit	Description	Default value
`max_offset_from_junction_start`	length	m	Maximum distance from an actor to the junction start	10m
`ref_car_max_distance_from_junction`	length	m	Maximum distance (in length units) from the junction for the reference vehicle to be considered inside the junction	10m
`stopping_car_speed_limit`	speed	kph	Maximum speed of an actor to be considered as stopped	2kph

[Click] The input items inherited from the sut.logiq_sut_and_npc_in_junction_scenario scenario are as follows:

Parameter	Type	Unit	Description	Default value
`min_offset_from_junction_start`	length	m	Minimum offset from the junction start; negative values indicate positions behind the junction start	-10m
`min_offset_from_junction_end`	length	m	Minimum offset from the junction end; negative values indicate positions behind the junction end	-5m
`max_offset_from_junction_end`	length	m	Maximum offset from the junction end; positive values indicate positions after the junction end	5m

[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	—

157.4 Metrics

157.4.1 Coverage

Item	Description	Values	Unit/Type
`traversal_relative_direction`	Traverse direction of the vehicle_actor relative to the Ego	parallel_to_right, parallel_to_parallel, parallel_to_left, parallel_to_opposite, right_to_parallel, right_to_left, right_to_opposite, right_to_right, opposite_to_opposite, opposite_to_right, opposite_to_left, opposite_to_parallel, left_to_parallel, left_to_right, left_to_opposite, left_to_left, unknown	traversal_relative_direction

[Click] The coverage items inherited from the sut.logiq_crossing_path_scenario scenario are as follows:

Item	Description	Values	Unit/Type
`PET_between_sut_and_npc`	Minimum time between the first vehicle exiting an encroachment point and the second vehicle entering that point. Note: Compound physical objects are not fully supported, and may yield incorrect results	[0..10), every: 1.0	s

[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

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

157.5 Log and Error Messages

No scenario-specific log messages.

157.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_yield_to_npc_with_crossing_paths post-match scenario usage

import "$FTX/logiq/scenario_library_post_match/junctions/sut_yield_to_npc_with_crossing_paths/sut_yield_to_npc_with_crossing_paths_top.osc"

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

match:
    sut_yield_to_npc_with_crossing_paths: sut.sut_yield_to_npc_with_crossing_paths(no_traffic_light_ahead_distance: 20m,
                                                                                   encroachment_start_buffer: 0.25,
                                                                                   encroachment_end_buffer: 0.25,
                                                                                   max_offset_from_junction_start: 10m,
                                                                                   ref_car_max_distance_from_junction: 10m,
                                                                                   stopping_car_speed_limit: 2kph,
                                                                                   min_offset_from_junction_start: -10m,
                                                                                   min_offset_from_junction_end: -5m,
                                                                                   max_offset_from_junction_end: 5m,
                                                                                   kinds: [vehicle, cyclist, truck, emergency_vehicle, bus, motorcycle])