Package Summary
| Version | 0.53.0 |
| License | Apache 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-10-23 |
| Dev Status | UNKNOWN |
| Released | UNRELEASED |
| Contributing |
Help Wanted (-)
Good First Issues (-) Pull Requests to Review (-) |
Package Description
Maintainers
- Maxime CLEMENT
- Alqudah Mohammad
- Zulfaqar Azmi
- Takumi Odashima
Authors
- Takamasa Horibe
- Takayuki Murooka
Trajectory Follower
This is the design document for the trajectory_follower package.
Purpose / Use cases
This package provides the interface of longitudinal and lateral controllers used by the node of the autoware_trajectory_follower_node package.
We can implement a detailed controller by deriving the longitudinal and lateral base interfaces.
Design
There are lateral and longitudinal base interface classes and each algorithm inherits from this class to implement. The interface class has the following base functions.
-
isReady(): Check if the control is ready to compute. -
run(): Compute control commands and return to Trajectory Follower Nodes. This must be implemented by inherited algorithms. -
sync(): Input the result of running the lateral controller. Only the longitudinal controller has this function.- steer angle convergence
- allow keeping stopped until steer is converged.
- steer angle convergence
See the Design of Trajectory Follower Nodes for how these functions work in the node.
Separated lateral (steering) and longitudinal (velocity) controls
This longitudinal controller assumes that the roles of lateral and longitudinal control are separated as follows.
- Lateral control computes a target steering to keep the vehicle on the trajectory, assuming perfect velocity tracking.
- Longitudinal control computes a target velocity/acceleration to keep the vehicle velocity on the trajectory speed, assuming perfect trajectory tracking.
Ideally, dealing with the lateral and longitudinal control as a single mixed problem can achieve high performance. In contrast, there are two reasons to provide velocity controller as a stand-alone function, described below.
Complex requirements for longitudinal motion
The longitudinal vehicle behavior that humans expect is difficult to express in a single logic. For example, the expected behavior just before stopping differs depending on whether the ego-position is ahead/behind of the stop line, or whether the current speed is higher/lower than the target speed to achieve a human-like movement.
In addition, some vehicles have difficulty measuring the ego-speed at extremely low speeds. In such cases, a configuration that can improve the functionality of the longitudinal control without affecting the lateral control is important.
There are many characteristics and needs that are unique to longitudinal control. Designing them separately from the lateral control keeps the modules less coupled and improves maintainability.
Nonlinear coupling of lateral and longitudinal motion
The lat-lon mixed control problem is very complex and uses nonlinear optimization to achieve high performance. Since it is difficult to guarantee the convergence of the nonlinear optimization, a simple control logic is also necessary for development.
Also, the benefits of simultaneous longitudinal and lateral control are small if the vehicle doesn’t move at high speed.
Related issues
Changelog for package autoware_trajectory_follower_base
0.53.0 (2026-09-29)
0.52.0 (2026-06-30)
0.51.0 (2026-05-01)
-
Merge remote-tracking branch 'origin/main' into tmp/bot/bump_version_base
-
feat(steer_offset_estimator): implement calibration logic (#12004)
- refactor(steer_offset_estimator): restructure node and estimator implementation
- Updated the CMakeLists.txt to reflect new library and executable structure.
- Removed outdated README and added a new detailed README.md for better documentation.
- Introduced a new node class for steer offset estimation and refactored the estimator logic.
- Added utility functions for pose and steering calculations.
- Implemented tests for the estimator and utility functions to ensure reliability.
- Updated parameters in the schema and configuration files for improved clarity and functionality.
- Removed deprecated files and images to streamline the package. This commit enhances the overall architecture and usability of the steer offset estimator package.
- refactor(steer_offset_estimator): update CMake configuration and remove deprecated files
- Bump CMake minimum version to 3.14 and adjust project structure in CMakeLists.txt.
- Refactor library and executable definitions for clarity and maintainability.
- Remove the main.cpp file as the node is now defined in a separate header and source file.
- Update parameter comments in the configuration file for better clarity.
- Remove the glog dependency from package.xml to streamline dependencies. This commit enhances the organization and readability of the steer offset estimator package.
- docs(steer_offset_estimator): enhance README formatting for mathematical equations
- Improved the formatting of mathematical equations in the README.md to enhance readability by adding line breaks.
- Removed the monitoring section to streamline the documentation. This update aims to provide clearer guidance on the steering offset estimation algorithm and its implementation details.
- docs(steer_offset_estimator): add debug info output section to README
- docs(steer_offset_estimator): improve formatting of algorithm steps in README
- feat(steer_offset_estimator): enhance estimator parameters and update calculations
- Added new parameters: measurement_noise, denominator_floor, and covariance_floor to improve estimation stability.
- Refactored the update logic to incorporate Kalman gain and residual calculations, enhancing the accuracy of the steering offset estimation.
- Updated debug output to reflect new calculation metrics, including kalman_gain and residual. This commit improves the robustness and performance of the steer offset estimator by refining its parameterization and calculation methods.
- feat(steer_offset_estimator): add new parameters for enhanced estimation
- Introduced measurement_noise, denominator_floor, and covariance_floor parameters to the SteerOffsetEstimatorParameters structure.
- Updated the parameter loading function to accommodate the new parameters, improving the configurability of the estimator. This change aims to enhance the performance and stability of the steering offset estimation process by allowing for more precise parameter tuning.
- fix(steer_offset_estimator): update debug output to use standard deviation
- Modified the debug output format in the SteerOffsetEstimatorNode to replace covariance with standard deviation for clarity.
- This change enhances the readability of the debug information by providing a more intuitive metric for uncertainty.
- refactor(steer_offset_estimator): rename and restructure noise parameters for clarity
- Renamed measurement_noise to measurement_noise_covariance and added process_noise_covariance to the SteerOffsetEstimatorParameters structure for better clarity.
- Updated the parameter loading function to reflect these changes, enhancing the configurability of the estimator.
- Refactored the update logic to utilize the new covariance
File truncated at 100 lines see the full file
Package Dependencies
System Dependencies
| Name |
|---|
| eigen |
Dependant Packages
Launch files
Messages
Services
Plugins
Recent questions tagged autoware_trajectory_follower_base at Robotics Stack Exchange
Package Summary
| Version | 0.53.0 |
| License | Apache 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-10-23 |
| Dev Status | UNKNOWN |
| Released | UNRELEASED |
| Contributing |
Help Wanted (-)
Good First Issues (-) Pull Requests to Review (-) |
Package Description
Maintainers
- Maxime CLEMENT
- Alqudah Mohammad
- Zulfaqar Azmi
- Takumi Odashima
Authors
- Takamasa Horibe
- Takayuki Murooka
Trajectory Follower
This is the design document for the trajectory_follower package.
Purpose / Use cases
This package provides the interface of longitudinal and lateral controllers used by the node of the autoware_trajectory_follower_node package.
We can implement a detailed controller by deriving the longitudinal and lateral base interfaces.
Design
There are lateral and longitudinal base interface classes and each algorithm inherits from this class to implement. The interface class has the following base functions.
-
isReady(): Check if the control is ready to compute. -
run(): Compute control commands and return to Trajectory Follower Nodes. This must be implemented by inherited algorithms. -
sync(): Input the result of running the lateral controller. Only the longitudinal controller has this function.- steer angle convergence
- allow keeping stopped until steer is converged.
- steer angle convergence
See the Design of Trajectory Follower Nodes for how these functions work in the node.
Separated lateral (steering) and longitudinal (velocity) controls
This longitudinal controller assumes that the roles of lateral and longitudinal control are separated as follows.
- Lateral control computes a target steering to keep the vehicle on the trajectory, assuming perfect velocity tracking.
- Longitudinal control computes a target velocity/acceleration to keep the vehicle velocity on the trajectory speed, assuming perfect trajectory tracking.
Ideally, dealing with the lateral and longitudinal control as a single mixed problem can achieve high performance. In contrast, there are two reasons to provide velocity controller as a stand-alone function, described below.
Complex requirements for longitudinal motion
The longitudinal vehicle behavior that humans expect is difficult to express in a single logic. For example, the expected behavior just before stopping differs depending on whether the ego-position is ahead/behind of the stop line, or whether the current speed is higher/lower than the target speed to achieve a human-like movement.
In addition, some vehicles have difficulty measuring the ego-speed at extremely low speeds. In such cases, a configuration that can improve the functionality of the longitudinal control without affecting the lateral control is important.
There are many characteristics and needs that are unique to longitudinal control. Designing them separately from the lateral control keeps the modules less coupled and improves maintainability.
Nonlinear coupling of lateral and longitudinal motion
The lat-lon mixed control problem is very complex and uses nonlinear optimization to achieve high performance. Since it is difficult to guarantee the convergence of the nonlinear optimization, a simple control logic is also necessary for development.
Also, the benefits of simultaneous longitudinal and lateral control are small if the vehicle doesn’t move at high speed.
Related issues
Changelog for package autoware_trajectory_follower_base
0.53.0 (2026-09-29)
0.52.0 (2026-06-30)
0.51.0 (2026-05-01)
-
Merge remote-tracking branch 'origin/main' into tmp/bot/bump_version_base
-
feat(steer_offset_estimator): implement calibration logic (#12004)
- refactor(steer_offset_estimator): restructure node and estimator implementation
- Updated the CMakeLists.txt to reflect new library and executable structure.
- Removed outdated README and added a new detailed README.md for better documentation.
- Introduced a new node class for steer offset estimation and refactored the estimator logic.
- Added utility functions for pose and steering calculations.
- Implemented tests for the estimator and utility functions to ensure reliability.
- Updated parameters in the schema and configuration files for improved clarity and functionality.
- Removed deprecated files and images to streamline the package. This commit enhances the overall architecture and usability of the steer offset estimator package.
- refactor(steer_offset_estimator): update CMake configuration and remove deprecated files
- Bump CMake minimum version to 3.14 and adjust project structure in CMakeLists.txt.
- Refactor library and executable definitions for clarity and maintainability.
- Remove the main.cpp file as the node is now defined in a separate header and source file.
- Update parameter comments in the configuration file for better clarity.
- Remove the glog dependency from package.xml to streamline dependencies. This commit enhances the organization and readability of the steer offset estimator package.
- docs(steer_offset_estimator): enhance README formatting for mathematical equations
- Improved the formatting of mathematical equations in the README.md to enhance readability by adding line breaks.
- Removed the monitoring section to streamline the documentation. This update aims to provide clearer guidance on the steering offset estimation algorithm and its implementation details.
- docs(steer_offset_estimator): add debug info output section to README
- docs(steer_offset_estimator): improve formatting of algorithm steps in README
- feat(steer_offset_estimator): enhance estimator parameters and update calculations
- Added new parameters: measurement_noise, denominator_floor, and covariance_floor to improve estimation stability.
- Refactored the update logic to incorporate Kalman gain and residual calculations, enhancing the accuracy of the steering offset estimation.
- Updated debug output to reflect new calculation metrics, including kalman_gain and residual. This commit improves the robustness and performance of the steer offset estimator by refining its parameterization and calculation methods.
- feat(steer_offset_estimator): add new parameters for enhanced estimation
- Introduced measurement_noise, denominator_floor, and covariance_floor parameters to the SteerOffsetEstimatorParameters structure.
- Updated the parameter loading function to accommodate the new parameters, improving the configurability of the estimator. This change aims to enhance the performance and stability of the steering offset estimation process by allowing for more precise parameter tuning.
- fix(steer_offset_estimator): update debug output to use standard deviation
- Modified the debug output format in the SteerOffsetEstimatorNode to replace covariance with standard deviation for clarity.
- This change enhances the readability of the debug information by providing a more intuitive metric for uncertainty.
- refactor(steer_offset_estimator): rename and restructure noise parameters for clarity
- Renamed measurement_noise to measurement_noise_covariance and added process_noise_covariance to the SteerOffsetEstimatorParameters structure for better clarity.
- Updated the parameter loading function to reflect these changes, enhancing the configurability of the estimator.
- Refactored the update logic to utilize the new covariance
File truncated at 100 lines see the full file
Package Dependencies
System Dependencies
| Name |
|---|
| eigen |
Dependant Packages
Launch files
Messages
Services
Plugins
Recent questions tagged autoware_trajectory_follower_base at Robotics Stack Exchange
Package Summary
| Version | 0.53.0 |
| License | Apache 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-10-23 |
| Dev Status | UNKNOWN |
| Released | UNRELEASED |
| Contributing |
Help Wanted (-)
Good First Issues (-) Pull Requests to Review (-) |
Package Description
Maintainers
- Maxime CLEMENT
- Alqudah Mohammad
- Zulfaqar Azmi
- Takumi Odashima
Authors
- Takamasa Horibe
- Takayuki Murooka
Trajectory Follower
This is the design document for the trajectory_follower package.
Purpose / Use cases
This package provides the interface of longitudinal and lateral controllers used by the node of the autoware_trajectory_follower_node package.
We can implement a detailed controller by deriving the longitudinal and lateral base interfaces.
Design
There are lateral and longitudinal base interface classes and each algorithm inherits from this class to implement. The interface class has the following base functions.
-
isReady(): Check if the control is ready to compute. -
run(): Compute control commands and return to Trajectory Follower Nodes. This must be implemented by inherited algorithms. -
sync(): Input the result of running the lateral controller. Only the longitudinal controller has this function.- steer angle convergence
- allow keeping stopped until steer is converged.
- steer angle convergence
See the Design of Trajectory Follower Nodes for how these functions work in the node.
Separated lateral (steering) and longitudinal (velocity) controls
This longitudinal controller assumes that the roles of lateral and longitudinal control are separated as follows.
- Lateral control computes a target steering to keep the vehicle on the trajectory, assuming perfect velocity tracking.
- Longitudinal control computes a target velocity/acceleration to keep the vehicle velocity on the trajectory speed, assuming perfect trajectory tracking.
Ideally, dealing with the lateral and longitudinal control as a single mixed problem can achieve high performance. In contrast, there are two reasons to provide velocity controller as a stand-alone function, described below.
Complex requirements for longitudinal motion
The longitudinal vehicle behavior that humans expect is difficult to express in a single logic. For example, the expected behavior just before stopping differs depending on whether the ego-position is ahead/behind of the stop line, or whether the current speed is higher/lower than the target speed to achieve a human-like movement.
In addition, some vehicles have difficulty measuring the ego-speed at extremely low speeds. In such cases, a configuration that can improve the functionality of the longitudinal control without affecting the lateral control is important.
There are many characteristics and needs that are unique to longitudinal control. Designing them separately from the lateral control keeps the modules less coupled and improves maintainability.
Nonlinear coupling of lateral and longitudinal motion
The lat-lon mixed control problem is very complex and uses nonlinear optimization to achieve high performance. Since it is difficult to guarantee the convergence of the nonlinear optimization, a simple control logic is also necessary for development.
Also, the benefits of simultaneous longitudinal and lateral control are small if the vehicle doesn’t move at high speed.
Related issues
Changelog for package autoware_trajectory_follower_base
0.53.0 (2026-09-29)
0.52.0 (2026-06-30)
0.51.0 (2026-05-01)
-
Merge remote-tracking branch 'origin/main' into tmp/bot/bump_version_base
-
feat(steer_offset_estimator): implement calibration logic (#12004)
- refactor(steer_offset_estimator): restructure node and estimator implementation
- Updated the CMakeLists.txt to reflect new library and executable structure.
- Removed outdated README and added a new detailed README.md for better documentation.
- Introduced a new node class for steer offset estimation and refactored the estimator logic.
- Added utility functions for pose and steering calculations.
- Implemented tests for the estimator and utility functions to ensure reliability.
- Updated parameters in the schema and configuration files for improved clarity and functionality.
- Removed deprecated files and images to streamline the package. This commit enhances the overall architecture and usability of the steer offset estimator package.
- refactor(steer_offset_estimator): update CMake configuration and remove deprecated files
- Bump CMake minimum version to 3.14 and adjust project structure in CMakeLists.txt.
- Refactor library and executable definitions for clarity and maintainability.
- Remove the main.cpp file as the node is now defined in a separate header and source file.
- Update parameter comments in the configuration file for better clarity.
- Remove the glog dependency from package.xml to streamline dependencies. This commit enhances the organization and readability of the steer offset estimator package.
- docs(steer_offset_estimator): enhance README formatting for mathematical equations
- Improved the formatting of mathematical equations in the README.md to enhance readability by adding line breaks.
- Removed the monitoring section to streamline the documentation. This update aims to provide clearer guidance on the steering offset estimation algorithm and its implementation details.
- docs(steer_offset_estimator): add debug info output section to README
- docs(steer_offset_estimator): improve formatting of algorithm steps in README
- feat(steer_offset_estimator): enhance estimator parameters and update calculations
- Added new parameters: measurement_noise, denominator_floor, and covariance_floor to improve estimation stability.
- Refactored the update logic to incorporate Kalman gain and residual calculations, enhancing the accuracy of the steering offset estimation.
- Updated debug output to reflect new calculation metrics, including kalman_gain and residual. This commit improves the robustness and performance of the steer offset estimator by refining its parameterization and calculation methods.
- feat(steer_offset_estimator): add new parameters for enhanced estimation
- Introduced measurement_noise, denominator_floor, and covariance_floor parameters to the SteerOffsetEstimatorParameters structure.
- Updated the parameter loading function to accommodate the new parameters, improving the configurability of the estimator. This change aims to enhance the performance and stability of the steering offset estimation process by allowing for more precise parameter tuning.
- fix(steer_offset_estimator): update debug output to use standard deviation
- Modified the debug output format in the SteerOffsetEstimatorNode to replace covariance with standard deviation for clarity.
- This change enhances the readability of the debug information by providing a more intuitive metric for uncertainty.
- refactor(steer_offset_estimator): rename and restructure noise parameters for clarity
- Renamed measurement_noise to measurement_noise_covariance and added process_noise_covariance to the SteerOffsetEstimatorParameters structure for better clarity.
- Updated the parameter loading function to reflect these changes, enhancing the configurability of the estimator.
- Refactored the update logic to utilize the new covariance
File truncated at 100 lines see the full file
Package Dependencies
System Dependencies
| Name |
|---|
| eigen |
Dependant Packages
Launch files
Messages
Services
Plugins
Recent questions tagged autoware_trajectory_follower_base at Robotics Stack Exchange
Package Summary
| Version | 0.53.0 |
| License | Apache 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-10-23 |
| Dev Status | UNKNOWN |
| Released | UNRELEASED |
| Contributing |
Help Wanted (-)
Good First Issues (-) Pull Requests to Review (-) |
Package Description
Maintainers
- Maxime CLEMENT
- Alqudah Mohammad
- Zulfaqar Azmi
- Takumi Odashima
Authors
- Takamasa Horibe
- Takayuki Murooka
Trajectory Follower
This is the design document for the trajectory_follower package.
Purpose / Use cases
This package provides the interface of longitudinal and lateral controllers used by the node of the autoware_trajectory_follower_node package.
We can implement a detailed controller by deriving the longitudinal and lateral base interfaces.
Design
There are lateral and longitudinal base interface classes and each algorithm inherits from this class to implement. The interface class has the following base functions.
-
isReady(): Check if the control is ready to compute. -
run(): Compute control commands and return to Trajectory Follower Nodes. This must be implemented by inherited algorithms. -
sync(): Input the result of running the lateral controller. Only the longitudinal controller has this function.- steer angle convergence
- allow keeping stopped until steer is converged.
- steer angle convergence
See the Design of Trajectory Follower Nodes for how these functions work in the node.
Separated lateral (steering) and longitudinal (velocity) controls
This longitudinal controller assumes that the roles of lateral and longitudinal control are separated as follows.
- Lateral control computes a target steering to keep the vehicle on the trajectory, assuming perfect velocity tracking.
- Longitudinal control computes a target velocity/acceleration to keep the vehicle velocity on the trajectory speed, assuming perfect trajectory tracking.
Ideally, dealing with the lateral and longitudinal control as a single mixed problem can achieve high performance. In contrast, there are two reasons to provide velocity controller as a stand-alone function, described below.
Complex requirements for longitudinal motion
The longitudinal vehicle behavior that humans expect is difficult to express in a single logic. For example, the expected behavior just before stopping differs depending on whether the ego-position is ahead/behind of the stop line, or whether the current speed is higher/lower than the target speed to achieve a human-like movement.
In addition, some vehicles have difficulty measuring the ego-speed at extremely low speeds. In such cases, a configuration that can improve the functionality of the longitudinal control without affecting the lateral control is important.
There are many characteristics and needs that are unique to longitudinal control. Designing them separately from the lateral control keeps the modules less coupled and improves maintainability.
Nonlinear coupling of lateral and longitudinal motion
The lat-lon mixed control problem is very complex and uses nonlinear optimization to achieve high performance. Since it is difficult to guarantee the convergence of the nonlinear optimization, a simple control logic is also necessary for development.
Also, the benefits of simultaneous longitudinal and lateral control are small if the vehicle doesn’t move at high speed.
Related issues
Changelog for package autoware_trajectory_follower_base
0.53.0 (2026-09-29)
0.52.0 (2026-06-30)
0.51.0 (2026-05-01)
-
Merge remote-tracking branch 'origin/main' into tmp/bot/bump_version_base
-
feat(steer_offset_estimator): implement calibration logic (#12004)
- refactor(steer_offset_estimator): restructure node and estimator implementation
- Updated the CMakeLists.txt to reflect new library and executable structure.
- Removed outdated README and added a new detailed README.md for better documentation.
- Introduced a new node class for steer offset estimation and refactored the estimator logic.
- Added utility functions for pose and steering calculations.
- Implemented tests for the estimator and utility functions to ensure reliability.
- Updated parameters in the schema and configuration files for improved clarity and functionality.
- Removed deprecated files and images to streamline the package. This commit enhances the overall architecture and usability of the steer offset estimator package.
- refactor(steer_offset_estimator): update CMake configuration and remove deprecated files
- Bump CMake minimum version to 3.14 and adjust project structure in CMakeLists.txt.
- Refactor library and executable definitions for clarity and maintainability.
- Remove the main.cpp file as the node is now defined in a separate header and source file.
- Update parameter comments in the configuration file for better clarity.
- Remove the glog dependency from package.xml to streamline dependencies. This commit enhances the organization and readability of the steer offset estimator package.
- docs(steer_offset_estimator): enhance README formatting for mathematical equations
- Improved the formatting of mathematical equations in the README.md to enhance readability by adding line breaks.
- Removed the monitoring section to streamline the documentation. This update aims to provide clearer guidance on the steering offset estimation algorithm and its implementation details.
- docs(steer_offset_estimator): add debug info output section to README
- docs(steer_offset_estimator): improve formatting of algorithm steps in README
- feat(steer_offset_estimator): enhance estimator parameters and update calculations
- Added new parameters: measurement_noise, denominator_floor, and covariance_floor to improve estimation stability.
- Refactored the update logic to incorporate Kalman gain and residual calculations, enhancing the accuracy of the steering offset estimation.
- Updated debug output to reflect new calculation metrics, including kalman_gain and residual. This commit improves the robustness and performance of the steer offset estimator by refining its parameterization and calculation methods.
- feat(steer_offset_estimator): add new parameters for enhanced estimation
- Introduced measurement_noise, denominator_floor, and covariance_floor parameters to the SteerOffsetEstimatorParameters structure.
- Updated the parameter loading function to accommodate the new parameters, improving the configurability of the estimator. This change aims to enhance the performance and stability of the steering offset estimation process by allowing for more precise parameter tuning.
- fix(steer_offset_estimator): update debug output to use standard deviation
- Modified the debug output format in the SteerOffsetEstimatorNode to replace covariance with standard deviation for clarity.
- This change enhances the readability of the debug information by providing a more intuitive metric for uncertainty.
- refactor(steer_offset_estimator): rename and restructure noise parameters for clarity
- Renamed measurement_noise to measurement_noise_covariance and added process_noise_covariance to the SteerOffsetEstimatorParameters structure for better clarity.
- Updated the parameter loading function to reflect these changes, enhancing the configurability of the estimator.
- Refactored the update logic to utilize the new covariance
File truncated at 100 lines see the full file
Package Dependencies
System Dependencies
| Name |
|---|
| eigen |
Dependant Packages
Launch files
Messages
Services
Plugins
Recent questions tagged autoware_trajectory_follower_base at Robotics Stack Exchange
Package Summary
| Version | 0.53.0 |
| License | Apache 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-10-23 |
| Dev Status | UNKNOWN |
| Released | UNRELEASED |
| Contributing |
Help Wanted (-)
Good First Issues (-) Pull Requests to Review (-) |
Package Description
Maintainers
- Maxime CLEMENT
- Alqudah Mohammad
- Zulfaqar Azmi
- Takumi Odashima
Authors
- Takamasa Horibe
- Takayuki Murooka
Trajectory Follower
This is the design document for the trajectory_follower package.
Purpose / Use cases
This package provides the interface of longitudinal and lateral controllers used by the node of the autoware_trajectory_follower_node package.
We can implement a detailed controller by deriving the longitudinal and lateral base interfaces.
Design
There are lateral and longitudinal base interface classes and each algorithm inherits from this class to implement. The interface class has the following base functions.
-
isReady(): Check if the control is ready to compute. -
run(): Compute control commands and return to Trajectory Follower Nodes. This must be implemented by inherited algorithms. -
sync(): Input the result of running the lateral controller. Only the longitudinal controller has this function.- steer angle convergence
- allow keeping stopped until steer is converged.
- steer angle convergence
See the Design of Trajectory Follower Nodes for how these functions work in the node.
Separated lateral (steering) and longitudinal (velocity) controls
This longitudinal controller assumes that the roles of lateral and longitudinal control are separated as follows.
- Lateral control computes a target steering to keep the vehicle on the trajectory, assuming perfect velocity tracking.
- Longitudinal control computes a target velocity/acceleration to keep the vehicle velocity on the trajectory speed, assuming perfect trajectory tracking.
Ideally, dealing with the lateral and longitudinal control as a single mixed problem can achieve high performance. In contrast, there are two reasons to provide velocity controller as a stand-alone function, described below.
Complex requirements for longitudinal motion
The longitudinal vehicle behavior that humans expect is difficult to express in a single logic. For example, the expected behavior just before stopping differs depending on whether the ego-position is ahead/behind of the stop line, or whether the current speed is higher/lower than the target speed to achieve a human-like movement.
In addition, some vehicles have difficulty measuring the ego-speed at extremely low speeds. In such cases, a configuration that can improve the functionality of the longitudinal control without affecting the lateral control is important.
There are many characteristics and needs that are unique to longitudinal control. Designing them separately from the lateral control keeps the modules less coupled and improves maintainability.
Nonlinear coupling of lateral and longitudinal motion
The lat-lon mixed control problem is very complex and uses nonlinear optimization to achieve high performance. Since it is difficult to guarantee the convergence of the nonlinear optimization, a simple control logic is also necessary for development.
Also, the benefits of simultaneous longitudinal and lateral control are small if the vehicle doesn’t move at high speed.
Related issues
Changelog for package autoware_trajectory_follower_base
0.53.0 (2026-09-29)
0.52.0 (2026-06-30)
0.51.0 (2026-05-01)
-
Merge remote-tracking branch 'origin/main' into tmp/bot/bump_version_base
-
feat(steer_offset_estimator): implement calibration logic (#12004)
- refactor(steer_offset_estimator): restructure node and estimator implementation
- Updated the CMakeLists.txt to reflect new library and executable structure.
- Removed outdated README and added a new detailed README.md for better documentation.
- Introduced a new node class for steer offset estimation and refactored the estimator logic.
- Added utility functions for pose and steering calculations.
- Implemented tests for the estimator and utility functions to ensure reliability.
- Updated parameters in the schema and configuration files for improved clarity and functionality.
- Removed deprecated files and images to streamline the package. This commit enhances the overall architecture and usability of the steer offset estimator package.
- refactor(steer_offset_estimator): update CMake configuration and remove deprecated files
- Bump CMake minimum version to 3.14 and adjust project structure in CMakeLists.txt.
- Refactor library and executable definitions for clarity and maintainability.
- Remove the main.cpp file as the node is now defined in a separate header and source file.
- Update parameter comments in the configuration file for better clarity.
- Remove the glog dependency from package.xml to streamline dependencies. This commit enhances the organization and readability of the steer offset estimator package.
- docs(steer_offset_estimator): enhance README formatting for mathematical equations
- Improved the formatting of mathematical equations in the README.md to enhance readability by adding line breaks.
- Removed the monitoring section to streamline the documentation. This update aims to provide clearer guidance on the steering offset estimation algorithm and its implementation details.
- docs(steer_offset_estimator): add debug info output section to README
- docs(steer_offset_estimator): improve formatting of algorithm steps in README
- feat(steer_offset_estimator): enhance estimator parameters and update calculations
- Added new parameters: measurement_noise, denominator_floor, and covariance_floor to improve estimation stability.
- Refactored the update logic to incorporate Kalman gain and residual calculations, enhancing the accuracy of the steering offset estimation.
- Updated debug output to reflect new calculation metrics, including kalman_gain and residual. This commit improves the robustness and performance of the steer offset estimator by refining its parameterization and calculation methods.
- feat(steer_offset_estimator): add new parameters for enhanced estimation
- Introduced measurement_noise, denominator_floor, and covariance_floor parameters to the SteerOffsetEstimatorParameters structure.
- Updated the parameter loading function to accommodate the new parameters, improving the configurability of the estimator. This change aims to enhance the performance and stability of the steering offset estimation process by allowing for more precise parameter tuning.
- fix(steer_offset_estimator): update debug output to use standard deviation
- Modified the debug output format in the SteerOffsetEstimatorNode to replace covariance with standard deviation for clarity.
- This change enhances the readability of the debug information by providing a more intuitive metric for uncertainty.
- refactor(steer_offset_estimator): rename and restructure noise parameters for clarity
- Renamed measurement_noise to measurement_noise_covariance and added process_noise_covariance to the SteerOffsetEstimatorParameters structure for better clarity.
- Updated the parameter loading function to reflect these changes, enhancing the configurability of the estimator.
- Refactored the update logic to utilize the new covariance
File truncated at 100 lines see the full file
Package Dependencies
System Dependencies
| Name |
|---|
| eigen |
Dependant Packages
Launch files
Messages
Services
Plugins
Recent questions tagged autoware_trajectory_follower_base at Robotics Stack Exchange
Package Summary
| Version | 0.53.0 |
| License | Apache 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-10-23 |
| Dev Status | UNKNOWN |
| Released | UNRELEASED |
| Contributing |
Help Wanted (-)
Good First Issues (-) Pull Requests to Review (-) |
Package Description
Maintainers
- Maxime CLEMENT
- Alqudah Mohammad
- Zulfaqar Azmi
- Takumi Odashima
Authors
- Takamasa Horibe
- Takayuki Murooka
Trajectory Follower
This is the design document for the trajectory_follower package.
Purpose / Use cases
This package provides the interface of longitudinal and lateral controllers used by the node of the autoware_trajectory_follower_node package.
We can implement a detailed controller by deriving the longitudinal and lateral base interfaces.
Design
There are lateral and longitudinal base interface classes and each algorithm inherits from this class to implement. The interface class has the following base functions.
-
isReady(): Check if the control is ready to compute. -
run(): Compute control commands and return to Trajectory Follower Nodes. This must be implemented by inherited algorithms. -
sync(): Input the result of running the lateral controller. Only the longitudinal controller has this function.- steer angle convergence
- allow keeping stopped until steer is converged.
- steer angle convergence
See the Design of Trajectory Follower Nodes for how these functions work in the node.
Separated lateral (steering) and longitudinal (velocity) controls
This longitudinal controller assumes that the roles of lateral and longitudinal control are separated as follows.
- Lateral control computes a target steering to keep the vehicle on the trajectory, assuming perfect velocity tracking.
- Longitudinal control computes a target velocity/acceleration to keep the vehicle velocity on the trajectory speed, assuming perfect trajectory tracking.
Ideally, dealing with the lateral and longitudinal control as a single mixed problem can achieve high performance. In contrast, there are two reasons to provide velocity controller as a stand-alone function, described below.
Complex requirements for longitudinal motion
The longitudinal vehicle behavior that humans expect is difficult to express in a single logic. For example, the expected behavior just before stopping differs depending on whether the ego-position is ahead/behind of the stop line, or whether the current speed is higher/lower than the target speed to achieve a human-like movement.
In addition, some vehicles have difficulty measuring the ego-speed at extremely low speeds. In such cases, a configuration that can improve the functionality of the longitudinal control without affecting the lateral control is important.
There are many characteristics and needs that are unique to longitudinal control. Designing them separately from the lateral control keeps the modules less coupled and improves maintainability.
Nonlinear coupling of lateral and longitudinal motion
The lat-lon mixed control problem is very complex and uses nonlinear optimization to achieve high performance. Since it is difficult to guarantee the convergence of the nonlinear optimization, a simple control logic is also necessary for development.
Also, the benefits of simultaneous longitudinal and lateral control are small if the vehicle doesn’t move at high speed.
Related issues
Changelog for package autoware_trajectory_follower_base
0.53.0 (2026-09-29)
0.52.0 (2026-06-30)
0.51.0 (2026-05-01)
-
Merge remote-tracking branch 'origin/main' into tmp/bot/bump_version_base
-
feat(steer_offset_estimator): implement calibration logic (#12004)
- refactor(steer_offset_estimator): restructure node and estimator implementation
- Updated the CMakeLists.txt to reflect new library and executable structure.
- Removed outdated README and added a new detailed README.md for better documentation.
- Introduced a new node class for steer offset estimation and refactored the estimator logic.
- Added utility functions for pose and steering calculations.
- Implemented tests for the estimator and utility functions to ensure reliability.
- Updated parameters in the schema and configuration files for improved clarity and functionality.
- Removed deprecated files and images to streamline the package. This commit enhances the overall architecture and usability of the steer offset estimator package.
- refactor(steer_offset_estimator): update CMake configuration and remove deprecated files
- Bump CMake minimum version to 3.14 and adjust project structure in CMakeLists.txt.
- Refactor library and executable definitions for clarity and maintainability.
- Remove the main.cpp file as the node is now defined in a separate header and source file.
- Update parameter comments in the configuration file for better clarity.
- Remove the glog dependency from package.xml to streamline dependencies. This commit enhances the organization and readability of the steer offset estimator package.
- docs(steer_offset_estimator): enhance README formatting for mathematical equations
- Improved the formatting of mathematical equations in the README.md to enhance readability by adding line breaks.
- Removed the monitoring section to streamline the documentation. This update aims to provide clearer guidance on the steering offset estimation algorithm and its implementation details.
- docs(steer_offset_estimator): add debug info output section to README
- docs(steer_offset_estimator): improve formatting of algorithm steps in README
- feat(steer_offset_estimator): enhance estimator parameters and update calculations
- Added new parameters: measurement_noise, denominator_floor, and covariance_floor to improve estimation stability.
- Refactored the update logic to incorporate Kalman gain and residual calculations, enhancing the accuracy of the steering offset estimation.
- Updated debug output to reflect new calculation metrics, including kalman_gain and residual. This commit improves the robustness and performance of the steer offset estimator by refining its parameterization and calculation methods.
- feat(steer_offset_estimator): add new parameters for enhanced estimation
- Introduced measurement_noise, denominator_floor, and covariance_floor parameters to the SteerOffsetEstimatorParameters structure.
- Updated the parameter loading function to accommodate the new parameters, improving the configurability of the estimator. This change aims to enhance the performance and stability of the steering offset estimation process by allowing for more precise parameter tuning.
- fix(steer_offset_estimator): update debug output to use standard deviation
- Modified the debug output format in the SteerOffsetEstimatorNode to replace covariance with standard deviation for clarity.
- This change enhances the readability of the debug information by providing a more intuitive metric for uncertainty.
- refactor(steer_offset_estimator): rename and restructure noise parameters for clarity
- Renamed measurement_noise to measurement_noise_covariance and added process_noise_covariance to the SteerOffsetEstimatorParameters structure for better clarity.
- Updated the parameter loading function to reflect these changes, enhancing the configurability of the estimator.
- Refactored the update logic to utilize the new covariance
File truncated at 100 lines see the full file
Package Dependencies
System Dependencies
| Name |
|---|
| eigen |
Dependant Packages
Launch files
Messages
Services
Plugins
Recent questions tagged autoware_trajectory_follower_base at Robotics Stack Exchange
Package Summary
| Version | 0.53.0 |
| License | Apache 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-10-23 |
| Dev Status | UNKNOWN |
| Released | UNRELEASED |
| Contributing |
Help Wanted (-)
Good First Issues (-) Pull Requests to Review (-) |
Package Description
Maintainers
- Maxime CLEMENT
- Alqudah Mohammad
- Zulfaqar Azmi
- Takumi Odashima
Authors
- Takamasa Horibe
- Takayuki Murooka
Trajectory Follower
This is the design document for the trajectory_follower package.
Purpose / Use cases
This package provides the interface of longitudinal and lateral controllers used by the node of the autoware_trajectory_follower_node package.
We can implement a detailed controller by deriving the longitudinal and lateral base interfaces.
Design
There are lateral and longitudinal base interface classes and each algorithm inherits from this class to implement. The interface class has the following base functions.
-
isReady(): Check if the control is ready to compute. -
run(): Compute control commands and return to Trajectory Follower Nodes. This must be implemented by inherited algorithms. -
sync(): Input the result of running the lateral controller. Only the longitudinal controller has this function.- steer angle convergence
- allow keeping stopped until steer is converged.
- steer angle convergence
See the Design of Trajectory Follower Nodes for how these functions work in the node.
Separated lateral (steering) and longitudinal (velocity) controls
This longitudinal controller assumes that the roles of lateral and longitudinal control are separated as follows.
- Lateral control computes a target steering to keep the vehicle on the trajectory, assuming perfect velocity tracking.
- Longitudinal control computes a target velocity/acceleration to keep the vehicle velocity on the trajectory speed, assuming perfect trajectory tracking.
Ideally, dealing with the lateral and longitudinal control as a single mixed problem can achieve high performance. In contrast, there are two reasons to provide velocity controller as a stand-alone function, described below.
Complex requirements for longitudinal motion
The longitudinal vehicle behavior that humans expect is difficult to express in a single logic. For example, the expected behavior just before stopping differs depending on whether the ego-position is ahead/behind of the stop line, or whether the current speed is higher/lower than the target speed to achieve a human-like movement.
In addition, some vehicles have difficulty measuring the ego-speed at extremely low speeds. In such cases, a configuration that can improve the functionality of the longitudinal control without affecting the lateral control is important.
There are many characteristics and needs that are unique to longitudinal control. Designing them separately from the lateral control keeps the modules less coupled and improves maintainability.
Nonlinear coupling of lateral and longitudinal motion
The lat-lon mixed control problem is very complex and uses nonlinear optimization to achieve high performance. Since it is difficult to guarantee the convergence of the nonlinear optimization, a simple control logic is also necessary for development.
Also, the benefits of simultaneous longitudinal and lateral control are small if the vehicle doesn’t move at high speed.
Related issues
Changelog for package autoware_trajectory_follower_base
0.53.0 (2026-09-29)
0.52.0 (2026-06-30)
0.51.0 (2026-05-01)
-
Merge remote-tracking branch 'origin/main' into tmp/bot/bump_version_base
-
feat(steer_offset_estimator): implement calibration logic (#12004)
- refactor(steer_offset_estimator): restructure node and estimator implementation
- Updated the CMakeLists.txt to reflect new library and executable structure.
- Removed outdated README and added a new detailed README.md for better documentation.
- Introduced a new node class for steer offset estimation and refactored the estimator logic.
- Added utility functions for pose and steering calculations.
- Implemented tests for the estimator and utility functions to ensure reliability.
- Updated parameters in the schema and configuration files for improved clarity and functionality.
- Removed deprecated files and images to streamline the package. This commit enhances the overall architecture and usability of the steer offset estimator package.
- refactor(steer_offset_estimator): update CMake configuration and remove deprecated files
- Bump CMake minimum version to 3.14 and adjust project structure in CMakeLists.txt.
- Refactor library and executable definitions for clarity and maintainability.
- Remove the main.cpp file as the node is now defined in a separate header and source file.
- Update parameter comments in the configuration file for better clarity.
- Remove the glog dependency from package.xml to streamline dependencies. This commit enhances the organization and readability of the steer offset estimator package.
- docs(steer_offset_estimator): enhance README formatting for mathematical equations
- Improved the formatting of mathematical equations in the README.md to enhance readability by adding line breaks.
- Removed the monitoring section to streamline the documentation. This update aims to provide clearer guidance on the steering offset estimation algorithm and its implementation details.
- docs(steer_offset_estimator): add debug info output section to README
- docs(steer_offset_estimator): improve formatting of algorithm steps in README
- feat(steer_offset_estimator): enhance estimator parameters and update calculations
- Added new parameters: measurement_noise, denominator_floor, and covariance_floor to improve estimation stability.
- Refactored the update logic to incorporate Kalman gain and residual calculations, enhancing the accuracy of the steering offset estimation.
- Updated debug output to reflect new calculation metrics, including kalman_gain and residual. This commit improves the robustness and performance of the steer offset estimator by refining its parameterization and calculation methods.
- feat(steer_offset_estimator): add new parameters for enhanced estimation
- Introduced measurement_noise, denominator_floor, and covariance_floor parameters to the SteerOffsetEstimatorParameters structure.
- Updated the parameter loading function to accommodate the new parameters, improving the configurability of the estimator. This change aims to enhance the performance and stability of the steering offset estimation process by allowing for more precise parameter tuning.
- fix(steer_offset_estimator): update debug output to use standard deviation
- Modified the debug output format in the SteerOffsetEstimatorNode to replace covariance with standard deviation for clarity.
- This change enhances the readability of the debug information by providing a more intuitive metric for uncertainty.
- refactor(steer_offset_estimator): rename and restructure noise parameters for clarity
- Renamed measurement_noise to measurement_noise_covariance and added process_noise_covariance to the SteerOffsetEstimatorParameters structure for better clarity.
- Updated the parameter loading function to reflect these changes, enhancing the configurability of the estimator.
- Refactored the update logic to utilize the new covariance
File truncated at 100 lines see the full file
Package Dependencies
System Dependencies
| Name |
|---|
| eigen |
Dependant Packages
Launch files
Messages
Services
Plugins
Recent questions tagged autoware_trajectory_follower_base at Robotics Stack Exchange
Package Summary
| Version | 0.53.0 |
| License | Apache 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-10-23 |
| Dev Status | UNKNOWN |
| Released | UNRELEASED |
| Contributing |
Help Wanted (-)
Good First Issues (-) Pull Requests to Review (-) |
Package Description
Maintainers
- Maxime CLEMENT
- Alqudah Mohammad
- Zulfaqar Azmi
- Takumi Odashima
Authors
- Takamasa Horibe
- Takayuki Murooka
Trajectory Follower
This is the design document for the trajectory_follower package.
Purpose / Use cases
This package provides the interface of longitudinal and lateral controllers used by the node of the autoware_trajectory_follower_node package.
We can implement a detailed controller by deriving the longitudinal and lateral base interfaces.
Design
There are lateral and longitudinal base interface classes and each algorithm inherits from this class to implement. The interface class has the following base functions.
-
isReady(): Check if the control is ready to compute. -
run(): Compute control commands and return to Trajectory Follower Nodes. This must be implemented by inherited algorithms. -
sync(): Input the result of running the lateral controller. Only the longitudinal controller has this function.- steer angle convergence
- allow keeping stopped until steer is converged.
- steer angle convergence
See the Design of Trajectory Follower Nodes for how these functions work in the node.
Separated lateral (steering) and longitudinal (velocity) controls
This longitudinal controller assumes that the roles of lateral and longitudinal control are separated as follows.
- Lateral control computes a target steering to keep the vehicle on the trajectory, assuming perfect velocity tracking.
- Longitudinal control computes a target velocity/acceleration to keep the vehicle velocity on the trajectory speed, assuming perfect trajectory tracking.
Ideally, dealing with the lateral and longitudinal control as a single mixed problem can achieve high performance. In contrast, there are two reasons to provide velocity controller as a stand-alone function, described below.
Complex requirements for longitudinal motion
The longitudinal vehicle behavior that humans expect is difficult to express in a single logic. For example, the expected behavior just before stopping differs depending on whether the ego-position is ahead/behind of the stop line, or whether the current speed is higher/lower than the target speed to achieve a human-like movement.
In addition, some vehicles have difficulty measuring the ego-speed at extremely low speeds. In such cases, a configuration that can improve the functionality of the longitudinal control without affecting the lateral control is important.
There are many characteristics and needs that are unique to longitudinal control. Designing them separately from the lateral control keeps the modules less coupled and improves maintainability.
Nonlinear coupling of lateral and longitudinal motion
The lat-lon mixed control problem is very complex and uses nonlinear optimization to achieve high performance. Since it is difficult to guarantee the convergence of the nonlinear optimization, a simple control logic is also necessary for development.
Also, the benefits of simultaneous longitudinal and lateral control are small if the vehicle doesn’t move at high speed.
Related issues
Changelog for package autoware_trajectory_follower_base
0.53.0 (2026-09-29)
0.52.0 (2026-06-30)
0.51.0 (2026-05-01)
-
Merge remote-tracking branch 'origin/main' into tmp/bot/bump_version_base
-
feat(steer_offset_estimator): implement calibration logic (#12004)
- refactor(steer_offset_estimator): restructure node and estimator implementation
- Updated the CMakeLists.txt to reflect new library and executable structure.
- Removed outdated README and added a new detailed README.md for better documentation.
- Introduced a new node class for steer offset estimation and refactored the estimator logic.
- Added utility functions for pose and steering calculations.
- Implemented tests for the estimator and utility functions to ensure reliability.
- Updated parameters in the schema and configuration files for improved clarity and functionality.
- Removed deprecated files and images to streamline the package. This commit enhances the overall architecture and usability of the steer offset estimator package.
- refactor(steer_offset_estimator): update CMake configuration and remove deprecated files
- Bump CMake minimum version to 3.14 and adjust project structure in CMakeLists.txt.
- Refactor library and executable definitions for clarity and maintainability.
- Remove the main.cpp file as the node is now defined in a separate header and source file.
- Update parameter comments in the configuration file for better clarity.
- Remove the glog dependency from package.xml to streamline dependencies. This commit enhances the organization and readability of the steer offset estimator package.
- docs(steer_offset_estimator): enhance README formatting for mathematical equations
- Improved the formatting of mathematical equations in the README.md to enhance readability by adding line breaks.
- Removed the monitoring section to streamline the documentation. This update aims to provide clearer guidance on the steering offset estimation algorithm and its implementation details.
- docs(steer_offset_estimator): add debug info output section to README
- docs(steer_offset_estimator): improve formatting of algorithm steps in README
- feat(steer_offset_estimator): enhance estimator parameters and update calculations
- Added new parameters: measurement_noise, denominator_floor, and covariance_floor to improve estimation stability.
- Refactored the update logic to incorporate Kalman gain and residual calculations, enhancing the accuracy of the steering offset estimation.
- Updated debug output to reflect new calculation metrics, including kalman_gain and residual. This commit improves the robustness and performance of the steer offset estimator by refining its parameterization and calculation methods.
- feat(steer_offset_estimator): add new parameters for enhanced estimation
- Introduced measurement_noise, denominator_floor, and covariance_floor parameters to the SteerOffsetEstimatorParameters structure.
- Updated the parameter loading function to accommodate the new parameters, improving the configurability of the estimator. This change aims to enhance the performance and stability of the steering offset estimation process by allowing for more precise parameter tuning.
- fix(steer_offset_estimator): update debug output to use standard deviation
- Modified the debug output format in the SteerOffsetEstimatorNode to replace covariance with standard deviation for clarity.
- This change enhances the readability of the debug information by providing a more intuitive metric for uncertainty.
- refactor(steer_offset_estimator): rename and restructure noise parameters for clarity
- Renamed measurement_noise to measurement_noise_covariance and added process_noise_covariance to the SteerOffsetEstimatorParameters structure for better clarity.
- Updated the parameter loading function to reflect these changes, enhancing the configurability of the estimator.
- Refactored the update logic to utilize the new covariance
File truncated at 100 lines see the full file
Package Dependencies
System Dependencies
| Name |
|---|
| eigen |
Dependant Packages
Launch files
Messages
Services
Plugins
Recent questions tagged autoware_trajectory_follower_base at Robotics Stack Exchange
Package Summary
| Version | 0.53.0 |
| License | Apache 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-10-23 |
| Dev Status | UNKNOWN |
| Released | UNRELEASED |
| Contributing |
Help Wanted (-)
Good First Issues (-) Pull Requests to Review (-) |
Package Description
Maintainers
- Maxime CLEMENT
- Alqudah Mohammad
- Zulfaqar Azmi
- Takumi Odashima
Authors
- Takamasa Horibe
- Takayuki Murooka
Trajectory Follower
This is the design document for the trajectory_follower package.
Purpose / Use cases
This package provides the interface of longitudinal and lateral controllers used by the node of the autoware_trajectory_follower_node package.
We can implement a detailed controller by deriving the longitudinal and lateral base interfaces.
Design
There are lateral and longitudinal base interface classes and each algorithm inherits from this class to implement. The interface class has the following base functions.
-
isReady(): Check if the control is ready to compute. -
run(): Compute control commands and return to Trajectory Follower Nodes. This must be implemented by inherited algorithms. -
sync(): Input the result of running the lateral controller. Only the longitudinal controller has this function.- steer angle convergence
- allow keeping stopped until steer is converged.
- steer angle convergence
See the Design of Trajectory Follower Nodes for how these functions work in the node.
Separated lateral (steering) and longitudinal (velocity) controls
This longitudinal controller assumes that the roles of lateral and longitudinal control are separated as follows.
- Lateral control computes a target steering to keep the vehicle on the trajectory, assuming perfect velocity tracking.
- Longitudinal control computes a target velocity/acceleration to keep the vehicle velocity on the trajectory speed, assuming perfect trajectory tracking.
Ideally, dealing with the lateral and longitudinal control as a single mixed problem can achieve high performance. In contrast, there are two reasons to provide velocity controller as a stand-alone function, described below.
Complex requirements for longitudinal motion
The longitudinal vehicle behavior that humans expect is difficult to express in a single logic. For example, the expected behavior just before stopping differs depending on whether the ego-position is ahead/behind of the stop line, or whether the current speed is higher/lower than the target speed to achieve a human-like movement.
In addition, some vehicles have difficulty measuring the ego-speed at extremely low speeds. In such cases, a configuration that can improve the functionality of the longitudinal control without affecting the lateral control is important.
There are many characteristics and needs that are unique to longitudinal control. Designing them separately from the lateral control keeps the modules less coupled and improves maintainability.
Nonlinear coupling of lateral and longitudinal motion
The lat-lon mixed control problem is very complex and uses nonlinear optimization to achieve high performance. Since it is difficult to guarantee the convergence of the nonlinear optimization, a simple control logic is also necessary for development.
Also, the benefits of simultaneous longitudinal and lateral control are small if the vehicle doesn’t move at high speed.
Related issues
Changelog for package autoware_trajectory_follower_base
0.53.0 (2026-09-29)
0.52.0 (2026-06-30)
0.51.0 (2026-05-01)
-
Merge remote-tracking branch 'origin/main' into tmp/bot/bump_version_base
-
feat(steer_offset_estimator): implement calibration logic (#12004)
- refactor(steer_offset_estimator): restructure node and estimator implementation
- Updated the CMakeLists.txt to reflect new library and executable structure.
- Removed outdated README and added a new detailed README.md for better documentation.
- Introduced a new node class for steer offset estimation and refactored the estimator logic.
- Added utility functions for pose and steering calculations.
- Implemented tests for the estimator and utility functions to ensure reliability.
- Updated parameters in the schema and configuration files for improved clarity and functionality.
- Removed deprecated files and images to streamline the package. This commit enhances the overall architecture and usability of the steer offset estimator package.
- refactor(steer_offset_estimator): update CMake configuration and remove deprecated files
- Bump CMake minimum version to 3.14 and adjust project structure in CMakeLists.txt.
- Refactor library and executable definitions for clarity and maintainability.
- Remove the main.cpp file as the node is now defined in a separate header and source file.
- Update parameter comments in the configuration file for better clarity.
- Remove the glog dependency from package.xml to streamline dependencies. This commit enhances the organization and readability of the steer offset estimator package.
- docs(steer_offset_estimator): enhance README formatting for mathematical equations
- Improved the formatting of mathematical equations in the README.md to enhance readability by adding line breaks.
- Removed the monitoring section to streamline the documentation. This update aims to provide clearer guidance on the steering offset estimation algorithm and its implementation details.
- docs(steer_offset_estimator): add debug info output section to README
- docs(steer_offset_estimator): improve formatting of algorithm steps in README
- feat(steer_offset_estimator): enhance estimator parameters and update calculations
- Added new parameters: measurement_noise, denominator_floor, and covariance_floor to improve estimation stability.
- Refactored the update logic to incorporate Kalman gain and residual calculations, enhancing the accuracy of the steering offset estimation.
- Updated debug output to reflect new calculation metrics, including kalman_gain and residual. This commit improves the robustness and performance of the steer offset estimator by refining its parameterization and calculation methods.
- feat(steer_offset_estimator): add new parameters for enhanced estimation
- Introduced measurement_noise, denominator_floor, and covariance_floor parameters to the SteerOffsetEstimatorParameters structure.
- Updated the parameter loading function to accommodate the new parameters, improving the configurability of the estimator. This change aims to enhance the performance and stability of the steering offset estimation process by allowing for more precise parameter tuning.
- fix(steer_offset_estimator): update debug output to use standard deviation
- Modified the debug output format in the SteerOffsetEstimatorNode to replace covariance with standard deviation for clarity.
- This change enhances the readability of the debug information by providing a more intuitive metric for uncertainty.
- refactor(steer_offset_estimator): rename and restructure noise parameters for clarity
- Renamed measurement_noise to measurement_noise_covariance and added process_noise_covariance to the SteerOffsetEstimatorParameters structure for better clarity.
- Updated the parameter loading function to reflect these changes, enhancing the configurability of the estimator.
- Refactored the update logic to utilize the new covariance
File truncated at 100 lines see the full file
Package Dependencies
System Dependencies
| Name |
|---|
| eigen |
Dependant Packages
Launch files
Messages
Services
Plugins
Recent questions tagged autoware_trajectory_follower_base at Robotics Stack Exchange
Package Summary
| Version | 0.53.0 |
| License | Apache 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-10-23 |
| Dev Status | UNKNOWN |
| Released | UNRELEASED |
| Contributing |
Help Wanted (-)
Good First Issues (-) Pull Requests to Review (-) |
Package Description
Maintainers
- Maxime CLEMENT
- Alqudah Mohammad
- Zulfaqar Azmi
- Takumi Odashima
Authors
- Takamasa Horibe
- Takayuki Murooka
Trajectory Follower
This is the design document for the trajectory_follower package.
Purpose / Use cases
This package provides the interface of longitudinal and lateral controllers used by the node of the autoware_trajectory_follower_node package.
We can implement a detailed controller by deriving the longitudinal and lateral base interfaces.
Design
There are lateral and longitudinal base interface classes and each algorithm inherits from this class to implement. The interface class has the following base functions.
-
isReady(): Check if the control is ready to compute. -
run(): Compute control commands and return to Trajectory Follower Nodes. This must be implemented by inherited algorithms. -
sync(): Input the result of running the lateral controller. Only the longitudinal controller has this function.- steer angle convergence
- allow keeping stopped until steer is converged.
- steer angle convergence
See the Design of Trajectory Follower Nodes for how these functions work in the node.
Separated lateral (steering) and longitudinal (velocity) controls
This longitudinal controller assumes that the roles of lateral and longitudinal control are separated as follows.
- Lateral control computes a target steering to keep the vehicle on the trajectory, assuming perfect velocity tracking.
- Longitudinal control computes a target velocity/acceleration to keep the vehicle velocity on the trajectory speed, assuming perfect trajectory tracking.
Ideally, dealing with the lateral and longitudinal control as a single mixed problem can achieve high performance. In contrast, there are two reasons to provide velocity controller as a stand-alone function, described below.
Complex requirements for longitudinal motion
The longitudinal vehicle behavior that humans expect is difficult to express in a single logic. For example, the expected behavior just before stopping differs depending on whether the ego-position is ahead/behind of the stop line, or whether the current speed is higher/lower than the target speed to achieve a human-like movement.
In addition, some vehicles have difficulty measuring the ego-speed at extremely low speeds. In such cases, a configuration that can improve the functionality of the longitudinal control without affecting the lateral control is important.
There are many characteristics and needs that are unique to longitudinal control. Designing them separately from the lateral control keeps the modules less coupled and improves maintainability.
Nonlinear coupling of lateral and longitudinal motion
The lat-lon mixed control problem is very complex and uses nonlinear optimization to achieve high performance. Since it is difficult to guarantee the convergence of the nonlinear optimization, a simple control logic is also necessary for development.
Also, the benefits of simultaneous longitudinal and lateral control are small if the vehicle doesn’t move at high speed.
Related issues
Changelog for package autoware_trajectory_follower_base
0.53.0 (2026-09-29)
0.52.0 (2026-06-30)
0.51.0 (2026-05-01)
-
Merge remote-tracking branch 'origin/main' into tmp/bot/bump_version_base
-
feat(steer_offset_estimator): implement calibration logic (#12004)
- refactor(steer_offset_estimator): restructure node and estimator implementation
- Updated the CMakeLists.txt to reflect new library and executable structure.
- Removed outdated README and added a new detailed README.md for better documentation.
- Introduced a new node class for steer offset estimation and refactored the estimator logic.
- Added utility functions for pose and steering calculations.
- Implemented tests for the estimator and utility functions to ensure reliability.
- Updated parameters in the schema and configuration files for improved clarity and functionality.
- Removed deprecated files and images to streamline the package. This commit enhances the overall architecture and usability of the steer offset estimator package.
- refactor(steer_offset_estimator): update CMake configuration and remove deprecated files
- Bump CMake minimum version to 3.14 and adjust project structure in CMakeLists.txt.
- Refactor library and executable definitions for clarity and maintainability.
- Remove the main.cpp file as the node is now defined in a separate header and source file.
- Update parameter comments in the configuration file for better clarity.
- Remove the glog dependency from package.xml to streamline dependencies. This commit enhances the organization and readability of the steer offset estimator package.
- docs(steer_offset_estimator): enhance README formatting for mathematical equations
- Improved the formatting of mathematical equations in the README.md to enhance readability by adding line breaks.
- Removed the monitoring section to streamline the documentation. This update aims to provide clearer guidance on the steering offset estimation algorithm and its implementation details.
- docs(steer_offset_estimator): add debug info output section to README
- docs(steer_offset_estimator): improve formatting of algorithm steps in README
- feat(steer_offset_estimator): enhance estimator parameters and update calculations
- Added new parameters: measurement_noise, denominator_floor, and covariance_floor to improve estimation stability.
- Refactored the update logic to incorporate Kalman gain and residual calculations, enhancing the accuracy of the steering offset estimation.
- Updated debug output to reflect new calculation metrics, including kalman_gain and residual. This commit improves the robustness and performance of the steer offset estimator by refining its parameterization and calculation methods.
- feat(steer_offset_estimator): add new parameters for enhanced estimation
- Introduced measurement_noise, denominator_floor, and covariance_floor parameters to the SteerOffsetEstimatorParameters structure.
- Updated the parameter loading function to accommodate the new parameters, improving the configurability of the estimator. This change aims to enhance the performance and stability of the steering offset estimation process by allowing for more precise parameter tuning.
- fix(steer_offset_estimator): update debug output to use standard deviation
- Modified the debug output format in the SteerOffsetEstimatorNode to replace covariance with standard deviation for clarity.
- This change enhances the readability of the debug information by providing a more intuitive metric for uncertainty.
- refactor(steer_offset_estimator): rename and restructure noise parameters for clarity
- Renamed measurement_noise to measurement_noise_covariance and added process_noise_covariance to the SteerOffsetEstimatorParameters structure for better clarity.
- Updated the parameter loading function to reflect these changes, enhancing the configurability of the estimator.
- Refactored the update logic to utilize the new covariance
File truncated at 100 lines see the full file
Package Dependencies
System Dependencies
| Name |
|---|
| eigen |