Skip to content

177. Cyclist Close to Moving SUT evaluation scenario

The cyclist_close_to_moving_sut evaluation scenario detects cases where a cyclist is close to the Ego while the Ego is moving.

Scenario location: $FTX/logiq/scenario_library_post_match/plain_objects/cyclist_close_to_moving_sut

Actor Description Type Depiction
ego Vehicle under test vehicle
cyclist Cyclist that is close to the Ego cyclist
Figure 1: Cyclist Close to Moving SUT

177.1 Scenario phases

The phase descriptions are as follows:

177.1.1 sut.cyclist_close_to_moving_sut

Ego: The Ego is driving at a speed of at least sut_minimal_speed.

cyclist: The cyclist is close to the Ego, maintaining a global distance from the Ego in the range between min_distance_from_cyclist and max_distance_from_cyclist. The scenario should last at most max_phase_duration.

177.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
min_distance_from_cyclist length m Minimum distance between the cyclist and the Ego 0m
max_distance_from_cyclist length m Maximum distance between the cyclist and the Ego 5m
sut_minimal_speed speed kph Minimum speed of the Ego 5kph
max_phase_duration time s Maximum phase duration 5s

177.3 Metrics

177.3.1 Coverage

[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

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

177.4 Log and Error Messages

No scenario-specific log messages.

177.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).
OSC2 code: cyclist_close_to_moving_sut post-match scenario usage
import "$FTX/logiq/scenario_library_post_match/plain_objects/cyclist_close_to_moving_sut/cyclist_close_to_moving_sut_top.osc"

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

match:
    cyclist_close_to_moving_sut: sut.cyclist_close_to_moving_sut(min_distance_from_cyclist: 0m,
                                                                 max_distance_from_cyclist: 5m,
                                                                 sut_minimal_speed: 5kph,
                                                                 max_phase_duration: 5s)