Package Summary
Tags | No category tags. |
Version | 0.47.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-08-16 |
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
- takayuki MUROOKA
- kosuke TAKEUCHI
- Temkei Kem
Authors
- Daniel SANCHEZ
- takayuki MUROOKA
Control Evaluator
Purpose
This package provides nodes that generate metrics to evaluate the quality of control.
It publishes metric information about control modules’ outputs as well as the ego vehicle’s current kinematics and position.
Evaluated metrics
The control evaluator uses the metrics defined in include/autoware/control_evaluator/metrics/metric.hpp
to calculate deviations in yaw and lateral distance from the ego’s set-point. The control_evaluator can also be customized to offer metrics/evaluation about other control modules. Currently, the control_evaluator offers a simple metric output based on the autonomous_emergency_braking node’s output, but this functionality can be extended to evaluate other control modules’ performance.
Kinematics output
The control evaluator module also constantly publishes information regarding the ego vehicle’s kinematics and position. It publishes the current ego lane id with the longitudinal s
and lateral t
arc coordinates. It also publishes the current ego speed, acceleration and jerk in its metric messages.
This information can be used by other nodes to establish automated evaluation using rosbags: by crosschecking the ego position and kinematics with the evaluated control module’s output, it is possible to judge if the evaluated control modules reacted in a satisfactory way at certain interesting points of the rosbag reproduction.
Changelog for package autoware_control_evaluator
0.47.0 (2025-08-11)
-
feat: change planning output topic name to /planning/trajectory (#11135)
- change planning output topic name to /planning/trajectory
* style(pre-commit): autofix ---------Co-authored-by: pre-commit-ci[bot] <66853113+pre-commit-ci[bot]@users.noreply.github.com>
-
feat(control_evaluator): add option to output_metrics only when ego is moving (#11125)
- add output_metrics_only_moving
- pre-commit
- use emplace_back
* fix build failures ---------
-
fix(control_evaluator): publish dist to uncrossable boundary (#11103) fix(control_evaluator): Publish dist to uncrossable boundary
-
style(pre-commit): update to clang-format-20 (#11088) Co-authored-by: pre-commit-ci[bot] <66853113+pre-commit-ci[bot]@users.noreply.github.com>
-
feat(control_evaluator): add steering_angle_abs metric (#10991) Co-authored-by: t4-adc <<grp-rd-1-adc-admin@tier4.jp>>
-
feat(control_evaluator): boundary departure check in control evaluator (#10859)
- feat(control_evaluator): add boundary departure check
- slight refactoring
- fix node dying due to invalid linestring reference
- docstring fix
- Revise metric's messages and move function call
* add comments to the extra margin ---------
-
Contributors: Kazunori-Nakajima, Kem (TiankuiXian), Mete Fatih Cırıt, Yukihiro Saito, Zulfaqar Azmi
0.46.0 (2025-06-20)
-
Merge remote-tracking branch 'upstream/main' into tmp/TaikiYamada/bump_version_base
-
feat(control_evaluator): change metrics to non-absolute and add absolute metrics (#10820) change metric name to _abs, and add no-abs metrics
-
feat(autoware_control_evaluator): add closest_object_distance metric (#10803)
- add closest_object_distance
- pre-commit
- add metric to list
- pre-commit
- fix TIER IV and autoware_utils_geometry
- add distance filter
- refactor code
* fix miss ---------
-
chore(control_evaluator): refactor control evaluator's logics. (#10741)
- fix conflict
* fix bug
-
fix(control_evaluator): add check route handler readiness (#10719) Co-authored-by: Jacek Namiota <<jnamiota@autonomous-systems.pl>>
-
Contributors: Kem (TiankuiXian), TaikiYamada4, namiota
0.45.0 (2025-05-22)
0.44.2 (2025-06-10)
0.44.1 (2025-05-01)
0.44.0 (2025-04-18)
-
Merge remote-tracking branch 'origin/main' into humble
-
fix(control_evaluator): fix bugs about output_metrics (#10433)
File truncated at 100 lines see the full file
Package Dependencies
System Dependencies
Name |
---|
nlohmann-json-dev |
Dependant Packages
Name | Deps |
---|---|
tier4_control_launch |
Launch files
- launch/control_evaluator.launch.xml
-
- output_metrics [default: false]
- input/odometry [default: /localization/kinematic_state]
- input/acceleration [default: /localization/acceleration]
- input/trajectory [default: /planning/trajectory]
- input/vector_map [default: /map/vector_map]
- input/route [default: /planning/mission_planning/route]
- input/behavior_path [default: /planning/scenario_planning/lane_driving/behavior_planning/path_with_lane_id]
- input/steering_status [default: /vehicle/status/steering_status]
- input/objects [default: /perception/object_recognition/objects]
Messages
Services
Plugins
Recent questions tagged autoware_control_evaluator at Robotics Stack Exchange
Package Summary
Tags | No category tags. |
Version | 0.47.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-08-16 |
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
- takayuki MUROOKA
- kosuke TAKEUCHI
- Temkei Kem
Authors
- Daniel SANCHEZ
- takayuki MUROOKA
Control Evaluator
Purpose
This package provides nodes that generate metrics to evaluate the quality of control.
It publishes metric information about control modules’ outputs as well as the ego vehicle’s current kinematics and position.
Evaluated metrics
The control evaluator uses the metrics defined in include/autoware/control_evaluator/metrics/metric.hpp
to calculate deviations in yaw and lateral distance from the ego’s set-point. The control_evaluator can also be customized to offer metrics/evaluation about other control modules. Currently, the control_evaluator offers a simple metric output based on the autonomous_emergency_braking node’s output, but this functionality can be extended to evaluate other control modules’ performance.
Kinematics output
The control evaluator module also constantly publishes information regarding the ego vehicle’s kinematics and position. It publishes the current ego lane id with the longitudinal s
and lateral t
arc coordinates. It also publishes the current ego speed, acceleration and jerk in its metric messages.
This information can be used by other nodes to establish automated evaluation using rosbags: by crosschecking the ego position and kinematics with the evaluated control module’s output, it is possible to judge if the evaluated control modules reacted in a satisfactory way at certain interesting points of the rosbag reproduction.
Changelog for package autoware_control_evaluator
0.47.0 (2025-08-11)
-
feat: change planning output topic name to /planning/trajectory (#11135)
- change planning output topic name to /planning/trajectory
* style(pre-commit): autofix ---------Co-authored-by: pre-commit-ci[bot] <66853113+pre-commit-ci[bot]@users.noreply.github.com>
-
feat(control_evaluator): add option to output_metrics only when ego is moving (#11125)
- add output_metrics_only_moving
- pre-commit
- use emplace_back
* fix build failures ---------
-
fix(control_evaluator): publish dist to uncrossable boundary (#11103) fix(control_evaluator): Publish dist to uncrossable boundary
-
style(pre-commit): update to clang-format-20 (#11088) Co-authored-by: pre-commit-ci[bot] <66853113+pre-commit-ci[bot]@users.noreply.github.com>
-
feat(control_evaluator): add steering_angle_abs metric (#10991) Co-authored-by: t4-adc <<grp-rd-1-adc-admin@tier4.jp>>
-
feat(control_evaluator): boundary departure check in control evaluator (#10859)
- feat(control_evaluator): add boundary departure check
- slight refactoring
- fix node dying due to invalid linestring reference
- docstring fix
- Revise metric's messages and move function call
* add comments to the extra margin ---------
-
Contributors: Kazunori-Nakajima, Kem (TiankuiXian), Mete Fatih Cırıt, Yukihiro Saito, Zulfaqar Azmi
0.46.0 (2025-06-20)
-
Merge remote-tracking branch 'upstream/main' into tmp/TaikiYamada/bump_version_base
-
feat(control_evaluator): change metrics to non-absolute and add absolute metrics (#10820) change metric name to _abs, and add no-abs metrics
-
feat(autoware_control_evaluator): add closest_object_distance metric (#10803)
- add closest_object_distance
- pre-commit
- add metric to list
- pre-commit
- fix TIER IV and autoware_utils_geometry
- add distance filter
- refactor code
* fix miss ---------
-
chore(control_evaluator): refactor control evaluator's logics. (#10741)
- fix conflict
* fix bug
-
fix(control_evaluator): add check route handler readiness (#10719) Co-authored-by: Jacek Namiota <<jnamiota@autonomous-systems.pl>>
-
Contributors: Kem (TiankuiXian), TaikiYamada4, namiota
0.45.0 (2025-05-22)
0.44.2 (2025-06-10)
0.44.1 (2025-05-01)
0.44.0 (2025-04-18)
-
Merge remote-tracking branch 'origin/main' into humble
-
fix(control_evaluator): fix bugs about output_metrics (#10433)
File truncated at 100 lines see the full file
Package Dependencies
System Dependencies
Name |
---|
nlohmann-json-dev |
Dependant Packages
Name | Deps |
---|---|
tier4_control_launch |
Launch files
- launch/control_evaluator.launch.xml
-
- output_metrics [default: false]
- input/odometry [default: /localization/kinematic_state]
- input/acceleration [default: /localization/acceleration]
- input/trajectory [default: /planning/trajectory]
- input/vector_map [default: /map/vector_map]
- input/route [default: /planning/mission_planning/route]
- input/behavior_path [default: /planning/scenario_planning/lane_driving/behavior_planning/path_with_lane_id]
- input/steering_status [default: /vehicle/status/steering_status]
- input/objects [default: /perception/object_recognition/objects]
Messages
Services
Plugins
Recent questions tagged autoware_control_evaluator at Robotics Stack Exchange
Package Summary
Tags | No category tags. |
Version | 0.47.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-08-16 |
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
- takayuki MUROOKA
- kosuke TAKEUCHI
- Temkei Kem
Authors
- Daniel SANCHEZ
- takayuki MUROOKA
Control Evaluator
Purpose
This package provides nodes that generate metrics to evaluate the quality of control.
It publishes metric information about control modules’ outputs as well as the ego vehicle’s current kinematics and position.
Evaluated metrics
The control evaluator uses the metrics defined in include/autoware/control_evaluator/metrics/metric.hpp
to calculate deviations in yaw and lateral distance from the ego’s set-point. The control_evaluator can also be customized to offer metrics/evaluation about other control modules. Currently, the control_evaluator offers a simple metric output based on the autonomous_emergency_braking node’s output, but this functionality can be extended to evaluate other control modules’ performance.
Kinematics output
The control evaluator module also constantly publishes information regarding the ego vehicle’s kinematics and position. It publishes the current ego lane id with the longitudinal s
and lateral t
arc coordinates. It also publishes the current ego speed, acceleration and jerk in its metric messages.
This information can be used by other nodes to establish automated evaluation using rosbags: by crosschecking the ego position and kinematics with the evaluated control module’s output, it is possible to judge if the evaluated control modules reacted in a satisfactory way at certain interesting points of the rosbag reproduction.
Changelog for package autoware_control_evaluator
0.47.0 (2025-08-11)
-
feat: change planning output topic name to /planning/trajectory (#11135)
- change planning output topic name to /planning/trajectory
* style(pre-commit): autofix ---------Co-authored-by: pre-commit-ci[bot] <66853113+pre-commit-ci[bot]@users.noreply.github.com>
-
feat(control_evaluator): add option to output_metrics only when ego is moving (#11125)
- add output_metrics_only_moving
- pre-commit
- use emplace_back
* fix build failures ---------
-
fix(control_evaluator): publish dist to uncrossable boundary (#11103) fix(control_evaluator): Publish dist to uncrossable boundary
-
style(pre-commit): update to clang-format-20 (#11088) Co-authored-by: pre-commit-ci[bot] <66853113+pre-commit-ci[bot]@users.noreply.github.com>
-
feat(control_evaluator): add steering_angle_abs metric (#10991) Co-authored-by: t4-adc <<grp-rd-1-adc-admin@tier4.jp>>
-
feat(control_evaluator): boundary departure check in control evaluator (#10859)
- feat(control_evaluator): add boundary departure check
- slight refactoring
- fix node dying due to invalid linestring reference
- docstring fix
- Revise metric's messages and move function call
* add comments to the extra margin ---------
-
Contributors: Kazunori-Nakajima, Kem (TiankuiXian), Mete Fatih Cırıt, Yukihiro Saito, Zulfaqar Azmi
0.46.0 (2025-06-20)
-
Merge remote-tracking branch 'upstream/main' into tmp/TaikiYamada/bump_version_base
-
feat(control_evaluator): change metrics to non-absolute and add absolute metrics (#10820) change metric name to _abs, and add no-abs metrics
-
feat(autoware_control_evaluator): add closest_object_distance metric (#10803)
- add closest_object_distance
- pre-commit
- add metric to list
- pre-commit
- fix TIER IV and autoware_utils_geometry
- add distance filter
- refactor code
* fix miss ---------
-
chore(control_evaluator): refactor control evaluator's logics. (#10741)
- fix conflict
* fix bug
-
fix(control_evaluator): add check route handler readiness (#10719) Co-authored-by: Jacek Namiota <<jnamiota@autonomous-systems.pl>>
-
Contributors: Kem (TiankuiXian), TaikiYamada4, namiota
0.45.0 (2025-05-22)
0.44.2 (2025-06-10)
0.44.1 (2025-05-01)
0.44.0 (2025-04-18)
-
Merge remote-tracking branch 'origin/main' into humble
-
fix(control_evaluator): fix bugs about output_metrics (#10433)
File truncated at 100 lines see the full file
Package Dependencies
System Dependencies
Name |
---|
nlohmann-json-dev |
Dependant Packages
Name | Deps |
---|---|
tier4_control_launch |
Launch files
- launch/control_evaluator.launch.xml
-
- output_metrics [default: false]
- input/odometry [default: /localization/kinematic_state]
- input/acceleration [default: /localization/acceleration]
- input/trajectory [default: /planning/trajectory]
- input/vector_map [default: /map/vector_map]
- input/route [default: /planning/mission_planning/route]
- input/behavior_path [default: /planning/scenario_planning/lane_driving/behavior_planning/path_with_lane_id]
- input/steering_status [default: /vehicle/status/steering_status]
- input/objects [default: /perception/object_recognition/objects]
Messages
Services
Plugins
Recent questions tagged autoware_control_evaluator at Robotics Stack Exchange
Package Summary
Tags | No category tags. |
Version | 0.47.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-08-16 |
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
- takayuki MUROOKA
- kosuke TAKEUCHI
- Temkei Kem
Authors
- Daniel SANCHEZ
- takayuki MUROOKA
Control Evaluator
Purpose
This package provides nodes that generate metrics to evaluate the quality of control.
It publishes metric information about control modules’ outputs as well as the ego vehicle’s current kinematics and position.
Evaluated metrics
The control evaluator uses the metrics defined in include/autoware/control_evaluator/metrics/metric.hpp
to calculate deviations in yaw and lateral distance from the ego’s set-point. The control_evaluator can also be customized to offer metrics/evaluation about other control modules. Currently, the control_evaluator offers a simple metric output based on the autonomous_emergency_braking node’s output, but this functionality can be extended to evaluate other control modules’ performance.
Kinematics output
The control evaluator module also constantly publishes information regarding the ego vehicle’s kinematics and position. It publishes the current ego lane id with the longitudinal s
and lateral t
arc coordinates. It also publishes the current ego speed, acceleration and jerk in its metric messages.
This information can be used by other nodes to establish automated evaluation using rosbags: by crosschecking the ego position and kinematics with the evaluated control module’s output, it is possible to judge if the evaluated control modules reacted in a satisfactory way at certain interesting points of the rosbag reproduction.
Changelog for package autoware_control_evaluator
0.47.0 (2025-08-11)
-
feat: change planning output topic name to /planning/trajectory (#11135)
- change planning output topic name to /planning/trajectory
* style(pre-commit): autofix ---------Co-authored-by: pre-commit-ci[bot] <66853113+pre-commit-ci[bot]@users.noreply.github.com>
-
feat(control_evaluator): add option to output_metrics only when ego is moving (#11125)
- add output_metrics_only_moving
- pre-commit
- use emplace_back
* fix build failures ---------
-
fix(control_evaluator): publish dist to uncrossable boundary (#11103) fix(control_evaluator): Publish dist to uncrossable boundary
-
style(pre-commit): update to clang-format-20 (#11088) Co-authored-by: pre-commit-ci[bot] <66853113+pre-commit-ci[bot]@users.noreply.github.com>
-
feat(control_evaluator): add steering_angle_abs metric (#10991) Co-authored-by: t4-adc <<grp-rd-1-adc-admin@tier4.jp>>
-
feat(control_evaluator): boundary departure check in control evaluator (#10859)
- feat(control_evaluator): add boundary departure check
- slight refactoring
- fix node dying due to invalid linestring reference
- docstring fix
- Revise metric's messages and move function call
* add comments to the extra margin ---------
-
Contributors: Kazunori-Nakajima, Kem (TiankuiXian), Mete Fatih Cırıt, Yukihiro Saito, Zulfaqar Azmi
0.46.0 (2025-06-20)
-
Merge remote-tracking branch 'upstream/main' into tmp/TaikiYamada/bump_version_base
-
feat(control_evaluator): change metrics to non-absolute and add absolute metrics (#10820) change metric name to _abs, and add no-abs metrics
-
feat(autoware_control_evaluator): add closest_object_distance metric (#10803)
- add closest_object_distance
- pre-commit
- add metric to list
- pre-commit
- fix TIER IV and autoware_utils_geometry
- add distance filter
- refactor code
* fix miss ---------
-
chore(control_evaluator): refactor control evaluator's logics. (#10741)
- fix conflict
* fix bug
-
fix(control_evaluator): add check route handler readiness (#10719) Co-authored-by: Jacek Namiota <<jnamiota@autonomous-systems.pl>>
-
Contributors: Kem (TiankuiXian), TaikiYamada4, namiota
0.45.0 (2025-05-22)
0.44.2 (2025-06-10)
0.44.1 (2025-05-01)
0.44.0 (2025-04-18)
-
Merge remote-tracking branch 'origin/main' into humble
-
fix(control_evaluator): fix bugs about output_metrics (#10433)
File truncated at 100 lines see the full file
Package Dependencies
System Dependencies
Name |
---|
nlohmann-json-dev |
Dependant Packages
Name | Deps |
---|---|
tier4_control_launch |
Launch files
- launch/control_evaluator.launch.xml
-
- output_metrics [default: false]
- input/odometry [default: /localization/kinematic_state]
- input/acceleration [default: /localization/acceleration]
- input/trajectory [default: /planning/trajectory]
- input/vector_map [default: /map/vector_map]
- input/route [default: /planning/mission_planning/route]
- input/behavior_path [default: /planning/scenario_planning/lane_driving/behavior_planning/path_with_lane_id]
- input/steering_status [default: /vehicle/status/steering_status]
- input/objects [default: /perception/object_recognition/objects]
Messages
Services
Plugins
Recent questions tagged autoware_control_evaluator at Robotics Stack Exchange
Package Summary
Tags | No category tags. |
Version | 0.47.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-08-16 |
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
- takayuki MUROOKA
- kosuke TAKEUCHI
- Temkei Kem
Authors
- Daniel SANCHEZ
- takayuki MUROOKA
Control Evaluator
Purpose
This package provides nodes that generate metrics to evaluate the quality of control.
It publishes metric information about control modules’ outputs as well as the ego vehicle’s current kinematics and position.
Evaluated metrics
The control evaluator uses the metrics defined in include/autoware/control_evaluator/metrics/metric.hpp
to calculate deviations in yaw and lateral distance from the ego’s set-point. The control_evaluator can also be customized to offer metrics/evaluation about other control modules. Currently, the control_evaluator offers a simple metric output based on the autonomous_emergency_braking node’s output, but this functionality can be extended to evaluate other control modules’ performance.
Kinematics output
The control evaluator module also constantly publishes information regarding the ego vehicle’s kinematics and position. It publishes the current ego lane id with the longitudinal s
and lateral t
arc coordinates. It also publishes the current ego speed, acceleration and jerk in its metric messages.
This information can be used by other nodes to establish automated evaluation using rosbags: by crosschecking the ego position and kinematics with the evaluated control module’s output, it is possible to judge if the evaluated control modules reacted in a satisfactory way at certain interesting points of the rosbag reproduction.
Changelog for package autoware_control_evaluator
0.47.0 (2025-08-11)
-
feat: change planning output topic name to /planning/trajectory (#11135)
- change planning output topic name to /planning/trajectory
* style(pre-commit): autofix ---------Co-authored-by: pre-commit-ci[bot] <66853113+pre-commit-ci[bot]@users.noreply.github.com>
-
feat(control_evaluator): add option to output_metrics only when ego is moving (#11125)
- add output_metrics_only_moving
- pre-commit
- use emplace_back
* fix build failures ---------
-
fix(control_evaluator): publish dist to uncrossable boundary (#11103) fix(control_evaluator): Publish dist to uncrossable boundary
-
style(pre-commit): update to clang-format-20 (#11088) Co-authored-by: pre-commit-ci[bot] <66853113+pre-commit-ci[bot]@users.noreply.github.com>
-
feat(control_evaluator): add steering_angle_abs metric (#10991) Co-authored-by: t4-adc <<grp-rd-1-adc-admin@tier4.jp>>
-
feat(control_evaluator): boundary departure check in control evaluator (#10859)
- feat(control_evaluator): add boundary departure check
- slight refactoring
- fix node dying due to invalid linestring reference
- docstring fix
- Revise metric's messages and move function call
* add comments to the extra margin ---------
-
Contributors: Kazunori-Nakajima, Kem (TiankuiXian), Mete Fatih Cırıt, Yukihiro Saito, Zulfaqar Azmi
0.46.0 (2025-06-20)
-
Merge remote-tracking branch 'upstream/main' into tmp/TaikiYamada/bump_version_base
-
feat(control_evaluator): change metrics to non-absolute and add absolute metrics (#10820) change metric name to _abs, and add no-abs metrics
-
feat(autoware_control_evaluator): add closest_object_distance metric (#10803)
- add closest_object_distance
- pre-commit
- add metric to list
- pre-commit
- fix TIER IV and autoware_utils_geometry
- add distance filter
- refactor code
* fix miss ---------
-
chore(control_evaluator): refactor control evaluator's logics. (#10741)
- fix conflict
* fix bug
-
fix(control_evaluator): add check route handler readiness (#10719) Co-authored-by: Jacek Namiota <<jnamiota@autonomous-systems.pl>>
-
Contributors: Kem (TiankuiXian), TaikiYamada4, namiota
0.45.0 (2025-05-22)
0.44.2 (2025-06-10)
0.44.1 (2025-05-01)
0.44.0 (2025-04-18)
-
Merge remote-tracking branch 'origin/main' into humble
-
fix(control_evaluator): fix bugs about output_metrics (#10433)
File truncated at 100 lines see the full file
Package Dependencies
System Dependencies
Name |
---|
nlohmann-json-dev |
Dependant Packages
Name | Deps |
---|---|
tier4_control_launch |
Launch files
- launch/control_evaluator.launch.xml
-
- output_metrics [default: false]
- input/odometry [default: /localization/kinematic_state]
- input/acceleration [default: /localization/acceleration]
- input/trajectory [default: /planning/trajectory]
- input/vector_map [default: /map/vector_map]
- input/route [default: /planning/mission_planning/route]
- input/behavior_path [default: /planning/scenario_planning/lane_driving/behavior_planning/path_with_lane_id]
- input/steering_status [default: /vehicle/status/steering_status]
- input/objects [default: /perception/object_recognition/objects]
Messages
Services
Plugins
Recent questions tagged autoware_control_evaluator at Robotics Stack Exchange
Package Summary
Tags | No category tags. |
Version | 0.47.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-08-16 |
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
- takayuki MUROOKA
- kosuke TAKEUCHI
- Temkei Kem
Authors
- Daniel SANCHEZ
- takayuki MUROOKA
Control Evaluator
Purpose
This package provides nodes that generate metrics to evaluate the quality of control.
It publishes metric information about control modules’ outputs as well as the ego vehicle’s current kinematics and position.
Evaluated metrics
The control evaluator uses the metrics defined in include/autoware/control_evaluator/metrics/metric.hpp
to calculate deviations in yaw and lateral distance from the ego’s set-point. The control_evaluator can also be customized to offer metrics/evaluation about other control modules. Currently, the control_evaluator offers a simple metric output based on the autonomous_emergency_braking node’s output, but this functionality can be extended to evaluate other control modules’ performance.
Kinematics output
The control evaluator module also constantly publishes information regarding the ego vehicle’s kinematics and position. It publishes the current ego lane id with the longitudinal s
and lateral t
arc coordinates. It also publishes the current ego speed, acceleration and jerk in its metric messages.
This information can be used by other nodes to establish automated evaluation using rosbags: by crosschecking the ego position and kinematics with the evaluated control module’s output, it is possible to judge if the evaluated control modules reacted in a satisfactory way at certain interesting points of the rosbag reproduction.
Changelog for package autoware_control_evaluator
0.47.0 (2025-08-11)
-
feat: change planning output topic name to /planning/trajectory (#11135)
- change planning output topic name to /planning/trajectory
* style(pre-commit): autofix ---------Co-authored-by: pre-commit-ci[bot] <66853113+pre-commit-ci[bot]@users.noreply.github.com>
-
feat(control_evaluator): add option to output_metrics only when ego is moving (#11125)
- add output_metrics_only_moving
- pre-commit
- use emplace_back
* fix build failures ---------
-
fix(control_evaluator): publish dist to uncrossable boundary (#11103) fix(control_evaluator): Publish dist to uncrossable boundary
-
style(pre-commit): update to clang-format-20 (#11088) Co-authored-by: pre-commit-ci[bot] <66853113+pre-commit-ci[bot]@users.noreply.github.com>
-
feat(control_evaluator): add steering_angle_abs metric (#10991) Co-authored-by: t4-adc <<grp-rd-1-adc-admin@tier4.jp>>
-
feat(control_evaluator): boundary departure check in control evaluator (#10859)
- feat(control_evaluator): add boundary departure check
- slight refactoring
- fix node dying due to invalid linestring reference
- docstring fix
- Revise metric's messages and move function call
* add comments to the extra margin ---------
-
Contributors: Kazunori-Nakajima, Kem (TiankuiXian), Mete Fatih Cırıt, Yukihiro Saito, Zulfaqar Azmi
0.46.0 (2025-06-20)
-
Merge remote-tracking branch 'upstream/main' into tmp/TaikiYamada/bump_version_base
-
feat(control_evaluator): change metrics to non-absolute and add absolute metrics (#10820) change metric name to _abs, and add no-abs metrics
-
feat(autoware_control_evaluator): add closest_object_distance metric (#10803)
- add closest_object_distance
- pre-commit
- add metric to list
- pre-commit
- fix TIER IV and autoware_utils_geometry
- add distance filter
- refactor code
* fix miss ---------
-
chore(control_evaluator): refactor control evaluator's logics. (#10741)
- fix conflict
* fix bug
-
fix(control_evaluator): add check route handler readiness (#10719) Co-authored-by: Jacek Namiota <<jnamiota@autonomous-systems.pl>>
-
Contributors: Kem (TiankuiXian), TaikiYamada4, namiota
0.45.0 (2025-05-22)
0.44.2 (2025-06-10)
0.44.1 (2025-05-01)
0.44.0 (2025-04-18)
-
Merge remote-tracking branch 'origin/main' into humble
-
fix(control_evaluator): fix bugs about output_metrics (#10433)
File truncated at 100 lines see the full file
Package Dependencies
System Dependencies
Name |
---|
nlohmann-json-dev |
Dependant Packages
Name | Deps |
---|---|
tier4_control_launch |
Launch files
- launch/control_evaluator.launch.xml
-
- output_metrics [default: false]
- input/odometry [default: /localization/kinematic_state]
- input/acceleration [default: /localization/acceleration]
- input/trajectory [default: /planning/trajectory]
- input/vector_map [default: /map/vector_map]
- input/route [default: /planning/mission_planning/route]
- input/behavior_path [default: /planning/scenario_planning/lane_driving/behavior_planning/path_with_lane_id]
- input/steering_status [default: /vehicle/status/steering_status]
- input/objects [default: /perception/object_recognition/objects]
Messages
Services
Plugins
Recent questions tagged autoware_control_evaluator at Robotics Stack Exchange
Package Summary
Tags | No category tags. |
Version | 0.47.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-08-16 |
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
- takayuki MUROOKA
- kosuke TAKEUCHI
- Temkei Kem
Authors
- Daniel SANCHEZ
- takayuki MUROOKA
Control Evaluator
Purpose
This package provides nodes that generate metrics to evaluate the quality of control.
It publishes metric information about control modules’ outputs as well as the ego vehicle’s current kinematics and position.
Evaluated metrics
The control evaluator uses the metrics defined in include/autoware/control_evaluator/metrics/metric.hpp
to calculate deviations in yaw and lateral distance from the ego’s set-point. The control_evaluator can also be customized to offer metrics/evaluation about other control modules. Currently, the control_evaluator offers a simple metric output based on the autonomous_emergency_braking node’s output, but this functionality can be extended to evaluate other control modules’ performance.
Kinematics output
The control evaluator module also constantly publishes information regarding the ego vehicle’s kinematics and position. It publishes the current ego lane id with the longitudinal s
and lateral t
arc coordinates. It also publishes the current ego speed, acceleration and jerk in its metric messages.
This information can be used by other nodes to establish automated evaluation using rosbags: by crosschecking the ego position and kinematics with the evaluated control module’s output, it is possible to judge if the evaluated control modules reacted in a satisfactory way at certain interesting points of the rosbag reproduction.
Changelog for package autoware_control_evaluator
0.47.0 (2025-08-11)
-
feat: change planning output topic name to /planning/trajectory (#11135)
- change planning output topic name to /planning/trajectory
* style(pre-commit): autofix ---------Co-authored-by: pre-commit-ci[bot] <66853113+pre-commit-ci[bot]@users.noreply.github.com>
-
feat(control_evaluator): add option to output_metrics only when ego is moving (#11125)
- add output_metrics_only_moving
- pre-commit
- use emplace_back
* fix build failures ---------
-
fix(control_evaluator): publish dist to uncrossable boundary (#11103) fix(control_evaluator): Publish dist to uncrossable boundary
-
style(pre-commit): update to clang-format-20 (#11088) Co-authored-by: pre-commit-ci[bot] <66853113+pre-commit-ci[bot]@users.noreply.github.com>
-
feat(control_evaluator): add steering_angle_abs metric (#10991) Co-authored-by: t4-adc <<grp-rd-1-adc-admin@tier4.jp>>
-
feat(control_evaluator): boundary departure check in control evaluator (#10859)
- feat(control_evaluator): add boundary departure check
- slight refactoring
- fix node dying due to invalid linestring reference
- docstring fix
- Revise metric's messages and move function call
* add comments to the extra margin ---------
-
Contributors: Kazunori-Nakajima, Kem (TiankuiXian), Mete Fatih Cırıt, Yukihiro Saito, Zulfaqar Azmi
0.46.0 (2025-06-20)
-
Merge remote-tracking branch 'upstream/main' into tmp/TaikiYamada/bump_version_base
-
feat(control_evaluator): change metrics to non-absolute and add absolute metrics (#10820) change metric name to _abs, and add no-abs metrics
-
feat(autoware_control_evaluator): add closest_object_distance metric (#10803)
- add closest_object_distance
- pre-commit
- add metric to list
- pre-commit
- fix TIER IV and autoware_utils_geometry
- add distance filter
- refactor code
* fix miss ---------
-
chore(control_evaluator): refactor control evaluator's logics. (#10741)
- fix conflict
* fix bug
-
fix(control_evaluator): add check route handler readiness (#10719) Co-authored-by: Jacek Namiota <<jnamiota@autonomous-systems.pl>>
-
Contributors: Kem (TiankuiXian), TaikiYamada4, namiota
0.45.0 (2025-05-22)
0.44.2 (2025-06-10)
0.44.1 (2025-05-01)
0.44.0 (2025-04-18)
-
Merge remote-tracking branch 'origin/main' into humble
-
fix(control_evaluator): fix bugs about output_metrics (#10433)
File truncated at 100 lines see the full file
Package Dependencies
System Dependencies
Name |
---|
nlohmann-json-dev |
Dependant Packages
Name | Deps |
---|---|
tier4_control_launch |
Launch files
- launch/control_evaluator.launch.xml
-
- output_metrics [default: false]
- input/odometry [default: /localization/kinematic_state]
- input/acceleration [default: /localization/acceleration]
- input/trajectory [default: /planning/trajectory]
- input/vector_map [default: /map/vector_map]
- input/route [default: /planning/mission_planning/route]
- input/behavior_path [default: /planning/scenario_planning/lane_driving/behavior_planning/path_with_lane_id]
- input/steering_status [default: /vehicle/status/steering_status]
- input/objects [default: /perception/object_recognition/objects]
Messages
Services
Plugins
Recent questions tagged autoware_control_evaluator at Robotics Stack Exchange
Package Summary
Tags | No category tags. |
Version | 0.47.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-08-16 |
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
- takayuki MUROOKA
- kosuke TAKEUCHI
- Temkei Kem
Authors
- Daniel SANCHEZ
- takayuki MUROOKA
Control Evaluator
Purpose
This package provides nodes that generate metrics to evaluate the quality of control.
It publishes metric information about control modules’ outputs as well as the ego vehicle’s current kinematics and position.
Evaluated metrics
The control evaluator uses the metrics defined in include/autoware/control_evaluator/metrics/metric.hpp
to calculate deviations in yaw and lateral distance from the ego’s set-point. The control_evaluator can also be customized to offer metrics/evaluation about other control modules. Currently, the control_evaluator offers a simple metric output based on the autonomous_emergency_braking node’s output, but this functionality can be extended to evaluate other control modules’ performance.
Kinematics output
The control evaluator module also constantly publishes information regarding the ego vehicle’s kinematics and position. It publishes the current ego lane id with the longitudinal s
and lateral t
arc coordinates. It also publishes the current ego speed, acceleration and jerk in its metric messages.
This information can be used by other nodes to establish automated evaluation using rosbags: by crosschecking the ego position and kinematics with the evaluated control module’s output, it is possible to judge if the evaluated control modules reacted in a satisfactory way at certain interesting points of the rosbag reproduction.
Changelog for package autoware_control_evaluator
0.47.0 (2025-08-11)
-
feat: change planning output topic name to /planning/trajectory (#11135)
- change planning output topic name to /planning/trajectory
* style(pre-commit): autofix ---------Co-authored-by: pre-commit-ci[bot] <66853113+pre-commit-ci[bot]@users.noreply.github.com>
-
feat(control_evaluator): add option to output_metrics only when ego is moving (#11125)
- add output_metrics_only_moving
- pre-commit
- use emplace_back
* fix build failures ---------
-
fix(control_evaluator): publish dist to uncrossable boundary (#11103) fix(control_evaluator): Publish dist to uncrossable boundary
-
style(pre-commit): update to clang-format-20 (#11088) Co-authored-by: pre-commit-ci[bot] <66853113+pre-commit-ci[bot]@users.noreply.github.com>
-
feat(control_evaluator): add steering_angle_abs metric (#10991) Co-authored-by: t4-adc <<grp-rd-1-adc-admin@tier4.jp>>
-
feat(control_evaluator): boundary departure check in control evaluator (#10859)
- feat(control_evaluator): add boundary departure check
- slight refactoring
- fix node dying due to invalid linestring reference
- docstring fix
- Revise metric's messages and move function call
* add comments to the extra margin ---------
-
Contributors: Kazunori-Nakajima, Kem (TiankuiXian), Mete Fatih Cırıt, Yukihiro Saito, Zulfaqar Azmi
0.46.0 (2025-06-20)
-
Merge remote-tracking branch 'upstream/main' into tmp/TaikiYamada/bump_version_base
-
feat(control_evaluator): change metrics to non-absolute and add absolute metrics (#10820) change metric name to _abs, and add no-abs metrics
-
feat(autoware_control_evaluator): add closest_object_distance metric (#10803)
- add closest_object_distance
- pre-commit
- add metric to list
- pre-commit
- fix TIER IV and autoware_utils_geometry
- add distance filter
- refactor code
* fix miss ---------
-
chore(control_evaluator): refactor control evaluator's logics. (#10741)
- fix conflict
* fix bug
-
fix(control_evaluator): add check route handler readiness (#10719) Co-authored-by: Jacek Namiota <<jnamiota@autonomous-systems.pl>>
-
Contributors: Kem (TiankuiXian), TaikiYamada4, namiota
0.45.0 (2025-05-22)
0.44.2 (2025-06-10)
0.44.1 (2025-05-01)
0.44.0 (2025-04-18)
-
Merge remote-tracking branch 'origin/main' into humble
-
fix(control_evaluator): fix bugs about output_metrics (#10433)
File truncated at 100 lines see the full file
Package Dependencies
System Dependencies
Name |
---|
nlohmann-json-dev |
Dependant Packages
Name | Deps |
---|---|
tier4_control_launch |
Launch files
- launch/control_evaluator.launch.xml
-
- output_metrics [default: false]
- input/odometry [default: /localization/kinematic_state]
- input/acceleration [default: /localization/acceleration]
- input/trajectory [default: /planning/trajectory]
- input/vector_map [default: /map/vector_map]
- input/route [default: /planning/mission_planning/route]
- input/behavior_path [default: /planning/scenario_planning/lane_driving/behavior_planning/path_with_lane_id]
- input/steering_status [default: /vehicle/status/steering_status]
- input/objects [default: /perception/object_recognition/objects]
Messages
Services
Plugins
Recent questions tagged autoware_control_evaluator at Robotics Stack Exchange
Package Summary
Tags | No category tags. |
Version | 0.47.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-08-16 |
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
- takayuki MUROOKA
- kosuke TAKEUCHI
- Temkei Kem
Authors
- Daniel SANCHEZ
- takayuki MUROOKA
Control Evaluator
Purpose
This package provides nodes that generate metrics to evaluate the quality of control.
It publishes metric information about control modules’ outputs as well as the ego vehicle’s current kinematics and position.
Evaluated metrics
The control evaluator uses the metrics defined in include/autoware/control_evaluator/metrics/metric.hpp
to calculate deviations in yaw and lateral distance from the ego’s set-point. The control_evaluator can also be customized to offer metrics/evaluation about other control modules. Currently, the control_evaluator offers a simple metric output based on the autonomous_emergency_braking node’s output, but this functionality can be extended to evaluate other control modules’ performance.
Kinematics output
The control evaluator module also constantly publishes information regarding the ego vehicle’s kinematics and position. It publishes the current ego lane id with the longitudinal s
and lateral t
arc coordinates. It also publishes the current ego speed, acceleration and jerk in its metric messages.
This information can be used by other nodes to establish automated evaluation using rosbags: by crosschecking the ego position and kinematics with the evaluated control module’s output, it is possible to judge if the evaluated control modules reacted in a satisfactory way at certain interesting points of the rosbag reproduction.
Changelog for package autoware_control_evaluator
0.47.0 (2025-08-11)
-
feat: change planning output topic name to /planning/trajectory (#11135)
- change planning output topic name to /planning/trajectory
* style(pre-commit): autofix ---------Co-authored-by: pre-commit-ci[bot] <66853113+pre-commit-ci[bot]@users.noreply.github.com>
-
feat(control_evaluator): add option to output_metrics only when ego is moving (#11125)
- add output_metrics_only_moving
- pre-commit
- use emplace_back
* fix build failures ---------
-
fix(control_evaluator): publish dist to uncrossable boundary (#11103) fix(control_evaluator): Publish dist to uncrossable boundary
-
style(pre-commit): update to clang-format-20 (#11088) Co-authored-by: pre-commit-ci[bot] <66853113+pre-commit-ci[bot]@users.noreply.github.com>
-
feat(control_evaluator): add steering_angle_abs metric (#10991) Co-authored-by: t4-adc <<grp-rd-1-adc-admin@tier4.jp>>
-
feat(control_evaluator): boundary departure check in control evaluator (#10859)
- feat(control_evaluator): add boundary departure check
- slight refactoring
- fix node dying due to invalid linestring reference
- docstring fix
- Revise metric's messages and move function call
* add comments to the extra margin ---------
-
Contributors: Kazunori-Nakajima, Kem (TiankuiXian), Mete Fatih Cırıt, Yukihiro Saito, Zulfaqar Azmi
0.46.0 (2025-06-20)
-
Merge remote-tracking branch 'upstream/main' into tmp/TaikiYamada/bump_version_base
-
feat(control_evaluator): change metrics to non-absolute and add absolute metrics (#10820) change metric name to _abs, and add no-abs metrics
-
feat(autoware_control_evaluator): add closest_object_distance metric (#10803)
- add closest_object_distance
- pre-commit
- add metric to list
- pre-commit
- fix TIER IV and autoware_utils_geometry
- add distance filter
- refactor code
* fix miss ---------
-
chore(control_evaluator): refactor control evaluator's logics. (#10741)
- fix conflict
* fix bug
-
fix(control_evaluator): add check route handler readiness (#10719) Co-authored-by: Jacek Namiota <<jnamiota@autonomous-systems.pl>>
-
Contributors: Kem (TiankuiXian), TaikiYamada4, namiota
0.45.0 (2025-05-22)
0.44.2 (2025-06-10)
0.44.1 (2025-05-01)
0.44.0 (2025-04-18)
-
Merge remote-tracking branch 'origin/main' into humble
-
fix(control_evaluator): fix bugs about output_metrics (#10433)
File truncated at 100 lines see the full file
Package Dependencies
System Dependencies
Name |
---|
nlohmann-json-dev |
Dependant Packages
Name | Deps |
---|---|
tier4_control_launch |
Launch files
- launch/control_evaluator.launch.xml
-
- output_metrics [default: false]
- input/odometry [default: /localization/kinematic_state]
- input/acceleration [default: /localization/acceleration]
- input/trajectory [default: /planning/trajectory]
- input/vector_map [default: /map/vector_map]
- input/route [default: /planning/mission_planning/route]
- input/behavior_path [default: /planning/scenario_planning/lane_driving/behavior_planning/path_with_lane_id]
- input/steering_status [default: /vehicle/status/steering_status]
- input/objects [default: /perception/object_recognition/objects]