Run Out

Role

run_out is the module that decelerates and stops for dynamic obstacles such as pedestrians, bicycles and motorcycles.

Activation Timing

This module is activated if launch_run_out becomes true

Inner-workings / Algorithms

Flow chart

@startuml
title modifyPathVelocity
start

partition "Preprocess path" {
:Calculate the expected target velocity for ego vehicle;
:Extend path;
:Trim path from ego position;
}

partition "Preprocess obstacles" {
:Create data of abstracted dynamic obstacles;
:Exclude obstacles outside of partition lanelet;
}

partition "Collision_detection" {
:Detect collision with dynamic obstacles;
}

partition "Insert velocity" {
:Insert velocity to decelerate for obstacles;

:Limit velocity with specified jerk and acc limit;
}
stop
@enduml

Preprocess path

Calculate the expected target velocity for ego vehicle

Calculate the expected target velocity for the ego vehicle path to calculate time to collision with obstacles more precisely. The expected target velocity is calculated with autoware velocity smoother module by using current velocity, current acceleration and velocity limits directed by the map and external API.

Extend the path

The path is extended by the length of base link to front to consider obstacles after the goal.

Trim path from ego position

The path is trimmed from ego position to a certain distance to reduce calculation time. Trimmed distance is specified by parameter of detection_distance.

Preprocess obstacles

Create data of abstracted dynamic obstacle

This module can handle multiple types of obstacles by creating abstracted dynamic obstacle data layer. Currently we have 3 types of detection method (Object, ObjectWithoutPath, Points) to create abstracted obstacle data.

Abstracted dynamic obstacle

Abstracted obstacle data has following information.

Enter the maximum/minimum velocity of the object as a parameter, adding enough margin to the expected velocity. This parameter is used to create polygons for collision detection.

Future work: Determine the maximum/minimum velocity from the estimated velocity with covariance of the object

3 types of detection method

We have 3 types of detection method to meet different safety and availability requirements. The characteristics of them are shown in the table below. Method of Object has high availability (less false positive) because it detects only objects whose predicted path is on the lane. However, sometimes it is not safe because perception may fail to detect obstacles or generate incorrect predicted paths. On the other hand, method of Points has high safety (less false negative) because it uses pointcloud as input. Since points don’t have a predicted path, the path that moves in the direction normal to the path of ego vehicle is considered to be the predicted path of abstracted dynamic obstacle data. However, without proper adjustment of filter of points, it may detect a lot of points and it will result in very low availability. Method of ObjectWithoutPath has the characteristics of an intermediate of Object and Points.

File truncated at 100 lines see the full file

Changelog for package autoware_behavior_velocity_run_out_module

0.47.0 (2025-08-11)

• style(pre-commit): update to clang-format-20 (#11088) Co-authored-by: pre-commit-ci[bot] <66853113+pre-commit-ci[bot]@users.noreply.github.com>
• Contributors: Mete Fatih Cırıt

0.46.0 (2025-06-20)

0.45.0 (2025-05-22)

• Merge remote-tracking branch 'origin/main' into tmp/notbot/bump_version_base
• fix(behavior_velocity_planner): add missing header (#10561) Co-authored-by: pre-commit-ci[bot] <66853113+pre-commit-ci[bot]@users.noreply.github.com>
• feat(behavior_velocity_planner): only wait for the required subscriptions (#10546)
• Contributors: Masaki Baba, TaikiYamada4, Takayuki Murooka

0.44.2 (2025-06-10)

0.44.1 (2025-05-01)

0.44.0 (2025-04-18)

• Merge remote-tracking branch 'origin/main' into humble
• fix(planning): apply THROTTLE to frequent log (#10419)
• Contributors: Ryohsuke Mitsudome, Takayuki Murooka

0.43.0 (2025-03-21)

• Merge remote-tracking branch 'origin/main' into chore/bump-version-0.43

• chore: rename from [autoware.universe]{.title-ref} to [autoware_universe]{.title-ref} (#10306)

• fix(behavior_velocity_planner): planning factor integration (#10292)

  • fix: blind_spot
  • fix: crosswalk
  • fix: detection_area
  • fix: intersection
  • fix: no_drivable_lane
  • fix: no_stopping_area
  • fix: run_out
  • fix: stop_line
  • fix: traffic_light
  • fix: virtual_traffic_light

  * fix: walk_way ---------

• feat(Autoware_planning_factor_interface): replace tier4_msgs with autoware_internal_msgs (#10204)

• Contributors: Hayato Mizushima, Satoshi OTA, Yutaka Kondo, 心刚

0.42.0 (2025-03-03)

• Merge remote-tracking branch 'origin/main' into tmp/bot/bump_version_base

• feat(autoware_utils): replace autoware_universe_utils with autoware_utils (#10191)

• fix: add missing includes to autoware_universe_utils (#10091)

• fix(behavior_velocity_run_out_module): fix slow_down jerk filter (#10065)

• feat!: replace tier4_planning_msgs/PathWithLaneId with autoware_internal_planning_msgs/PathWithLaneId (#10023)

• feat(planning_test_manager): abstract message-specific functions (#9882)

  • abstract message-specific functions
  • include necessary header
  • adapt velocity_smoother to new test manager
  • adapt behavior_velocity_planner to new test manager
  • adapt path_optimizer to new test manager
  • fix output subscription
  • adapt behavior_path_planner to new test manager
  • adapt scenario_selector to new test manager
  • adapt freespace_planner to new test manager
  • adapt planning_validator to new test manager
  • adapt obstacle_stop_planner to new test manager

File truncated at 100 lines see the full file