Package Summary
Tags | No category tags. |
Version | 0.39.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 | 2025-09-26 |
Dev Status | UNKNOWN |
Released | UNRELEASED |
Tags | planner ros calibration self-driving-car autonomous-driving autonomous-vehicles ros2 3d-map autoware |
Contributing |
Help Wanted (-)
Good First Issues (-) Pull Requests to Review (-) |
Package Description
Additional Links
Maintainers
- Daniel Sanchez
- Yukihiro Saito
- Go Sakayori
- Shintaro Sakoda
Authors
- Daniel Sanchez
Autoware Trajectory Modifier
The autoware_trajectory_modifier
package provides a plugin-based architecture for post-processing trajectory points to improve trajectory quality and ensure vehicle safety. It takes candidate trajectories and applies various modification algorithms to enhance their feasibility and safety characteristics.
Features
- Plugin-based architecture for extensible trajectory modifications
- Stop point fixing to prevent trajectory issues near stationary conditions
- Configurable parameters to adjust modification behavior
Architecture
The trajectory modifier uses a plugin-based system where different modification algorithms can be implemented as plugins. Each plugin inherits from the TrajectoryModifierPluginBase
class and implements the required interface.
Plugin Interface
All modifier plugins must inherit from TrajectoryModifierPluginBase
and implement:
-
modify_trajectory()
- Main method to modify trajectory points -
set_up_params()
- Initialize plugin parameters -
on_parameter()
- Handle parameter updates -
is_trajectory_modification_required()
- Determine if modification is needed
Current Plugins
Stop Point Fixer
The Stop Point Fixer plugin addresses trajectory issues when the ego vehicle is stationary or moving at very low speeds. It prevents problematic trajectory points that could cause planning issues by:
- Monitoring ego vehicle velocity and trajectory distance
- Replacing the trajectory with a single stop point when conditions are met
- Ensuring smooth operation during stationary periods
Dependencies
This package depends on the following packages:
-
autoware_internal_planning_msgs
: For candidate trajectory message types -
autoware_planning_msgs
: For output trajectory message types -
autoware_motion_utils
: Motion-related utility functions -
autoware_trajectory
: Trajectory data structures and utilities -
autoware_utils
: Common utility functions
Input/Output
-
Input:
autoware_internal_planning_msgs::msg::CandidateTrajectories
-
Output: Modified
autoware_internal_planning_msgs::msg::CandidateTrajectories
and selectedautoware_planning_msgs::msg::Trajectory
Parameters
-
use_stop_point_fixer
: Enable the stop point fixer modifier plugin (default: true) -
stop_point_fixer.velocity_threshold_mps
: Velocity threshold below which ego vehicle is considered stationary (default: 0.1 m/s) -
stop_point_fixer.min_distance_threshold_m
: Minimum distance threshold to trigger trajectory replacement (default: 1.0 m)
Parameters can be set via YAML configuration files in the config/
directory.
Adding New Modifier Plugins
To add a new modifier plugin:
- Create header and source files in
trajectory_modifier_plugins/
- Inherit from
TrajectoryModifierPluginBase
- Implement the required virtual methods
- Register the plugin in the main node’s
initialize_modifiers()
method - Add plugin-specific parameters to the schema and config files
Package Dependencies
System Dependencies
Dependant Packages
Launch files
- launch/trajectory_modifier.launch.xml
-
- trajectory_modifier_param_path [default: $(find-pkg-share autoware_trajectory_modifier)/config/trajectory_modifier.param.yaml]
- input_candidate_trajectories [default: /planning/diffusion_planner/candidate_trajectories]
- input_odometry [default: /localization/kinematic_state]
- input_acceleration [default: /localization/acceleration]
- output_candidate_trajectories [default: ~/output/candidate_trajectories]
Messages
Services
Plugins
Recent questions tagged autoware_trajectory_modifier at Robotics Stack Exchange
Package Summary
Tags | No category tags. |
Version | 0.39.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 | 2025-09-26 |
Dev Status | UNKNOWN |
Released | UNRELEASED |
Tags | planner ros calibration self-driving-car autonomous-driving autonomous-vehicles ros2 3d-map autoware |
Contributing |
Help Wanted (-)
Good First Issues (-) Pull Requests to Review (-) |
Package Description
Additional Links
Maintainers
- Daniel Sanchez
- Yukihiro Saito
- Go Sakayori
- Shintaro Sakoda
Authors
- Daniel Sanchez
Autoware Trajectory Modifier
The autoware_trajectory_modifier
package provides a plugin-based architecture for post-processing trajectory points to improve trajectory quality and ensure vehicle safety. It takes candidate trajectories and applies various modification algorithms to enhance their feasibility and safety characteristics.
Features
- Plugin-based architecture for extensible trajectory modifications
- Stop point fixing to prevent trajectory issues near stationary conditions
- Configurable parameters to adjust modification behavior
Architecture
The trajectory modifier uses a plugin-based system where different modification algorithms can be implemented as plugins. Each plugin inherits from the TrajectoryModifierPluginBase
class and implements the required interface.
Plugin Interface
All modifier plugins must inherit from TrajectoryModifierPluginBase
and implement:
-
modify_trajectory()
- Main method to modify trajectory points -
set_up_params()
- Initialize plugin parameters -
on_parameter()
- Handle parameter updates -
is_trajectory_modification_required()
- Determine if modification is needed
Current Plugins
Stop Point Fixer
The Stop Point Fixer plugin addresses trajectory issues when the ego vehicle is stationary or moving at very low speeds. It prevents problematic trajectory points that could cause planning issues by:
- Monitoring ego vehicle velocity and trajectory distance
- Replacing the trajectory with a single stop point when conditions are met
- Ensuring smooth operation during stationary periods
Dependencies
This package depends on the following packages:
-
autoware_internal_planning_msgs
: For candidate trajectory message types -
autoware_planning_msgs
: For output trajectory message types -
autoware_motion_utils
: Motion-related utility functions -
autoware_trajectory
: Trajectory data structures and utilities -
autoware_utils
: Common utility functions
Input/Output
-
Input:
autoware_internal_planning_msgs::msg::CandidateTrajectories
-
Output: Modified
autoware_internal_planning_msgs::msg::CandidateTrajectories
and selectedautoware_planning_msgs::msg::Trajectory
Parameters
-
use_stop_point_fixer
: Enable the stop point fixer modifier plugin (default: true) -
stop_point_fixer.velocity_threshold_mps
: Velocity threshold below which ego vehicle is considered stationary (default: 0.1 m/s) -
stop_point_fixer.min_distance_threshold_m
: Minimum distance threshold to trigger trajectory replacement (default: 1.0 m)
Parameters can be set via YAML configuration files in the config/
directory.
Adding New Modifier Plugins
To add a new modifier plugin:
- Create header and source files in
trajectory_modifier_plugins/
- Inherit from
TrajectoryModifierPluginBase
- Implement the required virtual methods
- Register the plugin in the main node’s
initialize_modifiers()
method - Add plugin-specific parameters to the schema and config files
Package Dependencies
System Dependencies
Dependant Packages
Launch files
- launch/trajectory_modifier.launch.xml
-
- trajectory_modifier_param_path [default: $(find-pkg-share autoware_trajectory_modifier)/config/trajectory_modifier.param.yaml]
- input_candidate_trajectories [default: /planning/diffusion_planner/candidate_trajectories]
- input_odometry [default: /localization/kinematic_state]
- input_acceleration [default: /localization/acceleration]
- output_candidate_trajectories [default: ~/output/candidate_trajectories]
Messages
Services
Plugins
Recent questions tagged autoware_trajectory_modifier at Robotics Stack Exchange
Package Summary
Tags | No category tags. |
Version | 0.39.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 | 2025-09-26 |
Dev Status | UNKNOWN |
Released | UNRELEASED |
Tags | planner ros calibration self-driving-car autonomous-driving autonomous-vehicles ros2 3d-map autoware |
Contributing |
Help Wanted (-)
Good First Issues (-) Pull Requests to Review (-) |
Package Description
Additional Links
Maintainers
- Daniel Sanchez
- Yukihiro Saito
- Go Sakayori
- Shintaro Sakoda
Authors
- Daniel Sanchez
Autoware Trajectory Modifier
The autoware_trajectory_modifier
package provides a plugin-based architecture for post-processing trajectory points to improve trajectory quality and ensure vehicle safety. It takes candidate trajectories and applies various modification algorithms to enhance their feasibility and safety characteristics.
Features
- Plugin-based architecture for extensible trajectory modifications
- Stop point fixing to prevent trajectory issues near stationary conditions
- Configurable parameters to adjust modification behavior
Architecture
The trajectory modifier uses a plugin-based system where different modification algorithms can be implemented as plugins. Each plugin inherits from the TrajectoryModifierPluginBase
class and implements the required interface.
Plugin Interface
All modifier plugins must inherit from TrajectoryModifierPluginBase
and implement:
-
modify_trajectory()
- Main method to modify trajectory points -
set_up_params()
- Initialize plugin parameters -
on_parameter()
- Handle parameter updates -
is_trajectory_modification_required()
- Determine if modification is needed
Current Plugins
Stop Point Fixer
The Stop Point Fixer plugin addresses trajectory issues when the ego vehicle is stationary or moving at very low speeds. It prevents problematic trajectory points that could cause planning issues by:
- Monitoring ego vehicle velocity and trajectory distance
- Replacing the trajectory with a single stop point when conditions are met
- Ensuring smooth operation during stationary periods
Dependencies
This package depends on the following packages:
-
autoware_internal_planning_msgs
: For candidate trajectory message types -
autoware_planning_msgs
: For output trajectory message types -
autoware_motion_utils
: Motion-related utility functions -
autoware_trajectory
: Trajectory data structures and utilities -
autoware_utils
: Common utility functions
Input/Output
-
Input:
autoware_internal_planning_msgs::msg::CandidateTrajectories
-
Output: Modified
autoware_internal_planning_msgs::msg::CandidateTrajectories
and selectedautoware_planning_msgs::msg::Trajectory
Parameters
-
use_stop_point_fixer
: Enable the stop point fixer modifier plugin (default: true) -
stop_point_fixer.velocity_threshold_mps
: Velocity threshold below which ego vehicle is considered stationary (default: 0.1 m/s) -
stop_point_fixer.min_distance_threshold_m
: Minimum distance threshold to trigger trajectory replacement (default: 1.0 m)
Parameters can be set via YAML configuration files in the config/
directory.
Adding New Modifier Plugins
To add a new modifier plugin:
- Create header and source files in
trajectory_modifier_plugins/
- Inherit from
TrajectoryModifierPluginBase
- Implement the required virtual methods
- Register the plugin in the main node’s
initialize_modifiers()
method - Add plugin-specific parameters to the schema and config files
Package Dependencies
System Dependencies
Dependant Packages
Launch files
- launch/trajectory_modifier.launch.xml
-
- trajectory_modifier_param_path [default: $(find-pkg-share autoware_trajectory_modifier)/config/trajectory_modifier.param.yaml]
- input_candidate_trajectories [default: /planning/diffusion_planner/candidate_trajectories]
- input_odometry [default: /localization/kinematic_state]
- input_acceleration [default: /localization/acceleration]
- output_candidate_trajectories [default: ~/output/candidate_trajectories]
Messages
Services
Plugins
Recent questions tagged autoware_trajectory_modifier at Robotics Stack Exchange
Package Summary
Tags | No category tags. |
Version | 0.39.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 | 2025-09-26 |
Dev Status | UNKNOWN |
Released | UNRELEASED |
Tags | planner ros calibration self-driving-car autonomous-driving autonomous-vehicles ros2 3d-map autoware |
Contributing |
Help Wanted (-)
Good First Issues (-) Pull Requests to Review (-) |
Package Description
Additional Links
Maintainers
- Daniel Sanchez
- Yukihiro Saito
- Go Sakayori
- Shintaro Sakoda
Authors
- Daniel Sanchez
Autoware Trajectory Modifier
The autoware_trajectory_modifier
package provides a plugin-based architecture for post-processing trajectory points to improve trajectory quality and ensure vehicle safety. It takes candidate trajectories and applies various modification algorithms to enhance their feasibility and safety characteristics.
Features
- Plugin-based architecture for extensible trajectory modifications
- Stop point fixing to prevent trajectory issues near stationary conditions
- Configurable parameters to adjust modification behavior
Architecture
The trajectory modifier uses a plugin-based system where different modification algorithms can be implemented as plugins. Each plugin inherits from the TrajectoryModifierPluginBase
class and implements the required interface.
Plugin Interface
All modifier plugins must inherit from TrajectoryModifierPluginBase
and implement:
-
modify_trajectory()
- Main method to modify trajectory points -
set_up_params()
- Initialize plugin parameters -
on_parameter()
- Handle parameter updates -
is_trajectory_modification_required()
- Determine if modification is needed
Current Plugins
Stop Point Fixer
The Stop Point Fixer plugin addresses trajectory issues when the ego vehicle is stationary or moving at very low speeds. It prevents problematic trajectory points that could cause planning issues by:
- Monitoring ego vehicle velocity and trajectory distance
- Replacing the trajectory with a single stop point when conditions are met
- Ensuring smooth operation during stationary periods
Dependencies
This package depends on the following packages:
-
autoware_internal_planning_msgs
: For candidate trajectory message types -
autoware_planning_msgs
: For output trajectory message types -
autoware_motion_utils
: Motion-related utility functions -
autoware_trajectory
: Trajectory data structures and utilities -
autoware_utils
: Common utility functions
Input/Output
-
Input:
autoware_internal_planning_msgs::msg::CandidateTrajectories
-
Output: Modified
autoware_internal_planning_msgs::msg::CandidateTrajectories
and selectedautoware_planning_msgs::msg::Trajectory
Parameters
-
use_stop_point_fixer
: Enable the stop point fixer modifier plugin (default: true) -
stop_point_fixer.velocity_threshold_mps
: Velocity threshold below which ego vehicle is considered stationary (default: 0.1 m/s) -
stop_point_fixer.min_distance_threshold_m
: Minimum distance threshold to trigger trajectory replacement (default: 1.0 m)
Parameters can be set via YAML configuration files in the config/
directory.
Adding New Modifier Plugins
To add a new modifier plugin:
- Create header and source files in
trajectory_modifier_plugins/
- Inherit from
TrajectoryModifierPluginBase
- Implement the required virtual methods
- Register the plugin in the main node’s
initialize_modifiers()
method - Add plugin-specific parameters to the schema and config files
Package Dependencies
System Dependencies
Dependant Packages
Launch files
- launch/trajectory_modifier.launch.xml
-
- trajectory_modifier_param_path [default: $(find-pkg-share autoware_trajectory_modifier)/config/trajectory_modifier.param.yaml]
- input_candidate_trajectories [default: /planning/diffusion_planner/candidate_trajectories]
- input_odometry [default: /localization/kinematic_state]
- input_acceleration [default: /localization/acceleration]
- output_candidate_trajectories [default: ~/output/candidate_trajectories]
Messages
Services
Plugins
Recent questions tagged autoware_trajectory_modifier at Robotics Stack Exchange
Package Summary
Tags | No category tags. |
Version | 0.39.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 | 2025-09-26 |
Dev Status | UNKNOWN |
Released | UNRELEASED |
Tags | planner ros calibration self-driving-car autonomous-driving autonomous-vehicles ros2 3d-map autoware |
Contributing |
Help Wanted (-)
Good First Issues (-) Pull Requests to Review (-) |
Package Description
Additional Links
Maintainers
- Daniel Sanchez
- Yukihiro Saito
- Go Sakayori
- Shintaro Sakoda
Authors
- Daniel Sanchez
Autoware Trajectory Modifier
The autoware_trajectory_modifier
package provides a plugin-based architecture for post-processing trajectory points to improve trajectory quality and ensure vehicle safety. It takes candidate trajectories and applies various modification algorithms to enhance their feasibility and safety characteristics.
Features
- Plugin-based architecture for extensible trajectory modifications
- Stop point fixing to prevent trajectory issues near stationary conditions
- Configurable parameters to adjust modification behavior
Architecture
The trajectory modifier uses a plugin-based system where different modification algorithms can be implemented as plugins. Each plugin inherits from the TrajectoryModifierPluginBase
class and implements the required interface.
Plugin Interface
All modifier plugins must inherit from TrajectoryModifierPluginBase
and implement:
-
modify_trajectory()
- Main method to modify trajectory points -
set_up_params()
- Initialize plugin parameters -
on_parameter()
- Handle parameter updates -
is_trajectory_modification_required()
- Determine if modification is needed
Current Plugins
Stop Point Fixer
The Stop Point Fixer plugin addresses trajectory issues when the ego vehicle is stationary or moving at very low speeds. It prevents problematic trajectory points that could cause planning issues by:
- Monitoring ego vehicle velocity and trajectory distance
- Replacing the trajectory with a single stop point when conditions are met
- Ensuring smooth operation during stationary periods
Dependencies
This package depends on the following packages:
-
autoware_internal_planning_msgs
: For candidate trajectory message types -
autoware_planning_msgs
: For output trajectory message types -
autoware_motion_utils
: Motion-related utility functions -
autoware_trajectory
: Trajectory data structures and utilities -
autoware_utils
: Common utility functions
Input/Output
-
Input:
autoware_internal_planning_msgs::msg::CandidateTrajectories
-
Output: Modified
autoware_internal_planning_msgs::msg::CandidateTrajectories
and selectedautoware_planning_msgs::msg::Trajectory
Parameters
-
use_stop_point_fixer
: Enable the stop point fixer modifier plugin (default: true) -
stop_point_fixer.velocity_threshold_mps
: Velocity threshold below which ego vehicle is considered stationary (default: 0.1 m/s) -
stop_point_fixer.min_distance_threshold_m
: Minimum distance threshold to trigger trajectory replacement (default: 1.0 m)
Parameters can be set via YAML configuration files in the config/
directory.
Adding New Modifier Plugins
To add a new modifier plugin:
- Create header and source files in
trajectory_modifier_plugins/
- Inherit from
TrajectoryModifierPluginBase
- Implement the required virtual methods
- Register the plugin in the main node’s
initialize_modifiers()
method - Add plugin-specific parameters to the schema and config files
Package Dependencies
System Dependencies
Dependant Packages
Launch files
- launch/trajectory_modifier.launch.xml
-
- trajectory_modifier_param_path [default: $(find-pkg-share autoware_trajectory_modifier)/config/trajectory_modifier.param.yaml]
- input_candidate_trajectories [default: /planning/diffusion_planner/candidate_trajectories]
- input_odometry [default: /localization/kinematic_state]
- input_acceleration [default: /localization/acceleration]
- output_candidate_trajectories [default: ~/output/candidate_trajectories]
Messages
Services
Plugins
Recent questions tagged autoware_trajectory_modifier at Robotics Stack Exchange
Package Summary
Tags | No category tags. |
Version | 0.39.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 | 2025-09-26 |
Dev Status | UNKNOWN |
Released | UNRELEASED |
Tags | planner ros calibration self-driving-car autonomous-driving autonomous-vehicles ros2 3d-map autoware |
Contributing |
Help Wanted (-)
Good First Issues (-) Pull Requests to Review (-) |
Package Description
Additional Links
Maintainers
- Daniel Sanchez
- Yukihiro Saito
- Go Sakayori
- Shintaro Sakoda
Authors
- Daniel Sanchez
Autoware Trajectory Modifier
The autoware_trajectory_modifier
package provides a plugin-based architecture for post-processing trajectory points to improve trajectory quality and ensure vehicle safety. It takes candidate trajectories and applies various modification algorithms to enhance their feasibility and safety characteristics.
Features
- Plugin-based architecture for extensible trajectory modifications
- Stop point fixing to prevent trajectory issues near stationary conditions
- Configurable parameters to adjust modification behavior
Architecture
The trajectory modifier uses a plugin-based system where different modification algorithms can be implemented as plugins. Each plugin inherits from the TrajectoryModifierPluginBase
class and implements the required interface.
Plugin Interface
All modifier plugins must inherit from TrajectoryModifierPluginBase
and implement:
-
modify_trajectory()
- Main method to modify trajectory points -
set_up_params()
- Initialize plugin parameters -
on_parameter()
- Handle parameter updates -
is_trajectory_modification_required()
- Determine if modification is needed
Current Plugins
Stop Point Fixer
The Stop Point Fixer plugin addresses trajectory issues when the ego vehicle is stationary or moving at very low speeds. It prevents problematic trajectory points that could cause planning issues by:
- Monitoring ego vehicle velocity and trajectory distance
- Replacing the trajectory with a single stop point when conditions are met
- Ensuring smooth operation during stationary periods
Dependencies
This package depends on the following packages:
-
autoware_internal_planning_msgs
: For candidate trajectory message types -
autoware_planning_msgs
: For output trajectory message types -
autoware_motion_utils
: Motion-related utility functions -
autoware_trajectory
: Trajectory data structures and utilities -
autoware_utils
: Common utility functions
Input/Output
-
Input:
autoware_internal_planning_msgs::msg::CandidateTrajectories
-
Output: Modified
autoware_internal_planning_msgs::msg::CandidateTrajectories
and selectedautoware_planning_msgs::msg::Trajectory
Parameters
-
use_stop_point_fixer
: Enable the stop point fixer modifier plugin (default: true) -
stop_point_fixer.velocity_threshold_mps
: Velocity threshold below which ego vehicle is considered stationary (default: 0.1 m/s) -
stop_point_fixer.min_distance_threshold_m
: Minimum distance threshold to trigger trajectory replacement (default: 1.0 m)
Parameters can be set via YAML configuration files in the config/
directory.
Adding New Modifier Plugins
To add a new modifier plugin:
- Create header and source files in
trajectory_modifier_plugins/
- Inherit from
TrajectoryModifierPluginBase
- Implement the required virtual methods
- Register the plugin in the main node’s
initialize_modifiers()
method - Add plugin-specific parameters to the schema and config files
Package Dependencies
System Dependencies
Dependant Packages
Launch files
- launch/trajectory_modifier.launch.xml
-
- trajectory_modifier_param_path [default: $(find-pkg-share autoware_trajectory_modifier)/config/trajectory_modifier.param.yaml]
- input_candidate_trajectories [default: /planning/diffusion_planner/candidate_trajectories]
- input_odometry [default: /localization/kinematic_state]
- input_acceleration [default: /localization/acceleration]
- output_candidate_trajectories [default: ~/output/candidate_trajectories]
Messages
Services
Plugins
Recent questions tagged autoware_trajectory_modifier at Robotics Stack Exchange
Package Summary
Tags | No category tags. |
Version | 0.39.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 | 2025-09-26 |
Dev Status | UNKNOWN |
Released | UNRELEASED |
Tags | planner ros calibration self-driving-car autonomous-driving autonomous-vehicles ros2 3d-map autoware |
Contributing |
Help Wanted (-)
Good First Issues (-) Pull Requests to Review (-) |
Package Description
Additional Links
Maintainers
- Daniel Sanchez
- Yukihiro Saito
- Go Sakayori
- Shintaro Sakoda
Authors
- Daniel Sanchez
Autoware Trajectory Modifier
The autoware_trajectory_modifier
package provides a plugin-based architecture for post-processing trajectory points to improve trajectory quality and ensure vehicle safety. It takes candidate trajectories and applies various modification algorithms to enhance their feasibility and safety characteristics.
Features
- Plugin-based architecture for extensible trajectory modifications
- Stop point fixing to prevent trajectory issues near stationary conditions
- Configurable parameters to adjust modification behavior
Architecture
The trajectory modifier uses a plugin-based system where different modification algorithms can be implemented as plugins. Each plugin inherits from the TrajectoryModifierPluginBase
class and implements the required interface.
Plugin Interface
All modifier plugins must inherit from TrajectoryModifierPluginBase
and implement:
-
modify_trajectory()
- Main method to modify trajectory points -
set_up_params()
- Initialize plugin parameters -
on_parameter()
- Handle parameter updates -
is_trajectory_modification_required()
- Determine if modification is needed
Current Plugins
Stop Point Fixer
The Stop Point Fixer plugin addresses trajectory issues when the ego vehicle is stationary or moving at very low speeds. It prevents problematic trajectory points that could cause planning issues by:
- Monitoring ego vehicle velocity and trajectory distance
- Replacing the trajectory with a single stop point when conditions are met
- Ensuring smooth operation during stationary periods
Dependencies
This package depends on the following packages:
-
autoware_internal_planning_msgs
: For candidate trajectory message types -
autoware_planning_msgs
: For output trajectory message types -
autoware_motion_utils
: Motion-related utility functions -
autoware_trajectory
: Trajectory data structures and utilities -
autoware_utils
: Common utility functions
Input/Output
-
Input:
autoware_internal_planning_msgs::msg::CandidateTrajectories
-
Output: Modified
autoware_internal_planning_msgs::msg::CandidateTrajectories
and selectedautoware_planning_msgs::msg::Trajectory
Parameters
-
use_stop_point_fixer
: Enable the stop point fixer modifier plugin (default: true) -
stop_point_fixer.velocity_threshold_mps
: Velocity threshold below which ego vehicle is considered stationary (default: 0.1 m/s) -
stop_point_fixer.min_distance_threshold_m
: Minimum distance threshold to trigger trajectory replacement (default: 1.0 m)
Parameters can be set via YAML configuration files in the config/
directory.
Adding New Modifier Plugins
To add a new modifier plugin:
- Create header and source files in
trajectory_modifier_plugins/
- Inherit from
TrajectoryModifierPluginBase
- Implement the required virtual methods
- Register the plugin in the main node’s
initialize_modifiers()
method - Add plugin-specific parameters to the schema and config files
Package Dependencies
System Dependencies
Dependant Packages
Launch files
- launch/trajectory_modifier.launch.xml
-
- trajectory_modifier_param_path [default: $(find-pkg-share autoware_trajectory_modifier)/config/trajectory_modifier.param.yaml]
- input_candidate_trajectories [default: /planning/diffusion_planner/candidate_trajectories]
- input_odometry [default: /localization/kinematic_state]
- input_acceleration [default: /localization/acceleration]
- output_candidate_trajectories [default: ~/output/candidate_trajectories]
Messages
Services
Plugins
Recent questions tagged autoware_trajectory_modifier at Robotics Stack Exchange
Package Summary
Tags | No category tags. |
Version | 0.39.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 | 2025-09-26 |
Dev Status | UNKNOWN |
Released | UNRELEASED |
Tags | planner ros calibration self-driving-car autonomous-driving autonomous-vehicles ros2 3d-map autoware |
Contributing |
Help Wanted (-)
Good First Issues (-) Pull Requests to Review (-) |
Package Description
Additional Links
Maintainers
- Daniel Sanchez
- Yukihiro Saito
- Go Sakayori
- Shintaro Sakoda
Authors
- Daniel Sanchez
Autoware Trajectory Modifier
The autoware_trajectory_modifier
package provides a plugin-based architecture for post-processing trajectory points to improve trajectory quality and ensure vehicle safety. It takes candidate trajectories and applies various modification algorithms to enhance their feasibility and safety characteristics.
Features
- Plugin-based architecture for extensible trajectory modifications
- Stop point fixing to prevent trajectory issues near stationary conditions
- Configurable parameters to adjust modification behavior
Architecture
The trajectory modifier uses a plugin-based system where different modification algorithms can be implemented as plugins. Each plugin inherits from the TrajectoryModifierPluginBase
class and implements the required interface.
Plugin Interface
All modifier plugins must inherit from TrajectoryModifierPluginBase
and implement:
-
modify_trajectory()
- Main method to modify trajectory points -
set_up_params()
- Initialize plugin parameters -
on_parameter()
- Handle parameter updates -
is_trajectory_modification_required()
- Determine if modification is needed
Current Plugins
Stop Point Fixer
The Stop Point Fixer plugin addresses trajectory issues when the ego vehicle is stationary or moving at very low speeds. It prevents problematic trajectory points that could cause planning issues by:
- Monitoring ego vehicle velocity and trajectory distance
- Replacing the trajectory with a single stop point when conditions are met
- Ensuring smooth operation during stationary periods
Dependencies
This package depends on the following packages:
-
autoware_internal_planning_msgs
: For candidate trajectory message types -
autoware_planning_msgs
: For output trajectory message types -
autoware_motion_utils
: Motion-related utility functions -
autoware_trajectory
: Trajectory data structures and utilities -
autoware_utils
: Common utility functions
Input/Output
-
Input:
autoware_internal_planning_msgs::msg::CandidateTrajectories
-
Output: Modified
autoware_internal_planning_msgs::msg::CandidateTrajectories
and selectedautoware_planning_msgs::msg::Trajectory
Parameters
-
use_stop_point_fixer
: Enable the stop point fixer modifier plugin (default: true) -
stop_point_fixer.velocity_threshold_mps
: Velocity threshold below which ego vehicle is considered stationary (default: 0.1 m/s) -
stop_point_fixer.min_distance_threshold_m
: Minimum distance threshold to trigger trajectory replacement (default: 1.0 m)
Parameters can be set via YAML configuration files in the config/
directory.
Adding New Modifier Plugins
To add a new modifier plugin:
- Create header and source files in
trajectory_modifier_plugins/
- Inherit from
TrajectoryModifierPluginBase
- Implement the required virtual methods
- Register the plugin in the main node’s
initialize_modifiers()
method - Add plugin-specific parameters to the schema and config files
Package Dependencies
System Dependencies
Dependant Packages
Launch files
- launch/trajectory_modifier.launch.xml
-
- trajectory_modifier_param_path [default: $(find-pkg-share autoware_trajectory_modifier)/config/trajectory_modifier.param.yaml]
- input_candidate_trajectories [default: /planning/diffusion_planner/candidate_trajectories]
- input_odometry [default: /localization/kinematic_state]
- input_acceleration [default: /localization/acceleration]
- output_candidate_trajectories [default: ~/output/candidate_trajectories]
Messages
Services
Plugins
Recent questions tagged autoware_trajectory_modifier at Robotics Stack Exchange
Package Summary
Tags | No category tags. |
Version | 0.39.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 | 2025-09-26 |
Dev Status | UNKNOWN |
Released | UNRELEASED |
Tags | planner ros calibration self-driving-car autonomous-driving autonomous-vehicles ros2 3d-map autoware |
Contributing |
Help Wanted (-)
Good First Issues (-) Pull Requests to Review (-) |
Package Description
Additional Links
Maintainers
- Daniel Sanchez
- Yukihiro Saito
- Go Sakayori
- Shintaro Sakoda
Authors
- Daniel Sanchez
Autoware Trajectory Modifier
The autoware_trajectory_modifier
package provides a plugin-based architecture for post-processing trajectory points to improve trajectory quality and ensure vehicle safety. It takes candidate trajectories and applies various modification algorithms to enhance their feasibility and safety characteristics.
Features
- Plugin-based architecture for extensible trajectory modifications
- Stop point fixing to prevent trajectory issues near stationary conditions
- Configurable parameters to adjust modification behavior
Architecture
The trajectory modifier uses a plugin-based system where different modification algorithms can be implemented as plugins. Each plugin inherits from the TrajectoryModifierPluginBase
class and implements the required interface.
Plugin Interface
All modifier plugins must inherit from TrajectoryModifierPluginBase
and implement:
-
modify_trajectory()
- Main method to modify trajectory points -
set_up_params()
- Initialize plugin parameters -
on_parameter()
- Handle parameter updates -
is_trajectory_modification_required()
- Determine if modification is needed
Current Plugins
Stop Point Fixer
The Stop Point Fixer plugin addresses trajectory issues when the ego vehicle is stationary or moving at very low speeds. It prevents problematic trajectory points that could cause planning issues by:
- Monitoring ego vehicle velocity and trajectory distance
- Replacing the trajectory with a single stop point when conditions are met
- Ensuring smooth operation during stationary periods
Dependencies
This package depends on the following packages:
-
autoware_internal_planning_msgs
: For candidate trajectory message types -
autoware_planning_msgs
: For output trajectory message types -
autoware_motion_utils
: Motion-related utility functions -
autoware_trajectory
: Trajectory data structures and utilities -
autoware_utils
: Common utility functions
Input/Output
-
Input:
autoware_internal_planning_msgs::msg::CandidateTrajectories
-
Output: Modified
autoware_internal_planning_msgs::msg::CandidateTrajectories
and selectedautoware_planning_msgs::msg::Trajectory
Parameters
-
use_stop_point_fixer
: Enable the stop point fixer modifier plugin (default: true) -
stop_point_fixer.velocity_threshold_mps
: Velocity threshold below which ego vehicle is considered stationary (default: 0.1 m/s) -
stop_point_fixer.min_distance_threshold_m
: Minimum distance threshold to trigger trajectory replacement (default: 1.0 m)
Parameters can be set via YAML configuration files in the config/
directory.
Adding New Modifier Plugins
To add a new modifier plugin:
- Create header and source files in
trajectory_modifier_plugins/
- Inherit from
TrajectoryModifierPluginBase
- Implement the required virtual methods
- Register the plugin in the main node’s
initialize_modifiers()
method - Add plugin-specific parameters to the schema and config files
Package Dependencies
System Dependencies
Dependant Packages
Launch files
- launch/trajectory_modifier.launch.xml
-
- trajectory_modifier_param_path [default: $(find-pkg-share autoware_trajectory_modifier)/config/trajectory_modifier.param.yaml]
- input_candidate_trajectories [default: /planning/diffusion_planner/candidate_trajectories]
- input_odometry [default: /localization/kinematic_state]
- input_acceleration [default: /localization/acceleration]
- output_candidate_trajectories [default: ~/output/candidate_trajectories]