Package Summary
| Version | 0.50.0 |
| License | Apache License 2.0 |
| Build type | AMENT_CMAKE |
| Use | RECOMMENDED |
Repository Summary
| Description | |
| Checkout URI | https://github.com/autowarefoundation/autoware_universe.git |
| VCS Type | git |
| VCS Version | main |
| Last Updated | 2026-02-25 |
| Dev Status | UNKNOWN |
| Released | UNRELEASED |
| Contributing |
Help Wanted (-)
Good First Issues (-) Pull Requests to Review (-) |
Package Description
Maintainers
- Kosuke Takeuchi
- Alqudah Mohammad
Authors
- Takamasa Horibe
- Takayuki Murooka
- Akihito OHSATO
- Tomohito ANDO
The autoware_freespace_planner
freespace_planner_node
freespace_planner_node is a global path planner node that plans trajectory
in the space having static/dynamic obstacles. This node is currently based on
Hybrid A* search algorithm in freespace_planning_algorithms package.
Other algorithms such as rrt* will be also added and selectable in the future.
Note Due to the constraint of trajectory following, the output trajectory will be split to include only the single direction path. In other words, the output trajectory doesn’t include both forward and backward trajectories at once.
Input topics
| Name | Type | Description |
|---|---|---|
~input/route |
autoware_planning_msgs::Route | route and goal pose |
~input/occupancy_grid |
nav_msgs::OccupancyGrid | costmap, for drivable areas |
~input/odometry |
nav_msgs::Odometry | vehicle velocity, for checking whether vehicle is stopped |
~input/scenario |
tier4_planning_msgs::Scenario | scenarios to be activated, for node activation |
Output topics
| Name | Type | Description |
|---|---|---|
~output/trajectory |
autoware_planning_msgs::Trajectory | trajectory to be followed |
is_completed |
bool (implemented as rosparam) | whether all split trajectory are published |
Output TFs
None
How to launch
- Write your remapping info in
freespace_planner.launchor add args when executingroslaunch roslaunch freespace_planner freespace_planner.launch
Parameters
{{json_to_markdown(“planning/autoware_freespace_planner/schema/freespace_planner.schema.json”)}}
Node parameters
| Parameter | Type | Description |
|---|---|---|
planning_algorithms |
string | algorithms used in the node |
vehicle_shape_margin_m |
float | collision margin in planning algorithm |
update_rate |
double | timer’s update rate |
waypoints_velocity |
double | velocity in output trajectory (currently, only constant velocity is supported) |
th_arrived_distance_m |
double | threshold distance to check if vehicle has arrived at the trajectory’s endpoint |
th_stopped_time_sec |
double | threshold time to check if vehicle is stopped |
th_stopped_velocity_mps |
double | threshold velocity to check if vehicle is stopped |
th_course_out_distance_m |
double | threshold distance to check if vehicle is out of course |
th_obstacle_time_sec |
double | threshold time to check if obstacle is on the trajectory |
vehicle_shape_margin_m |
double | vehicle margin |
replan_when_obstacle_found |
bool | whether replanning when obstacle has found on the trajectory |
replan_when_course_out |
bool | whether replanning when vehicle is out of course |
Planner common parameters
| Parameter | Type | Description |
|---|---|---|
time_limit |
double | time limit of planning |
maximum_turning_ratio |
double | max ratio of actual turning range to use |
turning_steps |
double | number of turning steps within turning range |
theta_size |
double | the number of angle’s discretization |
lateral_goal_range |
double | goal range of lateral position |
longitudinal_goal_range |
double | goal range of longitudinal position |
angle_goal_range |
double | goal range of angle |
curve_weight |
double | additional cost factor for curve actions |
reverse_weight |
double | additional cost factor for reverse actions |
direction_change_weight |
double | additional cost factor for switching direction |
obstacle_threshold |
double | threshold for regarding a certain grid as obstacle |
A* search parameters
| Parameter | Type | Description |
|---|---|---|
search_method |
string | method of searching, start to goal or vice versa |
only_behind_solutions |
bool | whether restricting the solutions to be behind the goal |
use_back |
bool | whether using backward trajectory |
adapt_expansion_distance |
bool | if true, adapt expansion distance based on environment |
expansion_distance |
double | length of expansion for node transitions |
near_goal_distance |
double | near goal distance threshold |
distance_heuristic_weight |
double | heuristic weight for estimating node’s cost |
smoothness_weight |
double | cost factor for change in curvature |
obstacle_distance_weight |
double | cost factor for distance to obstacle |
goal_lat_distance_weight |
double | cost factor for lateral distance from goal |
RRT* search parameters
| Parameter | Type | Description |
|---|---|---|
max planning time |
double | maximum planning time [msec] (used only when enable_update is set true) |
enable_update |
bool | whether update after feasible solution found until max_planning time elapse |
use_informed_sampling |
bool | Use informed RRT* (of Gammell et al.) |
neighbor_radius |
double | neighbor radius of RRT* algorithm |
File truncated at 100 lines see the full file
Changelog for package autoware_freespace_planner
0.50.0 (2026-02-14)
- Merge remote-tracking branch 'origin/main' into humble
- feat!: remove ROS 2 Galactic codes (#11905)
- Contributors: Ryohsuke Mitsudome
0.49.0 (2025-12-30)
-
Merge remote-tracking branch 'origin/main' into prepare-0.49.0-changelog
-
fix(freespace_planner): build testing failure (#11759)
-
fix: resolve clock type mismatch in tf2 lookups with simulation time (#11523)
* fix: resolve clock type mismatch in tf2 transform lookups Replace rclcpp::Time(0) with tf2::TimePointZero in lookupTransform calls to fix clock type conflicts when using simulation time. The issue:
- rclcpp::Time(0) creates a time with SYSTEM_TIME clock type
- When nodes run with use_sim_time:=true, transforms use ROS_TIME clock
- This causes clock type mismatch errors in tf2 lookups
- Error: "Lookup would require extrapolation into the past" The fix:
- tf2::TimePointZero is clock-type agnostic
- Correctly represents "get latest available transform"
- Also replaced rclcpp::Duration::from_seconds() with tf2::durationFromSec() This bug affects transform lookups in critical safety and planning components, causing runtime errors when simulation time is enabled. Affected packages:
- autoware_autonomous_emergency_braking
- autoware_planning_evaluator
- autoware_freespace_planner
* style(pre-commit): autofix ---------Co-authored-by: pre-commit-ci-lite[bot] <117423508+pre-commit-ci-lite[bot]@users.noreply.github.com> Co-authored-by: Shumpei Wakabayashi <<42209144+shmpwk@users.noreply.github.com>>
-
Contributors: Ryohsuke Mitsudome, Zulfaqar Azmi, ralwing
0.48.0 (2025-11-18)
- Merge remote-tracking branch 'origin/main' into humble
- feat(autoware_freespace_planner): utilize all 3 components of velocity (#11427) fix:the stopping speed judgments of freespace_planner and mission_planner are consistent, taking into account the speed in xyz direction Signed-off-by: yangzesong <<15340400289@163.com>> Co-authored-by: yangzesong <<15340400289@163.com>>
- Contributors: Ryohsuke Mitsudome
0.47.1 (2025-08-14)
0.47.0 (2025-08-11)
0.46.0 (2025-06-20)
0.45.0 (2025-05-22)
0.44.2 (2025-06-10)
0.44.1 (2025-05-01)
0.44.0 (2025-04-18)
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)
-
feat: adaption to ROS nodes guidelines about directory structure (#10268)
-
fix(planning): add missing exec_depend (#10134)
- fix(planning): add missing exec_depend
- fix find-pkg-share
* fix find-pkg-share ---------
-
Contributors: Hayato Mizushima, NorahXiong, Takagi, Isamu, Yutaka Kondo
File truncated at 100 lines see the full file
Package Dependencies
System Dependencies
Dependant Packages
| Name | Deps |
|---|---|
| tier4_planning_launch |
Launch files
- launch/freespace_planner.launch.xml
-
- input_route [default: input_route]
- input_occupancy_grid [default: input_occupancy_grid]
- input_scenario [default: input_scenario]
- input_odometry [default: /localization/kinematic_state]
- output_trajectory [default: output_trajectory]
- is_completed [default: is_completed]
- param_file [default: $(find-pkg-share autoware_freespace_planner)/config/freespace_planner.param.yaml]
- vehicle_info_param_file [default: $(find-pkg-share autoware_vehicle_info_utils)/config/vehicle_info.param.yaml]
Messages
Services
Plugins
Recent questions tagged autoware_freespace_planner at Robotics Stack Exchange
Package Summary
| Version | 0.50.0 |
| License | Apache License 2.0 |
| Build type | AMENT_CMAKE |
| Use | RECOMMENDED |
Repository Summary
| Description | |
| Checkout URI | https://github.com/autowarefoundation/autoware_universe.git |
| VCS Type | git |
| VCS Version | main |
| Last Updated | 2026-02-25 |
| Dev Status | UNKNOWN |
| Released | UNRELEASED |
| Contributing |
Help Wanted (-)
Good First Issues (-) Pull Requests to Review (-) |
Package Description
Maintainers
- Kosuke Takeuchi
- Alqudah Mohammad
Authors
- Takamasa Horibe
- Takayuki Murooka
- Akihito OHSATO
- Tomohito ANDO
The autoware_freespace_planner
freespace_planner_node
freespace_planner_node is a global path planner node that plans trajectory
in the space having static/dynamic obstacles. This node is currently based on
Hybrid A* search algorithm in freespace_planning_algorithms package.
Other algorithms such as rrt* will be also added and selectable in the future.
Note Due to the constraint of trajectory following, the output trajectory will be split to include only the single direction path. In other words, the output trajectory doesn’t include both forward and backward trajectories at once.
Input topics
| Name | Type | Description |
|---|---|---|
~input/route |
autoware_planning_msgs::Route | route and goal pose |
~input/occupancy_grid |
nav_msgs::OccupancyGrid | costmap, for drivable areas |
~input/odometry |
nav_msgs::Odometry | vehicle velocity, for checking whether vehicle is stopped |
~input/scenario |
tier4_planning_msgs::Scenario | scenarios to be activated, for node activation |
Output topics
| Name | Type | Description |
|---|---|---|
~output/trajectory |
autoware_planning_msgs::Trajectory | trajectory to be followed |
is_completed |
bool (implemented as rosparam) | whether all split trajectory are published |
Output TFs
None
How to launch
- Write your remapping info in
freespace_planner.launchor add args when executingroslaunch roslaunch freespace_planner freespace_planner.launch
Parameters
{{json_to_markdown(“planning/autoware_freespace_planner/schema/freespace_planner.schema.json”)}}
Node parameters
| Parameter | Type | Description |
|---|---|---|
planning_algorithms |
string | algorithms used in the node |
vehicle_shape_margin_m |
float | collision margin in planning algorithm |
update_rate |
double | timer’s update rate |
waypoints_velocity |
double | velocity in output trajectory (currently, only constant velocity is supported) |
th_arrived_distance_m |
double | threshold distance to check if vehicle has arrived at the trajectory’s endpoint |
th_stopped_time_sec |
double | threshold time to check if vehicle is stopped |
th_stopped_velocity_mps |
double | threshold velocity to check if vehicle is stopped |
th_course_out_distance_m |
double | threshold distance to check if vehicle is out of course |
th_obstacle_time_sec |
double | threshold time to check if obstacle is on the trajectory |
vehicle_shape_margin_m |
double | vehicle margin |
replan_when_obstacle_found |
bool | whether replanning when obstacle has found on the trajectory |
replan_when_course_out |
bool | whether replanning when vehicle is out of course |
Planner common parameters
| Parameter | Type | Description |
|---|---|---|
time_limit |
double | time limit of planning |
maximum_turning_ratio |
double | max ratio of actual turning range to use |
turning_steps |
double | number of turning steps within turning range |
theta_size |
double | the number of angle’s discretization |
lateral_goal_range |
double | goal range of lateral position |
longitudinal_goal_range |
double | goal range of longitudinal position |
angle_goal_range |
double | goal range of angle |
curve_weight |
double | additional cost factor for curve actions |
reverse_weight |
double | additional cost factor for reverse actions |
direction_change_weight |
double | additional cost factor for switching direction |
obstacle_threshold |
double | threshold for regarding a certain grid as obstacle |
A* search parameters
| Parameter | Type | Description |
|---|---|---|
search_method |
string | method of searching, start to goal or vice versa |
only_behind_solutions |
bool | whether restricting the solutions to be behind the goal |
use_back |
bool | whether using backward trajectory |
adapt_expansion_distance |
bool | if true, adapt expansion distance based on environment |
expansion_distance |
double | length of expansion for node transitions |
near_goal_distance |
double | near goal distance threshold |
distance_heuristic_weight |
double | heuristic weight for estimating node’s cost |
smoothness_weight |
double | cost factor for change in curvature |
obstacle_distance_weight |
double | cost factor for distance to obstacle |
goal_lat_distance_weight |
double | cost factor for lateral distance from goal |
RRT* search parameters
| Parameter | Type | Description |
|---|---|---|
max planning time |
double | maximum planning time [msec] (used only when enable_update is set true) |
enable_update |
bool | whether update after feasible solution found until max_planning time elapse |
use_informed_sampling |
bool | Use informed RRT* (of Gammell et al.) |
neighbor_radius |
double | neighbor radius of RRT* algorithm |
File truncated at 100 lines see the full file
Changelog for package autoware_freespace_planner
0.50.0 (2026-02-14)
- Merge remote-tracking branch 'origin/main' into humble
- feat!: remove ROS 2 Galactic codes (#11905)
- Contributors: Ryohsuke Mitsudome
0.49.0 (2025-12-30)
-
Merge remote-tracking branch 'origin/main' into prepare-0.49.0-changelog
-
fix(freespace_planner): build testing failure (#11759)
-
fix: resolve clock type mismatch in tf2 lookups with simulation time (#11523)
* fix: resolve clock type mismatch in tf2 transform lookups Replace rclcpp::Time(0) with tf2::TimePointZero in lookupTransform calls to fix clock type conflicts when using simulation time. The issue:
- rclcpp::Time(0) creates a time with SYSTEM_TIME clock type
- When nodes run with use_sim_time:=true, transforms use ROS_TIME clock
- This causes clock type mismatch errors in tf2 lookups
- Error: "Lookup would require extrapolation into the past" The fix:
- tf2::TimePointZero is clock-type agnostic
- Correctly represents "get latest available transform"
- Also replaced rclcpp::Duration::from_seconds() with tf2::durationFromSec() This bug affects transform lookups in critical safety and planning components, causing runtime errors when simulation time is enabled. Affected packages:
- autoware_autonomous_emergency_braking
- autoware_planning_evaluator
- autoware_freespace_planner
* style(pre-commit): autofix ---------Co-authored-by: pre-commit-ci-lite[bot] <117423508+pre-commit-ci-lite[bot]@users.noreply.github.com> Co-authored-by: Shumpei Wakabayashi <<42209144+shmpwk@users.noreply.github.com>>
-
Contributors: Ryohsuke Mitsudome, Zulfaqar Azmi, ralwing
0.48.0 (2025-11-18)
- Merge remote-tracking branch 'origin/main' into humble
- feat(autoware_freespace_planner): utilize all 3 components of velocity (#11427) fix:the stopping speed judgments of freespace_planner and mission_planner are consistent, taking into account the speed in xyz direction Signed-off-by: yangzesong <<15340400289@163.com>> Co-authored-by: yangzesong <<15340400289@163.com>>
- Contributors: Ryohsuke Mitsudome
0.47.1 (2025-08-14)
0.47.0 (2025-08-11)
0.46.0 (2025-06-20)
0.45.0 (2025-05-22)
0.44.2 (2025-06-10)
0.44.1 (2025-05-01)
0.44.0 (2025-04-18)
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)
-
feat: adaption to ROS nodes guidelines about directory structure (#10268)
-
fix(planning): add missing exec_depend (#10134)
- fix(planning): add missing exec_depend
- fix find-pkg-share
* fix find-pkg-share ---------
-
Contributors: Hayato Mizushima, NorahXiong, Takagi, Isamu, Yutaka Kondo
File truncated at 100 lines see the full file
Package Dependencies
System Dependencies
Dependant Packages
| Name | Deps |
|---|---|
| tier4_planning_launch |
Launch files
- launch/freespace_planner.launch.xml
-
- input_route [default: input_route]
- input_occupancy_grid [default: input_occupancy_grid]
- input_scenario [default: input_scenario]
- input_odometry [default: /localization/kinematic_state]
- output_trajectory [default: output_trajectory]
- is_completed [default: is_completed]
- param_file [default: $(find-pkg-share autoware_freespace_planner)/config/freespace_planner.param.yaml]
- vehicle_info_param_file [default: $(find-pkg-share autoware_vehicle_info_utils)/config/vehicle_info.param.yaml]
Messages
Services
Plugins
Recent questions tagged autoware_freespace_planner at Robotics Stack Exchange
Package Summary
| Version | 0.50.0 |
| License | Apache License 2.0 |
| Build type | AMENT_CMAKE |
| Use | RECOMMENDED |
Repository Summary
| Description | |
| Checkout URI | https://github.com/autowarefoundation/autoware_universe.git |
| VCS Type | git |
| VCS Version | main |
| Last Updated | 2026-02-25 |
| Dev Status | UNKNOWN |
| Released | UNRELEASED |
| Contributing |
Help Wanted (-)
Good First Issues (-) Pull Requests to Review (-) |
Package Description
Maintainers
- Kosuke Takeuchi
- Alqudah Mohammad
Authors
- Takamasa Horibe
- Takayuki Murooka
- Akihito OHSATO
- Tomohito ANDO
The autoware_freespace_planner
freespace_planner_node
freespace_planner_node is a global path planner node that plans trajectory
in the space having static/dynamic obstacles. This node is currently based on
Hybrid A* search algorithm in freespace_planning_algorithms package.
Other algorithms such as rrt* will be also added and selectable in the future.
Note Due to the constraint of trajectory following, the output trajectory will be split to include only the single direction path. In other words, the output trajectory doesn’t include both forward and backward trajectories at once.
Input topics
| Name | Type | Description |
|---|---|---|
~input/route |
autoware_planning_msgs::Route | route and goal pose |
~input/occupancy_grid |
nav_msgs::OccupancyGrid | costmap, for drivable areas |
~input/odometry |
nav_msgs::Odometry | vehicle velocity, for checking whether vehicle is stopped |
~input/scenario |
tier4_planning_msgs::Scenario | scenarios to be activated, for node activation |
Output topics
| Name | Type | Description |
|---|---|---|
~output/trajectory |
autoware_planning_msgs::Trajectory | trajectory to be followed |
is_completed |
bool (implemented as rosparam) | whether all split trajectory are published |
Output TFs
None
How to launch
- Write your remapping info in
freespace_planner.launchor add args when executingroslaunch roslaunch freespace_planner freespace_planner.launch
Parameters
{{json_to_markdown(“planning/autoware_freespace_planner/schema/freespace_planner.schema.json”)}}
Node parameters
| Parameter | Type | Description |
|---|---|---|
planning_algorithms |
string | algorithms used in the node |
vehicle_shape_margin_m |
float | collision margin in planning algorithm |
update_rate |
double | timer’s update rate |
waypoints_velocity |
double | velocity in output trajectory (currently, only constant velocity is supported) |
th_arrived_distance_m |
double | threshold distance to check if vehicle has arrived at the trajectory’s endpoint |
th_stopped_time_sec |
double | threshold time to check if vehicle is stopped |
th_stopped_velocity_mps |
double | threshold velocity to check if vehicle is stopped |
th_course_out_distance_m |
double | threshold distance to check if vehicle is out of course |
th_obstacle_time_sec |
double | threshold time to check if obstacle is on the trajectory |
vehicle_shape_margin_m |
double | vehicle margin |
replan_when_obstacle_found |
bool | whether replanning when obstacle has found on the trajectory |
replan_when_course_out |
bool | whether replanning when vehicle is out of course |
Planner common parameters
| Parameter | Type | Description |
|---|---|---|
time_limit |
double | time limit of planning |
maximum_turning_ratio |
double | max ratio of actual turning range to use |
turning_steps |
double | number of turning steps within turning range |
theta_size |
double | the number of angle’s discretization |
lateral_goal_range |
double | goal range of lateral position |
longitudinal_goal_range |
double | goal range of longitudinal position |
angle_goal_range |
double | goal range of angle |
curve_weight |
double | additional cost factor for curve actions |
reverse_weight |
double | additional cost factor for reverse actions |
direction_change_weight |
double | additional cost factor for switching direction |
obstacle_threshold |
double | threshold for regarding a certain grid as obstacle |
A* search parameters
| Parameter | Type | Description |
|---|---|---|
search_method |
string | method of searching, start to goal or vice versa |
only_behind_solutions |
bool | whether restricting the solutions to be behind the goal |
use_back |
bool | whether using backward trajectory |
adapt_expansion_distance |
bool | if true, adapt expansion distance based on environment |
expansion_distance |
double | length of expansion for node transitions |
near_goal_distance |
double | near goal distance threshold |
distance_heuristic_weight |
double | heuristic weight for estimating node’s cost |
smoothness_weight |
double | cost factor for change in curvature |
obstacle_distance_weight |
double | cost factor for distance to obstacle |
goal_lat_distance_weight |
double | cost factor for lateral distance from goal |
RRT* search parameters
| Parameter | Type | Description |
|---|---|---|
max planning time |
double | maximum planning time [msec] (used only when enable_update is set true) |
enable_update |
bool | whether update after feasible solution found until max_planning time elapse |
use_informed_sampling |
bool | Use informed RRT* (of Gammell et al.) |
neighbor_radius |
double | neighbor radius of RRT* algorithm |
File truncated at 100 lines see the full file
Changelog for package autoware_freespace_planner
0.50.0 (2026-02-14)
- Merge remote-tracking branch 'origin/main' into humble
- feat!: remove ROS 2 Galactic codes (#11905)
- Contributors: Ryohsuke Mitsudome
0.49.0 (2025-12-30)
-
Merge remote-tracking branch 'origin/main' into prepare-0.49.0-changelog
-
fix(freespace_planner): build testing failure (#11759)
-
fix: resolve clock type mismatch in tf2 lookups with simulation time (#11523)
* fix: resolve clock type mismatch in tf2 transform lookups Replace rclcpp::Time(0) with tf2::TimePointZero in lookupTransform calls to fix clock type conflicts when using simulation time. The issue:
- rclcpp::Time(0) creates a time with SYSTEM_TIME clock type
- When nodes run with use_sim_time:=true, transforms use ROS_TIME clock
- This causes clock type mismatch errors in tf2 lookups
- Error: "Lookup would require extrapolation into the past" The fix:
- tf2::TimePointZero is clock-type agnostic
- Correctly represents "get latest available transform"
- Also replaced rclcpp::Duration::from_seconds() with tf2::durationFromSec() This bug affects transform lookups in critical safety and planning components, causing runtime errors when simulation time is enabled. Affected packages:
- autoware_autonomous_emergency_braking
- autoware_planning_evaluator
- autoware_freespace_planner
* style(pre-commit): autofix ---------Co-authored-by: pre-commit-ci-lite[bot] <117423508+pre-commit-ci-lite[bot]@users.noreply.github.com> Co-authored-by: Shumpei Wakabayashi <<42209144+shmpwk@users.noreply.github.com>>
-
Contributors: Ryohsuke Mitsudome, Zulfaqar Azmi, ralwing
0.48.0 (2025-11-18)
- Merge remote-tracking branch 'origin/main' into humble
- feat(autoware_freespace_planner): utilize all 3 components of velocity (#11427) fix:the stopping speed judgments of freespace_planner and mission_planner are consistent, taking into account the speed in xyz direction Signed-off-by: yangzesong <<15340400289@163.com>> Co-authored-by: yangzesong <<15340400289@163.com>>
- Contributors: Ryohsuke Mitsudome
0.47.1 (2025-08-14)
0.47.0 (2025-08-11)
0.46.0 (2025-06-20)
0.45.0 (2025-05-22)
0.44.2 (2025-06-10)
0.44.1 (2025-05-01)
0.44.0 (2025-04-18)
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)
-
feat: adaption to ROS nodes guidelines about directory structure (#10268)
-
fix(planning): add missing exec_depend (#10134)
- fix(planning): add missing exec_depend
- fix find-pkg-share
* fix find-pkg-share ---------
-
Contributors: Hayato Mizushima, NorahXiong, Takagi, Isamu, Yutaka Kondo
File truncated at 100 lines see the full file
Package Dependencies
System Dependencies
Dependant Packages
| Name | Deps |
|---|---|
| tier4_planning_launch |
Launch files
- launch/freespace_planner.launch.xml
-
- input_route [default: input_route]
- input_occupancy_grid [default: input_occupancy_grid]
- input_scenario [default: input_scenario]
- input_odometry [default: /localization/kinematic_state]
- output_trajectory [default: output_trajectory]
- is_completed [default: is_completed]
- param_file [default: $(find-pkg-share autoware_freespace_planner)/config/freespace_planner.param.yaml]
- vehicle_info_param_file [default: $(find-pkg-share autoware_vehicle_info_utils)/config/vehicle_info.param.yaml]
Messages
Services
Plugins
Recent questions tagged autoware_freespace_planner at Robotics Stack Exchange
Package Summary
| Version | 0.50.0 |
| License | Apache License 2.0 |
| Build type | AMENT_CMAKE |
| Use | RECOMMENDED |
Repository Summary
| Description | |
| Checkout URI | https://github.com/autowarefoundation/autoware_universe.git |
| VCS Type | git |
| VCS Version | main |
| Last Updated | 2026-02-25 |
| Dev Status | UNKNOWN |
| Released | UNRELEASED |
| Contributing |
Help Wanted (-)
Good First Issues (-) Pull Requests to Review (-) |
Package Description
Maintainers
- Kosuke Takeuchi
- Alqudah Mohammad
Authors
- Takamasa Horibe
- Takayuki Murooka
- Akihito OHSATO
- Tomohito ANDO
The autoware_freespace_planner
freespace_planner_node
freespace_planner_node is a global path planner node that plans trajectory
in the space having static/dynamic obstacles. This node is currently based on
Hybrid A* search algorithm in freespace_planning_algorithms package.
Other algorithms such as rrt* will be also added and selectable in the future.
Note Due to the constraint of trajectory following, the output trajectory will be split to include only the single direction path. In other words, the output trajectory doesn’t include both forward and backward trajectories at once.
Input topics
| Name | Type | Description |
|---|---|---|
~input/route |
autoware_planning_msgs::Route | route and goal pose |
~input/occupancy_grid |
nav_msgs::OccupancyGrid | costmap, for drivable areas |
~input/odometry |
nav_msgs::Odometry | vehicle velocity, for checking whether vehicle is stopped |
~input/scenario |
tier4_planning_msgs::Scenario | scenarios to be activated, for node activation |
Output topics
| Name | Type | Description |
|---|---|---|
~output/trajectory |
autoware_planning_msgs::Trajectory | trajectory to be followed |
is_completed |
bool (implemented as rosparam) | whether all split trajectory are published |
Output TFs
None
How to launch
- Write your remapping info in
freespace_planner.launchor add args when executingroslaunch roslaunch freespace_planner freespace_planner.launch
Parameters
{{json_to_markdown(“planning/autoware_freespace_planner/schema/freespace_planner.schema.json”)}}
Node parameters
| Parameter | Type | Description |
|---|---|---|
planning_algorithms |
string | algorithms used in the node |
vehicle_shape_margin_m |
float | collision margin in planning algorithm |
update_rate |
double | timer’s update rate |
waypoints_velocity |
double | velocity in output trajectory (currently, only constant velocity is supported) |
th_arrived_distance_m |
double | threshold distance to check if vehicle has arrived at the trajectory’s endpoint |
th_stopped_time_sec |
double | threshold time to check if vehicle is stopped |
th_stopped_velocity_mps |
double | threshold velocity to check if vehicle is stopped |
th_course_out_distance_m |
double | threshold distance to check if vehicle is out of course |
th_obstacle_time_sec |
double | threshold time to check if obstacle is on the trajectory |
vehicle_shape_margin_m |
double | vehicle margin |
replan_when_obstacle_found |
bool | whether replanning when obstacle has found on the trajectory |
replan_when_course_out |
bool | whether replanning when vehicle is out of course |
Planner common parameters
| Parameter | Type | Description |
|---|---|---|
time_limit |
double | time limit of planning |
maximum_turning_ratio |
double | max ratio of actual turning range to use |
turning_steps |
double | number of turning steps within turning range |
theta_size |
double | the number of angle’s discretization |
lateral_goal_range |
double | goal range of lateral position |
longitudinal_goal_range |
double | goal range of longitudinal position |
angle_goal_range |
double | goal range of angle |
curve_weight |
double | additional cost factor for curve actions |
reverse_weight |
double | additional cost factor for reverse actions |
direction_change_weight |
double | additional cost factor for switching direction |
obstacle_threshold |
double | threshold for regarding a certain grid as obstacle |
A* search parameters
| Parameter | Type | Description |
|---|---|---|
search_method |
string | method of searching, start to goal or vice versa |
only_behind_solutions |
bool | whether restricting the solutions to be behind the goal |
use_back |
bool | whether using backward trajectory |
adapt_expansion_distance |
bool | if true, adapt expansion distance based on environment |
expansion_distance |
double | length of expansion for node transitions |
near_goal_distance |
double | near goal distance threshold |
distance_heuristic_weight |
double | heuristic weight for estimating node’s cost |
smoothness_weight |
double | cost factor for change in curvature |
obstacle_distance_weight |
double | cost factor for distance to obstacle |
goal_lat_distance_weight |
double | cost factor for lateral distance from goal |
RRT* search parameters
| Parameter | Type | Description |
|---|---|---|
max planning time |
double | maximum planning time [msec] (used only when enable_update is set true) |
enable_update |
bool | whether update after feasible solution found until max_planning time elapse |
use_informed_sampling |
bool | Use informed RRT* (of Gammell et al.) |
neighbor_radius |
double | neighbor radius of RRT* algorithm |
File truncated at 100 lines see the full file
Changelog for package autoware_freespace_planner
0.50.0 (2026-02-14)
- Merge remote-tracking branch 'origin/main' into humble
- feat!: remove ROS 2 Galactic codes (#11905)
- Contributors: Ryohsuke Mitsudome
0.49.0 (2025-12-30)
-
Merge remote-tracking branch 'origin/main' into prepare-0.49.0-changelog
-
fix(freespace_planner): build testing failure (#11759)
-
fix: resolve clock type mismatch in tf2 lookups with simulation time (#11523)
* fix: resolve clock type mismatch in tf2 transform lookups Replace rclcpp::Time(0) with tf2::TimePointZero in lookupTransform calls to fix clock type conflicts when using simulation time. The issue:
- rclcpp::Time(0) creates a time with SYSTEM_TIME clock type
- When nodes run with use_sim_time:=true, transforms use ROS_TIME clock
- This causes clock type mismatch errors in tf2 lookups
- Error: "Lookup would require extrapolation into the past" The fix:
- tf2::TimePointZero is clock-type agnostic
- Correctly represents "get latest available transform"
- Also replaced rclcpp::Duration::from_seconds() with tf2::durationFromSec() This bug affects transform lookups in critical safety and planning components, causing runtime errors when simulation time is enabled. Affected packages:
- autoware_autonomous_emergency_braking
- autoware_planning_evaluator
- autoware_freespace_planner
* style(pre-commit): autofix ---------Co-authored-by: pre-commit-ci-lite[bot] <117423508+pre-commit-ci-lite[bot]@users.noreply.github.com> Co-authored-by: Shumpei Wakabayashi <<42209144+shmpwk@users.noreply.github.com>>
-
Contributors: Ryohsuke Mitsudome, Zulfaqar Azmi, ralwing
0.48.0 (2025-11-18)
- Merge remote-tracking branch 'origin/main' into humble
- feat(autoware_freespace_planner): utilize all 3 components of velocity (#11427) fix:the stopping speed judgments of freespace_planner and mission_planner are consistent, taking into account the speed in xyz direction Signed-off-by: yangzesong <<15340400289@163.com>> Co-authored-by: yangzesong <<15340400289@163.com>>
- Contributors: Ryohsuke Mitsudome
0.47.1 (2025-08-14)
0.47.0 (2025-08-11)
0.46.0 (2025-06-20)
0.45.0 (2025-05-22)
0.44.2 (2025-06-10)
0.44.1 (2025-05-01)
0.44.0 (2025-04-18)
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)
-
feat: adaption to ROS nodes guidelines about directory structure (#10268)
-
fix(planning): add missing exec_depend (#10134)
- fix(planning): add missing exec_depend
- fix find-pkg-share
* fix find-pkg-share ---------
-
Contributors: Hayato Mizushima, NorahXiong, Takagi, Isamu, Yutaka Kondo
File truncated at 100 lines see the full file
Package Dependencies
System Dependencies
Dependant Packages
| Name | Deps |
|---|---|
| tier4_planning_launch |
Launch files
- launch/freespace_planner.launch.xml
-
- input_route [default: input_route]
- input_occupancy_grid [default: input_occupancy_grid]
- input_scenario [default: input_scenario]
- input_odometry [default: /localization/kinematic_state]
- output_trajectory [default: output_trajectory]
- is_completed [default: is_completed]
- param_file [default: $(find-pkg-share autoware_freespace_planner)/config/freespace_planner.param.yaml]
- vehicle_info_param_file [default: $(find-pkg-share autoware_vehicle_info_utils)/config/vehicle_info.param.yaml]
Messages
Services
Plugins
Recent questions tagged autoware_freespace_planner at Robotics Stack Exchange
Package Summary
| Version | 0.50.0 |
| License | Apache License 2.0 |
| Build type | AMENT_CMAKE |
| Use | RECOMMENDED |
Repository Summary
| Description | |
| Checkout URI | https://github.com/autowarefoundation/autoware_universe.git |
| VCS Type | git |
| VCS Version | main |
| Last Updated | 2026-02-25 |
| Dev Status | UNKNOWN |
| Released | UNRELEASED |
| Contributing |
Help Wanted (-)
Good First Issues (-) Pull Requests to Review (-) |
Package Description
Maintainers
- Kosuke Takeuchi
- Alqudah Mohammad
Authors
- Takamasa Horibe
- Takayuki Murooka
- Akihito OHSATO
- Tomohito ANDO
The autoware_freespace_planner
freespace_planner_node
freespace_planner_node is a global path planner node that plans trajectory
in the space having static/dynamic obstacles. This node is currently based on
Hybrid A* search algorithm in freespace_planning_algorithms package.
Other algorithms such as rrt* will be also added and selectable in the future.
Note Due to the constraint of trajectory following, the output trajectory will be split to include only the single direction path. In other words, the output trajectory doesn’t include both forward and backward trajectories at once.
Input topics
| Name | Type | Description |
|---|---|---|
~input/route |
autoware_planning_msgs::Route | route and goal pose |
~input/occupancy_grid |
nav_msgs::OccupancyGrid | costmap, for drivable areas |
~input/odometry |
nav_msgs::Odometry | vehicle velocity, for checking whether vehicle is stopped |
~input/scenario |
tier4_planning_msgs::Scenario | scenarios to be activated, for node activation |
Output topics
| Name | Type | Description |
|---|---|---|
~output/trajectory |
autoware_planning_msgs::Trajectory | trajectory to be followed |
is_completed |
bool (implemented as rosparam) | whether all split trajectory are published |
Output TFs
None
How to launch
- Write your remapping info in
freespace_planner.launchor add args when executingroslaunch roslaunch freespace_planner freespace_planner.launch
Parameters
{{json_to_markdown(“planning/autoware_freespace_planner/schema/freespace_planner.schema.json”)}}
Node parameters
| Parameter | Type | Description |
|---|---|---|
planning_algorithms |
string | algorithms used in the node |
vehicle_shape_margin_m |
float | collision margin in planning algorithm |
update_rate |
double | timer’s update rate |
waypoints_velocity |
double | velocity in output trajectory (currently, only constant velocity is supported) |
th_arrived_distance_m |
double | threshold distance to check if vehicle has arrived at the trajectory’s endpoint |
th_stopped_time_sec |
double | threshold time to check if vehicle is stopped |
th_stopped_velocity_mps |
double | threshold velocity to check if vehicle is stopped |
th_course_out_distance_m |
double | threshold distance to check if vehicle is out of course |
th_obstacle_time_sec |
double | threshold time to check if obstacle is on the trajectory |
vehicle_shape_margin_m |
double | vehicle margin |
replan_when_obstacle_found |
bool | whether replanning when obstacle has found on the trajectory |
replan_when_course_out |
bool | whether replanning when vehicle is out of course |
Planner common parameters
| Parameter | Type | Description |
|---|---|---|
time_limit |
double | time limit of planning |
maximum_turning_ratio |
double | max ratio of actual turning range to use |
turning_steps |
double | number of turning steps within turning range |
theta_size |
double | the number of angle’s discretization |
lateral_goal_range |
double | goal range of lateral position |
longitudinal_goal_range |
double | goal range of longitudinal position |
angle_goal_range |
double | goal range of angle |
curve_weight |
double | additional cost factor for curve actions |
reverse_weight |
double | additional cost factor for reverse actions |
direction_change_weight |
double | additional cost factor for switching direction |
obstacle_threshold |
double | threshold for regarding a certain grid as obstacle |
A* search parameters
| Parameter | Type | Description |
|---|---|---|
search_method |
string | method of searching, start to goal or vice versa |
only_behind_solutions |
bool | whether restricting the solutions to be behind the goal |
use_back |
bool | whether using backward trajectory |
adapt_expansion_distance |
bool | if true, adapt expansion distance based on environment |
expansion_distance |
double | length of expansion for node transitions |
near_goal_distance |
double | near goal distance threshold |
distance_heuristic_weight |
double | heuristic weight for estimating node’s cost |
smoothness_weight |
double | cost factor for change in curvature |
obstacle_distance_weight |
double | cost factor for distance to obstacle |
goal_lat_distance_weight |
double | cost factor for lateral distance from goal |
RRT* search parameters
| Parameter | Type | Description |
|---|---|---|
max planning time |
double | maximum planning time [msec] (used only when enable_update is set true) |
enable_update |
bool | whether update after feasible solution found until max_planning time elapse |
use_informed_sampling |
bool | Use informed RRT* (of Gammell et al.) |
neighbor_radius |
double | neighbor radius of RRT* algorithm |
File truncated at 100 lines see the full file
Changelog for package autoware_freespace_planner
0.50.0 (2026-02-14)
- Merge remote-tracking branch 'origin/main' into humble
- feat!: remove ROS 2 Galactic codes (#11905)
- Contributors: Ryohsuke Mitsudome
0.49.0 (2025-12-30)
-
Merge remote-tracking branch 'origin/main' into prepare-0.49.0-changelog
-
fix(freespace_planner): build testing failure (#11759)
-
fix: resolve clock type mismatch in tf2 lookups with simulation time (#11523)
* fix: resolve clock type mismatch in tf2 transform lookups Replace rclcpp::Time(0) with tf2::TimePointZero in lookupTransform calls to fix clock type conflicts when using simulation time. The issue:
- rclcpp::Time(0) creates a time with SYSTEM_TIME clock type
- When nodes run with use_sim_time:=true, transforms use ROS_TIME clock
- This causes clock type mismatch errors in tf2 lookups
- Error: "Lookup would require extrapolation into the past" The fix:
- tf2::TimePointZero is clock-type agnostic
- Correctly represents "get latest available transform"
- Also replaced rclcpp::Duration::from_seconds() with tf2::durationFromSec() This bug affects transform lookups in critical safety and planning components, causing runtime errors when simulation time is enabled. Affected packages:
- autoware_autonomous_emergency_braking
- autoware_planning_evaluator
- autoware_freespace_planner
* style(pre-commit): autofix ---------Co-authored-by: pre-commit-ci-lite[bot] <117423508+pre-commit-ci-lite[bot]@users.noreply.github.com> Co-authored-by: Shumpei Wakabayashi <<42209144+shmpwk@users.noreply.github.com>>
-
Contributors: Ryohsuke Mitsudome, Zulfaqar Azmi, ralwing
0.48.0 (2025-11-18)
- Merge remote-tracking branch 'origin/main' into humble
- feat(autoware_freespace_planner): utilize all 3 components of velocity (#11427) fix:the stopping speed judgments of freespace_planner and mission_planner are consistent, taking into account the speed in xyz direction Signed-off-by: yangzesong <<15340400289@163.com>> Co-authored-by: yangzesong <<15340400289@163.com>>
- Contributors: Ryohsuke Mitsudome
0.47.1 (2025-08-14)
0.47.0 (2025-08-11)
0.46.0 (2025-06-20)
0.45.0 (2025-05-22)
0.44.2 (2025-06-10)
0.44.1 (2025-05-01)
0.44.0 (2025-04-18)
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)
-
feat: adaption to ROS nodes guidelines about directory structure (#10268)
-
fix(planning): add missing exec_depend (#10134)
- fix(planning): add missing exec_depend
- fix find-pkg-share
* fix find-pkg-share ---------
-
Contributors: Hayato Mizushima, NorahXiong, Takagi, Isamu, Yutaka Kondo
File truncated at 100 lines see the full file
Package Dependencies
System Dependencies
Dependant Packages
| Name | Deps |
|---|---|
| tier4_planning_launch |
Launch files
- launch/freespace_planner.launch.xml
-
- input_route [default: input_route]
- input_occupancy_grid [default: input_occupancy_grid]
- input_scenario [default: input_scenario]
- input_odometry [default: /localization/kinematic_state]
- output_trajectory [default: output_trajectory]
- is_completed [default: is_completed]
- param_file [default: $(find-pkg-share autoware_freespace_planner)/config/freespace_planner.param.yaml]
- vehicle_info_param_file [default: $(find-pkg-share autoware_vehicle_info_utils)/config/vehicle_info.param.yaml]
Messages
Services
Plugins
Recent questions tagged autoware_freespace_planner at Robotics Stack Exchange
Package Summary
| Version | 0.50.0 |
| License | Apache License 2.0 |
| Build type | AMENT_CMAKE |
| Use | RECOMMENDED |
Repository Summary
| Description | |
| Checkout URI | https://github.com/autowarefoundation/autoware_universe.git |
| VCS Type | git |
| VCS Version | main |
| Last Updated | 2026-02-25 |
| Dev Status | UNKNOWN |
| Released | UNRELEASED |
| Contributing |
Help Wanted (-)
Good First Issues (-) Pull Requests to Review (-) |
Package Description
Maintainers
- Kosuke Takeuchi
- Alqudah Mohammad
Authors
- Takamasa Horibe
- Takayuki Murooka
- Akihito OHSATO
- Tomohito ANDO
The autoware_freespace_planner
freespace_planner_node
freespace_planner_node is a global path planner node that plans trajectory
in the space having static/dynamic obstacles. This node is currently based on
Hybrid A* search algorithm in freespace_planning_algorithms package.
Other algorithms such as rrt* will be also added and selectable in the future.
Note Due to the constraint of trajectory following, the output trajectory will be split to include only the single direction path. In other words, the output trajectory doesn’t include both forward and backward trajectories at once.
Input topics
| Name | Type | Description |
|---|---|---|
~input/route |
autoware_planning_msgs::Route | route and goal pose |
~input/occupancy_grid |
nav_msgs::OccupancyGrid | costmap, for drivable areas |
~input/odometry |
nav_msgs::Odometry | vehicle velocity, for checking whether vehicle is stopped |
~input/scenario |
tier4_planning_msgs::Scenario | scenarios to be activated, for node activation |
Output topics
| Name | Type | Description |
|---|---|---|
~output/trajectory |
autoware_planning_msgs::Trajectory | trajectory to be followed |
is_completed |
bool (implemented as rosparam) | whether all split trajectory are published |
Output TFs
None
How to launch
- Write your remapping info in
freespace_planner.launchor add args when executingroslaunch roslaunch freespace_planner freespace_planner.launch
Parameters
{{json_to_markdown(“planning/autoware_freespace_planner/schema/freespace_planner.schema.json”)}}
Node parameters
| Parameter | Type | Description |
|---|---|---|
planning_algorithms |
string | algorithms used in the node |
vehicle_shape_margin_m |
float | collision margin in planning algorithm |
update_rate |
double | timer’s update rate |
waypoints_velocity |
double | velocity in output trajectory (currently, only constant velocity is supported) |
th_arrived_distance_m |
double | threshold distance to check if vehicle has arrived at the trajectory’s endpoint |
th_stopped_time_sec |
double | threshold time to check if vehicle is stopped |
th_stopped_velocity_mps |
double | threshold velocity to check if vehicle is stopped |
th_course_out_distance_m |
double | threshold distance to check if vehicle is out of course |
th_obstacle_time_sec |
double | threshold time to check if obstacle is on the trajectory |
vehicle_shape_margin_m |
double | vehicle margin |
replan_when_obstacle_found |
bool | whether replanning when obstacle has found on the trajectory |
replan_when_course_out |
bool | whether replanning when vehicle is out of course |
Planner common parameters
| Parameter | Type | Description |
|---|---|---|
time_limit |
double | time limit of planning |
maximum_turning_ratio |
double | max ratio of actual turning range to use |
turning_steps |
double | number of turning steps within turning range |
theta_size |
double | the number of angle’s discretization |
lateral_goal_range |
double | goal range of lateral position |
longitudinal_goal_range |
double | goal range of longitudinal position |
angle_goal_range |
double | goal range of angle |
curve_weight |
double | additional cost factor for curve actions |
reverse_weight |
double | additional cost factor for reverse actions |
direction_change_weight |
double | additional cost factor for switching direction |
obstacle_threshold |
double | threshold for regarding a certain grid as obstacle |
A* search parameters
| Parameter | Type | Description |
|---|---|---|
search_method |
string | method of searching, start to goal or vice versa |
only_behind_solutions |
bool | whether restricting the solutions to be behind the goal |
use_back |
bool | whether using backward trajectory |
adapt_expansion_distance |
bool | if true, adapt expansion distance based on environment |
expansion_distance |
double | length of expansion for node transitions |
near_goal_distance |
double | near goal distance threshold |
distance_heuristic_weight |
double | heuristic weight for estimating node’s cost |
smoothness_weight |
double | cost factor for change in curvature |
obstacle_distance_weight |
double | cost factor for distance to obstacle |
goal_lat_distance_weight |
double | cost factor for lateral distance from goal |
RRT* search parameters
| Parameter | Type | Description |
|---|---|---|
max planning time |
double | maximum planning time [msec] (used only when enable_update is set true) |
enable_update |
bool | whether update after feasible solution found until max_planning time elapse |
use_informed_sampling |
bool | Use informed RRT* (of Gammell et al.) |
neighbor_radius |
double | neighbor radius of RRT* algorithm |
File truncated at 100 lines see the full file
Changelog for package autoware_freespace_planner
0.50.0 (2026-02-14)
- Merge remote-tracking branch 'origin/main' into humble
- feat!: remove ROS 2 Galactic codes (#11905)
- Contributors: Ryohsuke Mitsudome
0.49.0 (2025-12-30)
-
Merge remote-tracking branch 'origin/main' into prepare-0.49.0-changelog
-
fix(freespace_planner): build testing failure (#11759)
-
fix: resolve clock type mismatch in tf2 lookups with simulation time (#11523)
* fix: resolve clock type mismatch in tf2 transform lookups Replace rclcpp::Time(0) with tf2::TimePointZero in lookupTransform calls to fix clock type conflicts when using simulation time. The issue:
- rclcpp::Time(0) creates a time with SYSTEM_TIME clock type
- When nodes run with use_sim_time:=true, transforms use ROS_TIME clock
- This causes clock type mismatch errors in tf2 lookups
- Error: "Lookup would require extrapolation into the past" The fix:
- tf2::TimePointZero is clock-type agnostic
- Correctly represents "get latest available transform"
- Also replaced rclcpp::Duration::from_seconds() with tf2::durationFromSec() This bug affects transform lookups in critical safety and planning components, causing runtime errors when simulation time is enabled. Affected packages:
- autoware_autonomous_emergency_braking
- autoware_planning_evaluator
- autoware_freespace_planner
* style(pre-commit): autofix ---------Co-authored-by: pre-commit-ci-lite[bot] <117423508+pre-commit-ci-lite[bot]@users.noreply.github.com> Co-authored-by: Shumpei Wakabayashi <<42209144+shmpwk@users.noreply.github.com>>
-
Contributors: Ryohsuke Mitsudome, Zulfaqar Azmi, ralwing
0.48.0 (2025-11-18)
- Merge remote-tracking branch 'origin/main' into humble
- feat(autoware_freespace_planner): utilize all 3 components of velocity (#11427) fix:the stopping speed judgments of freespace_planner and mission_planner are consistent, taking into account the speed in xyz direction Signed-off-by: yangzesong <<15340400289@163.com>> Co-authored-by: yangzesong <<15340400289@163.com>>
- Contributors: Ryohsuke Mitsudome
0.47.1 (2025-08-14)
0.47.0 (2025-08-11)
0.46.0 (2025-06-20)
0.45.0 (2025-05-22)
0.44.2 (2025-06-10)
0.44.1 (2025-05-01)
0.44.0 (2025-04-18)
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)
-
feat: adaption to ROS nodes guidelines about directory structure (#10268)
-
fix(planning): add missing exec_depend (#10134)
- fix(planning): add missing exec_depend
- fix find-pkg-share
* fix find-pkg-share ---------
-
Contributors: Hayato Mizushima, NorahXiong, Takagi, Isamu, Yutaka Kondo
File truncated at 100 lines see the full file
Package Dependencies
System Dependencies
Dependant Packages
| Name | Deps |
|---|---|
| tier4_planning_launch |
Launch files
- launch/freespace_planner.launch.xml
-
- input_route [default: input_route]
- input_occupancy_grid [default: input_occupancy_grid]
- input_scenario [default: input_scenario]
- input_odometry [default: /localization/kinematic_state]
- output_trajectory [default: output_trajectory]
- is_completed [default: is_completed]
- param_file [default: $(find-pkg-share autoware_freespace_planner)/config/freespace_planner.param.yaml]
- vehicle_info_param_file [default: $(find-pkg-share autoware_vehicle_info_utils)/config/vehicle_info.param.yaml]
Messages
Services
Plugins
Recent questions tagged autoware_freespace_planner at Robotics Stack Exchange
Package Summary
| Version | 0.50.0 |
| License | Apache License 2.0 |
| Build type | AMENT_CMAKE |
| Use | RECOMMENDED |
Repository Summary
| Description | |
| Checkout URI | https://github.com/autowarefoundation/autoware_universe.git |
| VCS Type | git |
| VCS Version | main |
| Last Updated | 2026-02-25 |
| Dev Status | UNKNOWN |
| Released | UNRELEASED |
| Contributing |
Help Wanted (-)
Good First Issues (-) Pull Requests to Review (-) |
Package Description
Maintainers
- Kosuke Takeuchi
- Alqudah Mohammad
Authors
- Takamasa Horibe
- Takayuki Murooka
- Akihito OHSATO
- Tomohito ANDO
The autoware_freespace_planner
freespace_planner_node
freespace_planner_node is a global path planner node that plans trajectory
in the space having static/dynamic obstacles. This node is currently based on
Hybrid A* search algorithm in freespace_planning_algorithms package.
Other algorithms such as rrt* will be also added and selectable in the future.
Note Due to the constraint of trajectory following, the output trajectory will be split to include only the single direction path. In other words, the output trajectory doesn’t include both forward and backward trajectories at once.
Input topics
| Name | Type | Description |
|---|---|---|
~input/route |
autoware_planning_msgs::Route | route and goal pose |
~input/occupancy_grid |
nav_msgs::OccupancyGrid | costmap, for drivable areas |
~input/odometry |
nav_msgs::Odometry | vehicle velocity, for checking whether vehicle is stopped |
~input/scenario |
tier4_planning_msgs::Scenario | scenarios to be activated, for node activation |
Output topics
| Name | Type | Description |
|---|---|---|
~output/trajectory |
autoware_planning_msgs::Trajectory | trajectory to be followed |
is_completed |
bool (implemented as rosparam) | whether all split trajectory are published |
Output TFs
None
How to launch
- Write your remapping info in
freespace_planner.launchor add args when executingroslaunch roslaunch freespace_planner freespace_planner.launch
Parameters
{{json_to_markdown(“planning/autoware_freespace_planner/schema/freespace_planner.schema.json”)}}
Node parameters
| Parameter | Type | Description |
|---|---|---|
planning_algorithms |
string | algorithms used in the node |
vehicle_shape_margin_m |
float | collision margin in planning algorithm |
update_rate |
double | timer’s update rate |
waypoints_velocity |
double | velocity in output trajectory (currently, only constant velocity is supported) |
th_arrived_distance_m |
double | threshold distance to check if vehicle has arrived at the trajectory’s endpoint |
th_stopped_time_sec |
double | threshold time to check if vehicle is stopped |
th_stopped_velocity_mps |
double | threshold velocity to check if vehicle is stopped |
th_course_out_distance_m |
double | threshold distance to check if vehicle is out of course |
th_obstacle_time_sec |
double | threshold time to check if obstacle is on the trajectory |
vehicle_shape_margin_m |
double | vehicle margin |
replan_when_obstacle_found |
bool | whether replanning when obstacle has found on the trajectory |
replan_when_course_out |
bool | whether replanning when vehicle is out of course |
Planner common parameters
| Parameter | Type | Description |
|---|---|---|
time_limit |
double | time limit of planning |
maximum_turning_ratio |
double | max ratio of actual turning range to use |
turning_steps |
double | number of turning steps within turning range |
theta_size |
double | the number of angle’s discretization |
lateral_goal_range |
double | goal range of lateral position |
longitudinal_goal_range |
double | goal range of longitudinal position |
angle_goal_range |
double | goal range of angle |
curve_weight |
double | additional cost factor for curve actions |
reverse_weight |
double | additional cost factor for reverse actions |
direction_change_weight |
double | additional cost factor for switching direction |
obstacle_threshold |
double | threshold for regarding a certain grid as obstacle |
A* search parameters
| Parameter | Type | Description |
|---|---|---|
search_method |
string | method of searching, start to goal or vice versa |
only_behind_solutions |
bool | whether restricting the solutions to be behind the goal |
use_back |
bool | whether using backward trajectory |
adapt_expansion_distance |
bool | if true, adapt expansion distance based on environment |
expansion_distance |
double | length of expansion for node transitions |
near_goal_distance |
double | near goal distance threshold |
distance_heuristic_weight |
double | heuristic weight for estimating node’s cost |
smoothness_weight |
double | cost factor for change in curvature |
obstacle_distance_weight |
double | cost factor for distance to obstacle |
goal_lat_distance_weight |
double | cost factor for lateral distance from goal |
RRT* search parameters
| Parameter | Type | Description |
|---|---|---|
max planning time |
double | maximum planning time [msec] (used only when enable_update is set true) |
enable_update |
bool | whether update after feasible solution found until max_planning time elapse |
use_informed_sampling |
bool | Use informed RRT* (of Gammell et al.) |
neighbor_radius |
double | neighbor radius of RRT* algorithm |
File truncated at 100 lines see the full file
Changelog for package autoware_freespace_planner
0.50.0 (2026-02-14)
- Merge remote-tracking branch 'origin/main' into humble
- feat!: remove ROS 2 Galactic codes (#11905)
- Contributors: Ryohsuke Mitsudome
0.49.0 (2025-12-30)
-
Merge remote-tracking branch 'origin/main' into prepare-0.49.0-changelog
-
fix(freespace_planner): build testing failure (#11759)
-
fix: resolve clock type mismatch in tf2 lookups with simulation time (#11523)
* fix: resolve clock type mismatch in tf2 transform lookups Replace rclcpp::Time(0) with tf2::TimePointZero in lookupTransform calls to fix clock type conflicts when using simulation time. The issue:
- rclcpp::Time(0) creates a time with SYSTEM_TIME clock type
- When nodes run with use_sim_time:=true, transforms use ROS_TIME clock
- This causes clock type mismatch errors in tf2 lookups
- Error: "Lookup would require extrapolation into the past" The fix:
- tf2::TimePointZero is clock-type agnostic
- Correctly represents "get latest available transform"
- Also replaced rclcpp::Duration::from_seconds() with tf2::durationFromSec() This bug affects transform lookups in critical safety and planning components, causing runtime errors when simulation time is enabled. Affected packages:
- autoware_autonomous_emergency_braking
- autoware_planning_evaluator
- autoware_freespace_planner
* style(pre-commit): autofix ---------Co-authored-by: pre-commit-ci-lite[bot] <117423508+pre-commit-ci-lite[bot]@users.noreply.github.com> Co-authored-by: Shumpei Wakabayashi <<42209144+shmpwk@users.noreply.github.com>>
-
Contributors: Ryohsuke Mitsudome, Zulfaqar Azmi, ralwing
0.48.0 (2025-11-18)
- Merge remote-tracking branch 'origin/main' into humble
- feat(autoware_freespace_planner): utilize all 3 components of velocity (#11427) fix:the stopping speed judgments of freespace_planner and mission_planner are consistent, taking into account the speed in xyz direction Signed-off-by: yangzesong <<15340400289@163.com>> Co-authored-by: yangzesong <<15340400289@163.com>>
- Contributors: Ryohsuke Mitsudome
0.47.1 (2025-08-14)
0.47.0 (2025-08-11)
0.46.0 (2025-06-20)
0.45.0 (2025-05-22)
0.44.2 (2025-06-10)
0.44.1 (2025-05-01)
0.44.0 (2025-04-18)
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)
-
feat: adaption to ROS nodes guidelines about directory structure (#10268)
-
fix(planning): add missing exec_depend (#10134)
- fix(planning): add missing exec_depend
- fix find-pkg-share
* fix find-pkg-share ---------
-
Contributors: Hayato Mizushima, NorahXiong, Takagi, Isamu, Yutaka Kondo
File truncated at 100 lines see the full file
Package Dependencies
System Dependencies
Dependant Packages
| Name | Deps |
|---|---|
| tier4_planning_launch |
Launch files
- launch/freespace_planner.launch.xml
-
- input_route [default: input_route]
- input_occupancy_grid [default: input_occupancy_grid]
- input_scenario [default: input_scenario]
- input_odometry [default: /localization/kinematic_state]
- output_trajectory [default: output_trajectory]
- is_completed [default: is_completed]
- param_file [default: $(find-pkg-share autoware_freespace_planner)/config/freespace_planner.param.yaml]
- vehicle_info_param_file [default: $(find-pkg-share autoware_vehicle_info_utils)/config/vehicle_info.param.yaml]
Messages
Services
Plugins
Recent questions tagged autoware_freespace_planner at Robotics Stack Exchange
Package Summary
| Version | 0.50.0 |
| License | Apache License 2.0 |
| Build type | AMENT_CMAKE |
| Use | RECOMMENDED |
Repository Summary
| Description | |
| Checkout URI | https://github.com/autowarefoundation/autoware_universe.git |
| VCS Type | git |
| VCS Version | main |
| Last Updated | 2026-02-25 |
| Dev Status | UNKNOWN |
| Released | UNRELEASED |
| Contributing |
Help Wanted (-)
Good First Issues (-) Pull Requests to Review (-) |
Package Description
Maintainers
- Kosuke Takeuchi
- Alqudah Mohammad
Authors
- Takamasa Horibe
- Takayuki Murooka
- Akihito OHSATO
- Tomohito ANDO
The autoware_freespace_planner
freespace_planner_node
freespace_planner_node is a global path planner node that plans trajectory
in the space having static/dynamic obstacles. This node is currently based on
Hybrid A* search algorithm in freespace_planning_algorithms package.
Other algorithms such as rrt* will be also added and selectable in the future.
Note Due to the constraint of trajectory following, the output trajectory will be split to include only the single direction path. In other words, the output trajectory doesn’t include both forward and backward trajectories at once.
Input topics
| Name | Type | Description |
|---|---|---|
~input/route |
autoware_planning_msgs::Route | route and goal pose |
~input/occupancy_grid |
nav_msgs::OccupancyGrid | costmap, for drivable areas |
~input/odometry |
nav_msgs::Odometry | vehicle velocity, for checking whether vehicle is stopped |
~input/scenario |
tier4_planning_msgs::Scenario | scenarios to be activated, for node activation |
Output topics
| Name | Type | Description |
|---|---|---|
~output/trajectory |
autoware_planning_msgs::Trajectory | trajectory to be followed |
is_completed |
bool (implemented as rosparam) | whether all split trajectory are published |
Output TFs
None
How to launch
- Write your remapping info in
freespace_planner.launchor add args when executingroslaunch roslaunch freespace_planner freespace_planner.launch
Parameters
{{json_to_markdown(“planning/autoware_freespace_planner/schema/freespace_planner.schema.json”)}}
Node parameters
| Parameter | Type | Description |
|---|---|---|
planning_algorithms |
string | algorithms used in the node |
vehicle_shape_margin_m |
float | collision margin in planning algorithm |
update_rate |
double | timer’s update rate |
waypoints_velocity |
double | velocity in output trajectory (currently, only constant velocity is supported) |
th_arrived_distance_m |
double | threshold distance to check if vehicle has arrived at the trajectory’s endpoint |
th_stopped_time_sec |
double | threshold time to check if vehicle is stopped |
th_stopped_velocity_mps |
double | threshold velocity to check if vehicle is stopped |
th_course_out_distance_m |
double | threshold distance to check if vehicle is out of course |
th_obstacle_time_sec |
double | threshold time to check if obstacle is on the trajectory |
vehicle_shape_margin_m |
double | vehicle margin |
replan_when_obstacle_found |
bool | whether replanning when obstacle has found on the trajectory |
replan_when_course_out |
bool | whether replanning when vehicle is out of course |
Planner common parameters
| Parameter | Type | Description |
|---|---|---|
time_limit |
double | time limit of planning |
maximum_turning_ratio |
double | max ratio of actual turning range to use |
turning_steps |
double | number of turning steps within turning range |
theta_size |
double | the number of angle’s discretization |
lateral_goal_range |
double | goal range of lateral position |
longitudinal_goal_range |
double | goal range of longitudinal position |
angle_goal_range |
double | goal range of angle |
curve_weight |
double | additional cost factor for curve actions |
reverse_weight |
double | additional cost factor for reverse actions |
direction_change_weight |
double | additional cost factor for switching direction |
obstacle_threshold |
double | threshold for regarding a certain grid as obstacle |
A* search parameters
| Parameter | Type | Description |
|---|---|---|
search_method |
string | method of searching, start to goal or vice versa |
only_behind_solutions |
bool | whether restricting the solutions to be behind the goal |
use_back |
bool | whether using backward trajectory |
adapt_expansion_distance |
bool | if true, adapt expansion distance based on environment |
expansion_distance |
double | length of expansion for node transitions |
near_goal_distance |
double | near goal distance threshold |
distance_heuristic_weight |
double | heuristic weight for estimating node’s cost |
smoothness_weight |
double | cost factor for change in curvature |
obstacle_distance_weight |
double | cost factor for distance to obstacle |
goal_lat_distance_weight |
double | cost factor for lateral distance from goal |
RRT* search parameters
| Parameter | Type | Description |
|---|---|---|
max planning time |
double | maximum planning time [msec] (used only when enable_update is set true) |
enable_update |
bool | whether update after feasible solution found until max_planning time elapse |
use_informed_sampling |
bool | Use informed RRT* (of Gammell et al.) |
neighbor_radius |
double | neighbor radius of RRT* algorithm |
File truncated at 100 lines see the full file
Changelog for package autoware_freespace_planner
0.50.0 (2026-02-14)
- Merge remote-tracking branch 'origin/main' into humble
- feat!: remove ROS 2 Galactic codes (#11905)
- Contributors: Ryohsuke Mitsudome
0.49.0 (2025-12-30)
-
Merge remote-tracking branch 'origin/main' into prepare-0.49.0-changelog
-
fix(freespace_planner): build testing failure (#11759)
-
fix: resolve clock type mismatch in tf2 lookups with simulation time (#11523)
* fix: resolve clock type mismatch in tf2 transform lookups Replace rclcpp::Time(0) with tf2::TimePointZero in lookupTransform calls to fix clock type conflicts when using simulation time. The issue:
- rclcpp::Time(0) creates a time with SYSTEM_TIME clock type
- When nodes run with use_sim_time:=true, transforms use ROS_TIME clock
- This causes clock type mismatch errors in tf2 lookups
- Error: "Lookup would require extrapolation into the past" The fix:
- tf2::TimePointZero is clock-type agnostic
- Correctly represents "get latest available transform"
- Also replaced rclcpp::Duration::from_seconds() with tf2::durationFromSec() This bug affects transform lookups in critical safety and planning components, causing runtime errors when simulation time is enabled. Affected packages:
- autoware_autonomous_emergency_braking
- autoware_planning_evaluator
- autoware_freespace_planner
* style(pre-commit): autofix ---------Co-authored-by: pre-commit-ci-lite[bot] <117423508+pre-commit-ci-lite[bot]@users.noreply.github.com> Co-authored-by: Shumpei Wakabayashi <<42209144+shmpwk@users.noreply.github.com>>
-
Contributors: Ryohsuke Mitsudome, Zulfaqar Azmi, ralwing
0.48.0 (2025-11-18)
- Merge remote-tracking branch 'origin/main' into humble
- feat(autoware_freespace_planner): utilize all 3 components of velocity (#11427) fix:the stopping speed judgments of freespace_planner and mission_planner are consistent, taking into account the speed in xyz direction Signed-off-by: yangzesong <<15340400289@163.com>> Co-authored-by: yangzesong <<15340400289@163.com>>
- Contributors: Ryohsuke Mitsudome
0.47.1 (2025-08-14)
0.47.0 (2025-08-11)
0.46.0 (2025-06-20)
0.45.0 (2025-05-22)
0.44.2 (2025-06-10)
0.44.1 (2025-05-01)
0.44.0 (2025-04-18)
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)
-
feat: adaption to ROS nodes guidelines about directory structure (#10268)
-
fix(planning): add missing exec_depend (#10134)
- fix(planning): add missing exec_depend
- fix find-pkg-share
* fix find-pkg-share ---------
-
Contributors: Hayato Mizushima, NorahXiong, Takagi, Isamu, Yutaka Kondo
File truncated at 100 lines see the full file
Package Dependencies
System Dependencies
Dependant Packages
| Name | Deps |
|---|---|
| tier4_planning_launch |
Launch files
- launch/freespace_planner.launch.xml
-
- input_route [default: input_route]
- input_occupancy_grid [default: input_occupancy_grid]
- input_scenario [default: input_scenario]
- input_odometry [default: /localization/kinematic_state]
- output_trajectory [default: output_trajectory]
- is_completed [default: is_completed]
- param_file [default: $(find-pkg-share autoware_freespace_planner)/config/freespace_planner.param.yaml]
- vehicle_info_param_file [default: $(find-pkg-share autoware_vehicle_info_utils)/config/vehicle_info.param.yaml]
Messages
Services
Plugins
Recent questions tagged autoware_freespace_planner at Robotics Stack Exchange
Package Summary
| Version | 0.50.0 |
| License | Apache License 2.0 |
| Build type | AMENT_CMAKE |
| Use | RECOMMENDED |
Repository Summary
| Description | |
| Checkout URI | https://github.com/autowarefoundation/autoware_universe.git |
| VCS Type | git |
| VCS Version | main |
| Last Updated | 2026-02-25 |
| Dev Status | UNKNOWN |
| Released | UNRELEASED |
| Contributing |
Help Wanted (-)
Good First Issues (-) Pull Requests to Review (-) |
Package Description
Maintainers
- Kosuke Takeuchi
- Alqudah Mohammad
Authors
- Takamasa Horibe
- Takayuki Murooka
- Akihito OHSATO
- Tomohito ANDO
The autoware_freespace_planner
freespace_planner_node
freespace_planner_node is a global path planner node that plans trajectory
in the space having static/dynamic obstacles. This node is currently based on
Hybrid A* search algorithm in freespace_planning_algorithms package.
Other algorithms such as rrt* will be also added and selectable in the future.
Note Due to the constraint of trajectory following, the output trajectory will be split to include only the single direction path. In other words, the output trajectory doesn’t include both forward and backward trajectories at once.
Input topics
| Name | Type | Description |
|---|---|---|
~input/route |
autoware_planning_msgs::Route | route and goal pose |
~input/occupancy_grid |
nav_msgs::OccupancyGrid | costmap, for drivable areas |
~input/odometry |
nav_msgs::Odometry | vehicle velocity, for checking whether vehicle is stopped |
~input/scenario |
tier4_planning_msgs::Scenario | scenarios to be activated, for node activation |
Output topics
| Name | Type | Description |
|---|---|---|
~output/trajectory |
autoware_planning_msgs::Trajectory | trajectory to be followed |
is_completed |
bool (implemented as rosparam) | whether all split trajectory are published |
Output TFs
None
How to launch
- Write your remapping info in
freespace_planner.launchor add args when executingroslaunch roslaunch freespace_planner freespace_planner.launch
Parameters
{{json_to_markdown(“planning/autoware_freespace_planner/schema/freespace_planner.schema.json”)}}
Node parameters
| Parameter | Type | Description |
|---|---|---|
planning_algorithms |
string | algorithms used in the node |
vehicle_shape_margin_m |
float | collision margin in planning algorithm |
update_rate |
double | timer’s update rate |
waypoints_velocity |
double | velocity in output trajectory (currently, only constant velocity is supported) |
th_arrived_distance_m |
double | threshold distance to check if vehicle has arrived at the trajectory’s endpoint |
th_stopped_time_sec |
double | threshold time to check if vehicle is stopped |
th_stopped_velocity_mps |
double | threshold velocity to check if vehicle is stopped |
th_course_out_distance_m |
double | threshold distance to check if vehicle is out of course |
th_obstacle_time_sec |
double | threshold time to check if obstacle is on the trajectory |
vehicle_shape_margin_m |
double | vehicle margin |
replan_when_obstacle_found |
bool | whether replanning when obstacle has found on the trajectory |
replan_when_course_out |
bool | whether replanning when vehicle is out of course |
Planner common parameters
| Parameter | Type | Description |
|---|---|---|
time_limit |
double | time limit of planning |
maximum_turning_ratio |
double | max ratio of actual turning range to use |
turning_steps |
double | number of turning steps within turning range |
theta_size |
double | the number of angle’s discretization |
lateral_goal_range |
double | goal range of lateral position |
longitudinal_goal_range |
double | goal range of longitudinal position |
angle_goal_range |
double | goal range of angle |
curve_weight |
double | additional cost factor for curve actions |
reverse_weight |
double | additional cost factor for reverse actions |
direction_change_weight |
double | additional cost factor for switching direction |
obstacle_threshold |
double | threshold for regarding a certain grid as obstacle |
A* search parameters
| Parameter | Type | Description |
|---|---|---|
search_method |
string | method of searching, start to goal or vice versa |
only_behind_solutions |
bool | whether restricting the solutions to be behind the goal |
use_back |
bool | whether using backward trajectory |
adapt_expansion_distance |
bool | if true, adapt expansion distance based on environment |
expansion_distance |
double | length of expansion for node transitions |
near_goal_distance |
double | near goal distance threshold |
distance_heuristic_weight |
double | heuristic weight for estimating node’s cost |
smoothness_weight |
double | cost factor for change in curvature |
obstacle_distance_weight |
double | cost factor for distance to obstacle |
goal_lat_distance_weight |
double | cost factor for lateral distance from goal |
RRT* search parameters
| Parameter | Type | Description |
|---|---|---|
max planning time |
double | maximum planning time [msec] (used only when enable_update is set true) |
enable_update |
bool | whether update after feasible solution found until max_planning time elapse |
use_informed_sampling |
bool | Use informed RRT* (of Gammell et al.) |
neighbor_radius |
double | neighbor radius of RRT* algorithm |
File truncated at 100 lines see the full file
Changelog for package autoware_freespace_planner
0.50.0 (2026-02-14)
- Merge remote-tracking branch 'origin/main' into humble
- feat!: remove ROS 2 Galactic codes (#11905)
- Contributors: Ryohsuke Mitsudome
0.49.0 (2025-12-30)
-
Merge remote-tracking branch 'origin/main' into prepare-0.49.0-changelog
-
fix(freespace_planner): build testing failure (#11759)
-
fix: resolve clock type mismatch in tf2 lookups with simulation time (#11523)
* fix: resolve clock type mismatch in tf2 transform lookups Replace rclcpp::Time(0) with tf2::TimePointZero in lookupTransform calls to fix clock type conflicts when using simulation time. The issue:
- rclcpp::Time(0) creates a time with SYSTEM_TIME clock type
- When nodes run with use_sim_time:=true, transforms use ROS_TIME clock
- This causes clock type mismatch errors in tf2 lookups
- Error: "Lookup would require extrapolation into the past" The fix:
- tf2::TimePointZero is clock-type agnostic
- Correctly represents "get latest available transform"
- Also replaced rclcpp::Duration::from_seconds() with tf2::durationFromSec() This bug affects transform lookups in critical safety and planning components, causing runtime errors when simulation time is enabled. Affected packages:
- autoware_autonomous_emergency_braking
- autoware_planning_evaluator
- autoware_freespace_planner
* style(pre-commit): autofix ---------Co-authored-by: pre-commit-ci-lite[bot] <117423508+pre-commit-ci-lite[bot]@users.noreply.github.com> Co-authored-by: Shumpei Wakabayashi <<42209144+shmpwk@users.noreply.github.com>>
-
Contributors: Ryohsuke Mitsudome, Zulfaqar Azmi, ralwing
0.48.0 (2025-11-18)
- Merge remote-tracking branch 'origin/main' into humble
- feat(autoware_freespace_planner): utilize all 3 components of velocity (#11427) fix:the stopping speed judgments of freespace_planner and mission_planner are consistent, taking into account the speed in xyz direction Signed-off-by: yangzesong <<15340400289@163.com>> Co-authored-by: yangzesong <<15340400289@163.com>>
- Contributors: Ryohsuke Mitsudome
0.47.1 (2025-08-14)
0.47.0 (2025-08-11)
0.46.0 (2025-06-20)
0.45.0 (2025-05-22)
0.44.2 (2025-06-10)
0.44.1 (2025-05-01)
0.44.0 (2025-04-18)
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)
-
feat: adaption to ROS nodes guidelines about directory structure (#10268)
-
fix(planning): add missing exec_depend (#10134)
- fix(planning): add missing exec_depend
- fix find-pkg-share
* fix find-pkg-share ---------
-
Contributors: Hayato Mizushima, NorahXiong, Takagi, Isamu, Yutaka Kondo
File truncated at 100 lines see the full file
Package Dependencies
System Dependencies
Dependant Packages
| Name | Deps |
|---|---|
| tier4_planning_launch |
Launch files
- launch/freespace_planner.launch.xml
-
- input_route [default: input_route]
- input_occupancy_grid [default: input_occupancy_grid]
- input_scenario [default: input_scenario]
- input_odometry [default: /localization/kinematic_state]
- output_trajectory [default: output_trajectory]
- is_completed [default: is_completed]
- param_file [default: $(find-pkg-share autoware_freespace_planner)/config/freespace_planner.param.yaml]
- vehicle_info_param_file [default: $(find-pkg-share autoware_vehicle_info_utils)/config/vehicle_info.param.yaml]