Package symbol

autoware_vehicle_info_utils package from autoware_core repo

autoware_adapi_adaptors autoware_adapi_specs autoware_core_api autoware_default_adapi autoware_core autoware_agnocast_wrapper autoware_component_interface_specs autoware_geography_utils autoware_global_parameter_loader autoware_interpolation autoware_kalman_filter autoware_lanelet2_utils autoware_marker_utils autoware_motion_utils autoware_node autoware_object_recognition_utils autoware_osqp_interface autoware_point_types autoware_qos_utils autoware_qp_interface autoware_signal_processing autoware_trajectory autoware_vehicle_info_utils autoware_command_gate autoware_core_control autoware_simple_pure_pursuit autoware_awsim_sensor_kit_description autoware_sample_sensor_kit_description autoware_sample_vehicle_description autoware_core_localization autoware_ekf_localizer autoware_gyro_odometer autoware_localization_util autoware_ndt_scan_matcher autoware_pose_initializer autoware_stop_filter autoware_twist2accel autoware_core_map autoware_lanelet2_map_visualizer autoware_map_height_fitter autoware_map_loader autoware_map_projection_loader autoware_core_perception autoware_euclidean_cluster_object_detector autoware_ground_filter autoware_perception_objects_converter autoware_core_planning autoware_mission_planner autoware_objects_of_interest_marker_interface autoware_path_generator autoware_planning_factor_interface autoware_planning_topic_converter autoware_route_handler autoware_velocity_smoother autoware_behavior_velocity_planner autoware_behavior_velocity_planner_common autoware_behavior_velocity_stop_line_module autoware_motion_velocity_obstacle_stop_module autoware_motion_velocity_planner autoware_motion_velocity_planner_common autoware_core_sensing autoware_crop_box_filter autoware_downsample_filters autoware_gnss_poser autoware_vehicle_velocity_converter autoware_planning_test_manager autoware_pyplot autoware_test_node autoware_test_utils autoware_testing autoware_core_vehicle

ROS Distro
humble

Package Summary

Version 1.9.0
License Apache License 2.0
Build type AMENT_CMAKE
Use RECOMMENDED

Repository Summary

Checkout URI https://github.com/autowarefoundation/autoware_core.git
VCS Type git
VCS Version main
Last Updated 2026-07-03
Dev Status DEVELOPED
Released RELEASED
Contributing Help Wanted (-)
Good First Issues (-)
Pull Requests to Review (-)

Package Description

The autoware_vehicle_info_utils package

Maintainers

  • Taiki Tanaka
  • Tomoya Kimura
  • Shumpei Wakabayashi
  • Mamoru Sobue
  • Jian Kang

Authors

  • Yamato ANDO

Vehicle Info Util

Purpose

This package is to get vehicle info parameters.

Description

In here, you can check the vehicle dimensions with more detail. The current format supports only the Ackermann model. This file defines the model assumed in autoware path planning, control, etc. and does not represent the exact physical model. If a model other than the Ackermann model is used, it is assumed that a vehicle interface will be designed to change the control output for the model.

Versioning Policy

We have implemented a versioning system for the vehicle_info.param.yaml file to ensure clarity and consistency in file format across different versions of Autoware and its external applications. Please see discussion for the details.

How to Operate

  • The current file format is set as an unversioned base version (version: field is commented out).
  • For the next update involving changes (such as additions, deletions, or modifications):
    • Uncomment and update the version line at the beginning of the file.
    • Initiate versioning by assigning a version number, starting from 0.1.0. Follow the semantic versioning format (MAJOR.MINOR.PATCH).
    • Update this Readme.md too.
  • For subsequent updates, continue incrementing the version number in accordance with the changes made.
    • Discuss how to increment version depending on the amount of changes made to the file.
/**:
  ros__parameters:
    # version: 0.1.0 # Uncomment and update this line for future format changes.
    wheel_radius: 0.383
    ...

Why Versioning?

  • Consistency Across Updates: Implementing version control will allow accurate tracking of changes over time and changes in vehicle information parameters.
  • Clarity for External Applications: External applications that depend on vehicle_info.param.yaml need to reference the correct file version for optimal compatibility and functionality.
  • Simplified Management for Customized Branches: Assigning versions directly to the vehicle_info.param.yaml file simplifies management compared to maintaining separate versions for multiple customized Autoware branches. This approach streamlines version tracking and reduces complexity.

Scripts

Minimum turning radius

$ ros2 run autoware_vehicle_info_utils min_turning_radius_calculator.py
yaml path is /home/autoware/pilot-auto/install/autoware_vehicle_info_utils/share/autoware_vehicle_info_utils/config/vehicle_info.param.yaml
Minimum turning radius is 3.253042620027102 [m] for rear, 4.253220695862465 [m] for front.

You can designate yaml file with -y option as follows.

ros2 run autoware_vehicle_info_utils min_turning_radius_calculator.py -y <path-to-yaml>

Assumptions / Known limits

TBD.

CHANGELOG

Changelog for package autoware_vehicle_info_utils

1.1.0 (2025-05-01)

  • refactor(autoware_vehicle_info_utils): rewrite using modern C++ without API breakage (#343)
  • Contributors: Yutaka Kondo

1.9.0 (2026-06-24)

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

  • test(autoware_vehicle_info_utils): cover pure paths and reuse get_or_declare_parameter (#1105)

    * test(autoware_vehicle_info_utils): cover pure paths and reuse get_or_declare_parameter Add no-ROS unit tests for the pure VehicleInfo helpers that were previously untested: createVehicleInfo's wheel_base/max_steer clamping and has_non_positive_values branches, calcMaxMinDimension's two branches, extendVehicleInfo's margin distribution, the full 5-margin createFootprint overload (asymmetric margins plus center_at_base_link, asserting all seven ring points), and calcCurvatureFromSteerAngle's NaN guard. These run directly against the free functions / VehicleInfo methods without rclcpp. Replace the file-local getParameter<T> helper in VehicleInfoUtils with autoware_utils_rclcpp::get_or_declare_parameter<T>, which has identical has_parameter/get/declare semantics, and add the autoware_utils_rclcpp dependency. The throwing behavior on a parameter type mismatch is preserved (declare_parameter still throws); only the redundant local RCLCPP_ERROR log line on that path is dropped. No public API change. Refs: autowarefoundation/autoware_core#1096

    * test(autoware_vehicle_info_utils): de-tautologize vehicle_info test oracles (#79) Replace expected values that mirrored the implementation's formula or were read back from the output fields under test with independently hand-computed concrete literals (or stdlib-only computations in the std::hypot style). This makes the assertions verify the calculation instead of re-deriving the same potentially-wrong value. Refs: autowarefoundation/autoware_core#1096

    * test(autoware_vehicle_info_utils): use independent oracles for derived-value asserts (#86) Replace test expected values that mirrored the implementation's own formulas with concrete, independently hand-computed literals so the assertions can no longer pass on a wrong production calculation.

    - extendVehicleInfo: assert hardcoded 4.4 / 2.4 / 1.2 instead of reconstructing 'length + margin' / 'base2back + margin / 2'.

    - calcMaxMinDimension branch guards: drop the ASSERTs that recomputed base2front from the output fields; the branch is fixed by the test-chosen inputs and documented in comments. std::hypot-style expected values (inputs picked by the test, stdlib as the only shared dependency) and the existing hardcoded literals are kept. No production code changed. Refs: autowarefoundation/autoware_core#1096 ---------

  • feat(vehicle_info_utils): adjust [VehicleInfo]{.title-ref} to cover [VehicleShape]{.title-ref} (#1083)

    • add function to help replacing VehicleShape

    * remove defaulted function ---------Co-authored-by: Junya Sasaki <<j2sasaki1990@gmail.com>>

  • feat(autoware_vehicle_info_utils): add base_pose to createFootprint (#1072)

  • Contributors: Sarun MUKDAPITAK, Yutaka Kondo, github-actions

1.8.0 (2026-05-01)

  • Merge remote-tracking branch 'origin/main' into tmp/bot/bump_version_base
  • refactor(autoware_core): add USE_SCOPED_HEADER_INSTALL_DIR to common and testing packages (#967) Co-authored-by: github-actions <<github-actions@github.com>> Co-authored-by: Junya Sasaki <<j2sasaki1990@gmail.com>>
  • Contributors: Vishal Chauhan, github-actions

1.7.0 (2026-02-14)

1.6.0 (2025-12-30)

  • Merge remote-tracking branch 'origin/main' into tmp/bot/bump_version_base
  • docs: fix broken links (#779)

File truncated at 100 lines see the full file

Launch files

No launch files found

Messages

No message files found.

Services

No service files found

Plugins

No plugins found.

Recent questions tagged autoware_vehicle_info_utils at Robotics Stack Exchange

Package symbol

autoware_vehicle_info_utils package from autoware_core repo

autoware_adapi_adaptors autoware_adapi_specs autoware_core_api autoware_default_adapi autoware_core autoware_agnocast_wrapper autoware_component_interface_specs autoware_geography_utils autoware_global_parameter_loader autoware_interpolation autoware_kalman_filter autoware_lanelet2_utils autoware_marker_utils autoware_motion_utils autoware_node autoware_object_recognition_utils autoware_osqp_interface autoware_point_types autoware_qos_utils autoware_qp_interface autoware_signal_processing autoware_trajectory autoware_vehicle_info_utils autoware_command_gate autoware_core_control autoware_simple_pure_pursuit autoware_awsim_sensor_kit_description autoware_sample_sensor_kit_description autoware_sample_vehicle_description autoware_core_localization autoware_ekf_localizer autoware_gyro_odometer autoware_localization_util autoware_ndt_scan_matcher autoware_pose_initializer autoware_stop_filter autoware_twist2accel autoware_core_map autoware_lanelet2_map_visualizer autoware_map_height_fitter autoware_map_loader autoware_map_projection_loader autoware_core_perception autoware_euclidean_cluster_object_detector autoware_ground_filter autoware_perception_objects_converter autoware_core_planning autoware_mission_planner autoware_objects_of_interest_marker_interface autoware_path_generator autoware_planning_factor_interface autoware_planning_topic_converter autoware_route_handler autoware_velocity_smoother autoware_behavior_velocity_planner autoware_behavior_velocity_planner_common autoware_behavior_velocity_stop_line_module autoware_motion_velocity_obstacle_stop_module autoware_motion_velocity_planner autoware_motion_velocity_planner_common autoware_core_sensing autoware_crop_box_filter autoware_downsample_filters autoware_gnss_poser autoware_vehicle_velocity_converter autoware_planning_test_manager autoware_pyplot autoware_test_node autoware_test_utils autoware_testing autoware_core_vehicle

ROS Distro
jazzy

Package Summary

Version 1.9.0
License Apache License 2.0
Build type AMENT_CMAKE
Use RECOMMENDED

Repository Summary

Checkout URI https://github.com/autowarefoundation/autoware_core.git
VCS Type git
VCS Version main
Last Updated 2026-07-03
Dev Status DEVELOPED
Released RELEASED
Contributing Help Wanted (-)
Good First Issues (-)
Pull Requests to Review (-)

Package Description

The autoware_vehicle_info_utils package

Maintainers

  • Taiki Tanaka
  • Tomoya Kimura
  • Shumpei Wakabayashi
  • Mamoru Sobue
  • Jian Kang

Authors

  • Yamato ANDO

Vehicle Info Util

Purpose

This package is to get vehicle info parameters.

Description

In here, you can check the vehicle dimensions with more detail. The current format supports only the Ackermann model. This file defines the model assumed in autoware path planning, control, etc. and does not represent the exact physical model. If a model other than the Ackermann model is used, it is assumed that a vehicle interface will be designed to change the control output for the model.

Versioning Policy

We have implemented a versioning system for the vehicle_info.param.yaml file to ensure clarity and consistency in file format across different versions of Autoware and its external applications. Please see discussion for the details.

How to Operate

  • The current file format is set as an unversioned base version (version: field is commented out).
  • For the next update involving changes (such as additions, deletions, or modifications):
    • Uncomment and update the version line at the beginning of the file.
    • Initiate versioning by assigning a version number, starting from 0.1.0. Follow the semantic versioning format (MAJOR.MINOR.PATCH).
    • Update this Readme.md too.
  • For subsequent updates, continue incrementing the version number in accordance with the changes made.
    • Discuss how to increment version depending on the amount of changes made to the file.
/**:
  ros__parameters:
    # version: 0.1.0 # Uncomment and update this line for future format changes.
    wheel_radius: 0.383
    ...

Why Versioning?

  • Consistency Across Updates: Implementing version control will allow accurate tracking of changes over time and changes in vehicle information parameters.
  • Clarity for External Applications: External applications that depend on vehicle_info.param.yaml need to reference the correct file version for optimal compatibility and functionality.
  • Simplified Management for Customized Branches: Assigning versions directly to the vehicle_info.param.yaml file simplifies management compared to maintaining separate versions for multiple customized Autoware branches. This approach streamlines version tracking and reduces complexity.

Scripts

Minimum turning radius

$ ros2 run autoware_vehicle_info_utils min_turning_radius_calculator.py
yaml path is /home/autoware/pilot-auto/install/autoware_vehicle_info_utils/share/autoware_vehicle_info_utils/config/vehicle_info.param.yaml
Minimum turning radius is 3.253042620027102 [m] for rear, 4.253220695862465 [m] for front.

You can designate yaml file with -y option as follows.

ros2 run autoware_vehicle_info_utils min_turning_radius_calculator.py -y <path-to-yaml>

Assumptions / Known limits

TBD.

CHANGELOG

Changelog for package autoware_vehicle_info_utils

1.1.0 (2025-05-01)

  • refactor(autoware_vehicle_info_utils): rewrite using modern C++ without API breakage (#343)
  • Contributors: Yutaka Kondo

1.9.0 (2026-06-24)

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

  • test(autoware_vehicle_info_utils): cover pure paths and reuse get_or_declare_parameter (#1105)

    * test(autoware_vehicle_info_utils): cover pure paths and reuse get_or_declare_parameter Add no-ROS unit tests for the pure VehicleInfo helpers that were previously untested: createVehicleInfo's wheel_base/max_steer clamping and has_non_positive_values branches, calcMaxMinDimension's two branches, extendVehicleInfo's margin distribution, the full 5-margin createFootprint overload (asymmetric margins plus center_at_base_link, asserting all seven ring points), and calcCurvatureFromSteerAngle's NaN guard. These run directly against the free functions / VehicleInfo methods without rclcpp. Replace the file-local getParameter<T> helper in VehicleInfoUtils with autoware_utils_rclcpp::get_or_declare_parameter<T>, which has identical has_parameter/get/declare semantics, and add the autoware_utils_rclcpp dependency. The throwing behavior on a parameter type mismatch is preserved (declare_parameter still throws); only the redundant local RCLCPP_ERROR log line on that path is dropped. No public API change. Refs: autowarefoundation/autoware_core#1096

    * test(autoware_vehicle_info_utils): de-tautologize vehicle_info test oracles (#79) Replace expected values that mirrored the implementation's formula or were read back from the output fields under test with independently hand-computed concrete literals (or stdlib-only computations in the std::hypot style). This makes the assertions verify the calculation instead of re-deriving the same potentially-wrong value. Refs: autowarefoundation/autoware_core#1096

    * test(autoware_vehicle_info_utils): use independent oracles for derived-value asserts (#86) Replace test expected values that mirrored the implementation's own formulas with concrete, independently hand-computed literals so the assertions can no longer pass on a wrong production calculation.

    - extendVehicleInfo: assert hardcoded 4.4 / 2.4 / 1.2 instead of reconstructing 'length + margin' / 'base2back + margin / 2'.

    - calcMaxMinDimension branch guards: drop the ASSERTs that recomputed base2front from the output fields; the branch is fixed by the test-chosen inputs and documented in comments. std::hypot-style expected values (inputs picked by the test, stdlib as the only shared dependency) and the existing hardcoded literals are kept. No production code changed. Refs: autowarefoundation/autoware_core#1096 ---------

  • feat(vehicle_info_utils): adjust [VehicleInfo]{.title-ref} to cover [VehicleShape]{.title-ref} (#1083)

    • add function to help replacing VehicleShape

    * remove defaulted function ---------Co-authored-by: Junya Sasaki <<j2sasaki1990@gmail.com>>

  • feat(autoware_vehicle_info_utils): add base_pose to createFootprint (#1072)

  • Contributors: Sarun MUKDAPITAK, Yutaka Kondo, github-actions

1.8.0 (2026-05-01)

  • Merge remote-tracking branch 'origin/main' into tmp/bot/bump_version_base
  • refactor(autoware_core): add USE_SCOPED_HEADER_INSTALL_DIR to common and testing packages (#967) Co-authored-by: github-actions <<github-actions@github.com>> Co-authored-by: Junya Sasaki <<j2sasaki1990@gmail.com>>
  • Contributors: Vishal Chauhan, github-actions

1.7.0 (2026-02-14)

1.6.0 (2025-12-30)

  • Merge remote-tracking branch 'origin/main' into tmp/bot/bump_version_base
  • docs: fix broken links (#779)

File truncated at 100 lines see the full file

Launch files

No launch files found

Messages

No message files found.

Services

No service files found

Plugins

No plugins found.

Recent questions tagged autoware_vehicle_info_utils at Robotics Stack Exchange

No version for distro kilted showing humble. Known supported distros are highlighted in the buttons above.
Package symbol

autoware_vehicle_info_utils package from autoware_core repo

autoware_adapi_adaptors autoware_adapi_specs autoware_core_api autoware_default_adapi autoware_core autoware_agnocast_wrapper autoware_component_interface_specs autoware_geography_utils autoware_global_parameter_loader autoware_interpolation autoware_kalman_filter autoware_lanelet2_utils autoware_marker_utils autoware_motion_utils autoware_node autoware_object_recognition_utils autoware_osqp_interface autoware_point_types autoware_qos_utils autoware_qp_interface autoware_signal_processing autoware_trajectory autoware_vehicle_info_utils autoware_command_gate autoware_core_control autoware_simple_pure_pursuit autoware_awsim_sensor_kit_description autoware_sample_sensor_kit_description autoware_sample_vehicle_description autoware_core_localization autoware_ekf_localizer autoware_gyro_odometer autoware_localization_util autoware_ndt_scan_matcher autoware_pose_initializer autoware_stop_filter autoware_twist2accel autoware_core_map autoware_lanelet2_map_visualizer autoware_map_height_fitter autoware_map_loader autoware_map_projection_loader autoware_core_perception autoware_euclidean_cluster_object_detector autoware_ground_filter autoware_perception_objects_converter autoware_core_planning autoware_mission_planner autoware_objects_of_interest_marker_interface autoware_path_generator autoware_planning_factor_interface autoware_planning_topic_converter autoware_route_handler autoware_velocity_smoother autoware_behavior_velocity_planner autoware_behavior_velocity_planner_common autoware_behavior_velocity_stop_line_module autoware_motion_velocity_obstacle_stop_module autoware_motion_velocity_planner autoware_motion_velocity_planner_common autoware_core_sensing autoware_crop_box_filter autoware_downsample_filters autoware_gnss_poser autoware_vehicle_velocity_converter autoware_planning_test_manager autoware_pyplot autoware_test_node autoware_test_utils autoware_testing autoware_core_vehicle

ROS Distro
humble

Package Summary

Version 1.9.0
License Apache License 2.0
Build type AMENT_CMAKE
Use RECOMMENDED

Repository Summary

Checkout URI https://github.com/autowarefoundation/autoware_core.git
VCS Type git
VCS Version main
Last Updated 2026-07-03
Dev Status DEVELOPED
Released RELEASED
Contributing Help Wanted (-)
Good First Issues (-)
Pull Requests to Review (-)

Package Description

The autoware_vehicle_info_utils package

Maintainers

  • Taiki Tanaka
  • Tomoya Kimura
  • Shumpei Wakabayashi
  • Mamoru Sobue
  • Jian Kang

Authors

  • Yamato ANDO

Vehicle Info Util

Purpose

This package is to get vehicle info parameters.

Description

In here, you can check the vehicle dimensions with more detail. The current format supports only the Ackermann model. This file defines the model assumed in autoware path planning, control, etc. and does not represent the exact physical model. If a model other than the Ackermann model is used, it is assumed that a vehicle interface will be designed to change the control output for the model.

Versioning Policy

We have implemented a versioning system for the vehicle_info.param.yaml file to ensure clarity and consistency in file format across different versions of Autoware and its external applications. Please see discussion for the details.

How to Operate

  • The current file format is set as an unversioned base version (version: field is commented out).
  • For the next update involving changes (such as additions, deletions, or modifications):
    • Uncomment and update the version line at the beginning of the file.
    • Initiate versioning by assigning a version number, starting from 0.1.0. Follow the semantic versioning format (MAJOR.MINOR.PATCH).
    • Update this Readme.md too.
  • For subsequent updates, continue incrementing the version number in accordance with the changes made.
    • Discuss how to increment version depending on the amount of changes made to the file.
/**:
  ros__parameters:
    # version: 0.1.0 # Uncomment and update this line for future format changes.
    wheel_radius: 0.383
    ...

Why Versioning?

  • Consistency Across Updates: Implementing version control will allow accurate tracking of changes over time and changes in vehicle information parameters.
  • Clarity for External Applications: External applications that depend on vehicle_info.param.yaml need to reference the correct file version for optimal compatibility and functionality.
  • Simplified Management for Customized Branches: Assigning versions directly to the vehicle_info.param.yaml file simplifies management compared to maintaining separate versions for multiple customized Autoware branches. This approach streamlines version tracking and reduces complexity.

Scripts

Minimum turning radius

$ ros2 run autoware_vehicle_info_utils min_turning_radius_calculator.py
yaml path is /home/autoware/pilot-auto/install/autoware_vehicle_info_utils/share/autoware_vehicle_info_utils/config/vehicle_info.param.yaml
Minimum turning radius is 3.253042620027102 [m] for rear, 4.253220695862465 [m] for front.

You can designate yaml file with -y option as follows.

ros2 run autoware_vehicle_info_utils min_turning_radius_calculator.py -y <path-to-yaml>

Assumptions / Known limits

TBD.

CHANGELOG

Changelog for package autoware_vehicle_info_utils

1.1.0 (2025-05-01)

  • refactor(autoware_vehicle_info_utils): rewrite using modern C++ without API breakage (#343)
  • Contributors: Yutaka Kondo

1.9.0 (2026-06-24)

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

  • test(autoware_vehicle_info_utils): cover pure paths and reuse get_or_declare_parameter (#1105)

    * test(autoware_vehicle_info_utils): cover pure paths and reuse get_or_declare_parameter Add no-ROS unit tests for the pure VehicleInfo helpers that were previously untested: createVehicleInfo's wheel_base/max_steer clamping and has_non_positive_values branches, calcMaxMinDimension's two branches, extendVehicleInfo's margin distribution, the full 5-margin createFootprint overload (asymmetric margins plus center_at_base_link, asserting all seven ring points), and calcCurvatureFromSteerAngle's NaN guard. These run directly against the free functions / VehicleInfo methods without rclcpp. Replace the file-local getParameter<T> helper in VehicleInfoUtils with autoware_utils_rclcpp::get_or_declare_parameter<T>, which has identical has_parameter/get/declare semantics, and add the autoware_utils_rclcpp dependency. The throwing behavior on a parameter type mismatch is preserved (declare_parameter still throws); only the redundant local RCLCPP_ERROR log line on that path is dropped. No public API change. Refs: autowarefoundation/autoware_core#1096

    * test(autoware_vehicle_info_utils): de-tautologize vehicle_info test oracles (#79) Replace expected values that mirrored the implementation's formula or were read back from the output fields under test with independently hand-computed concrete literals (or stdlib-only computations in the std::hypot style). This makes the assertions verify the calculation instead of re-deriving the same potentially-wrong value. Refs: autowarefoundation/autoware_core#1096

    * test(autoware_vehicle_info_utils): use independent oracles for derived-value asserts (#86) Replace test expected values that mirrored the implementation's own formulas with concrete, independently hand-computed literals so the assertions can no longer pass on a wrong production calculation.

    - extendVehicleInfo: assert hardcoded 4.4 / 2.4 / 1.2 instead of reconstructing 'length + margin' / 'base2back + margin / 2'.

    - calcMaxMinDimension branch guards: drop the ASSERTs that recomputed base2front from the output fields; the branch is fixed by the test-chosen inputs and documented in comments. std::hypot-style expected values (inputs picked by the test, stdlib as the only shared dependency) and the existing hardcoded literals are kept. No production code changed. Refs: autowarefoundation/autoware_core#1096 ---------

  • feat(vehicle_info_utils): adjust [VehicleInfo]{.title-ref} to cover [VehicleShape]{.title-ref} (#1083)

    • add function to help replacing VehicleShape

    * remove defaulted function ---------Co-authored-by: Junya Sasaki <<j2sasaki1990@gmail.com>>

  • feat(autoware_vehicle_info_utils): add base_pose to createFootprint (#1072)

  • Contributors: Sarun MUKDAPITAK, Yutaka Kondo, github-actions

1.8.0 (2026-05-01)

  • Merge remote-tracking branch 'origin/main' into tmp/bot/bump_version_base
  • refactor(autoware_core): add USE_SCOPED_HEADER_INSTALL_DIR to common and testing packages (#967) Co-authored-by: github-actions <<github-actions@github.com>> Co-authored-by: Junya Sasaki <<j2sasaki1990@gmail.com>>
  • Contributors: Vishal Chauhan, github-actions

1.7.0 (2026-02-14)

1.6.0 (2025-12-30)

  • Merge remote-tracking branch 'origin/main' into tmp/bot/bump_version_base
  • docs: fix broken links (#779)

File truncated at 100 lines see the full file

Launch files

No launch files found

Messages

No message files found.

Services

No service files found

Plugins

No plugins found.

Recent questions tagged autoware_vehicle_info_utils at Robotics Stack Exchange

No version for distro lyrical showing humble. Known supported distros are highlighted in the buttons above.
Package symbol

autoware_vehicle_info_utils package from autoware_core repo

autoware_adapi_adaptors autoware_adapi_specs autoware_core_api autoware_default_adapi autoware_core autoware_agnocast_wrapper autoware_component_interface_specs autoware_geography_utils autoware_global_parameter_loader autoware_interpolation autoware_kalman_filter autoware_lanelet2_utils autoware_marker_utils autoware_motion_utils autoware_node autoware_object_recognition_utils autoware_osqp_interface autoware_point_types autoware_qos_utils autoware_qp_interface autoware_signal_processing autoware_trajectory autoware_vehicle_info_utils autoware_command_gate autoware_core_control autoware_simple_pure_pursuit autoware_awsim_sensor_kit_description autoware_sample_sensor_kit_description autoware_sample_vehicle_description autoware_core_localization autoware_ekf_localizer autoware_gyro_odometer autoware_localization_util autoware_ndt_scan_matcher autoware_pose_initializer autoware_stop_filter autoware_twist2accel autoware_core_map autoware_lanelet2_map_visualizer autoware_map_height_fitter autoware_map_loader autoware_map_projection_loader autoware_core_perception autoware_euclidean_cluster_object_detector autoware_ground_filter autoware_perception_objects_converter autoware_core_planning autoware_mission_planner autoware_objects_of_interest_marker_interface autoware_path_generator autoware_planning_factor_interface autoware_planning_topic_converter autoware_route_handler autoware_velocity_smoother autoware_behavior_velocity_planner autoware_behavior_velocity_planner_common autoware_behavior_velocity_stop_line_module autoware_motion_velocity_obstacle_stop_module autoware_motion_velocity_planner autoware_motion_velocity_planner_common autoware_core_sensing autoware_crop_box_filter autoware_downsample_filters autoware_gnss_poser autoware_vehicle_velocity_converter autoware_planning_test_manager autoware_pyplot autoware_test_node autoware_test_utils autoware_testing autoware_core_vehicle

ROS Distro
humble

Package Summary

Version 1.9.0
License Apache License 2.0
Build type AMENT_CMAKE
Use RECOMMENDED

Repository Summary

Checkout URI https://github.com/autowarefoundation/autoware_core.git
VCS Type git
VCS Version main
Last Updated 2026-07-03
Dev Status DEVELOPED
Released RELEASED
Contributing Help Wanted (-)
Good First Issues (-)
Pull Requests to Review (-)

Package Description

The autoware_vehicle_info_utils package

Maintainers

  • Taiki Tanaka
  • Tomoya Kimura
  • Shumpei Wakabayashi
  • Mamoru Sobue
  • Jian Kang

Authors

  • Yamato ANDO

Vehicle Info Util

Purpose

This package is to get vehicle info parameters.

Description

In here, you can check the vehicle dimensions with more detail. The current format supports only the Ackermann model. This file defines the model assumed in autoware path planning, control, etc. and does not represent the exact physical model. If a model other than the Ackermann model is used, it is assumed that a vehicle interface will be designed to change the control output for the model.

Versioning Policy

We have implemented a versioning system for the vehicle_info.param.yaml file to ensure clarity and consistency in file format across different versions of Autoware and its external applications. Please see discussion for the details.

How to Operate

  • The current file format is set as an unversioned base version (version: field is commented out).
  • For the next update involving changes (such as additions, deletions, or modifications):
    • Uncomment and update the version line at the beginning of the file.
    • Initiate versioning by assigning a version number, starting from 0.1.0. Follow the semantic versioning format (MAJOR.MINOR.PATCH).
    • Update this Readme.md too.
  • For subsequent updates, continue incrementing the version number in accordance with the changes made.
    • Discuss how to increment version depending on the amount of changes made to the file.
/**:
  ros__parameters:
    # version: 0.1.0 # Uncomment and update this line for future format changes.
    wheel_radius: 0.383
    ...

Why Versioning?

  • Consistency Across Updates: Implementing version control will allow accurate tracking of changes over time and changes in vehicle information parameters.
  • Clarity for External Applications: External applications that depend on vehicle_info.param.yaml need to reference the correct file version for optimal compatibility and functionality.
  • Simplified Management for Customized Branches: Assigning versions directly to the vehicle_info.param.yaml file simplifies management compared to maintaining separate versions for multiple customized Autoware branches. This approach streamlines version tracking and reduces complexity.

Scripts

Minimum turning radius

$ ros2 run autoware_vehicle_info_utils min_turning_radius_calculator.py
yaml path is /home/autoware/pilot-auto/install/autoware_vehicle_info_utils/share/autoware_vehicle_info_utils/config/vehicle_info.param.yaml
Minimum turning radius is 3.253042620027102 [m] for rear, 4.253220695862465 [m] for front.

You can designate yaml file with -y option as follows.

ros2 run autoware_vehicle_info_utils min_turning_radius_calculator.py -y <path-to-yaml>

Assumptions / Known limits

TBD.

CHANGELOG

Changelog for package autoware_vehicle_info_utils

1.1.0 (2025-05-01)

  • refactor(autoware_vehicle_info_utils): rewrite using modern C++ without API breakage (#343)
  • Contributors: Yutaka Kondo

1.9.0 (2026-06-24)

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

  • test(autoware_vehicle_info_utils): cover pure paths and reuse get_or_declare_parameter (#1105)

    * test(autoware_vehicle_info_utils): cover pure paths and reuse get_or_declare_parameter Add no-ROS unit tests for the pure VehicleInfo helpers that were previously untested: createVehicleInfo's wheel_base/max_steer clamping and has_non_positive_values branches, calcMaxMinDimension's two branches, extendVehicleInfo's margin distribution, the full 5-margin createFootprint overload (asymmetric margins plus center_at_base_link, asserting all seven ring points), and calcCurvatureFromSteerAngle's NaN guard. These run directly against the free functions / VehicleInfo methods without rclcpp. Replace the file-local getParameter<T> helper in VehicleInfoUtils with autoware_utils_rclcpp::get_or_declare_parameter<T>, which has identical has_parameter/get/declare semantics, and add the autoware_utils_rclcpp dependency. The throwing behavior on a parameter type mismatch is preserved (declare_parameter still throws); only the redundant local RCLCPP_ERROR log line on that path is dropped. No public API change. Refs: autowarefoundation/autoware_core#1096

    * test(autoware_vehicle_info_utils): de-tautologize vehicle_info test oracles (#79) Replace expected values that mirrored the implementation's formula or were read back from the output fields under test with independently hand-computed concrete literals (or stdlib-only computations in the std::hypot style). This makes the assertions verify the calculation instead of re-deriving the same potentially-wrong value. Refs: autowarefoundation/autoware_core#1096

    * test(autoware_vehicle_info_utils): use independent oracles for derived-value asserts (#86) Replace test expected values that mirrored the implementation's own formulas with concrete, independently hand-computed literals so the assertions can no longer pass on a wrong production calculation.

    - extendVehicleInfo: assert hardcoded 4.4 / 2.4 / 1.2 instead of reconstructing 'length + margin' / 'base2back + margin / 2'.

    - calcMaxMinDimension branch guards: drop the ASSERTs that recomputed base2front from the output fields; the branch is fixed by the test-chosen inputs and documented in comments. std::hypot-style expected values (inputs picked by the test, stdlib as the only shared dependency) and the existing hardcoded literals are kept. No production code changed. Refs: autowarefoundation/autoware_core#1096 ---------

  • feat(vehicle_info_utils): adjust [VehicleInfo]{.title-ref} to cover [VehicleShape]{.title-ref} (#1083)

    • add function to help replacing VehicleShape

    * remove defaulted function ---------Co-authored-by: Junya Sasaki <<j2sasaki1990@gmail.com>>

  • feat(autoware_vehicle_info_utils): add base_pose to createFootprint (#1072)

  • Contributors: Sarun MUKDAPITAK, Yutaka Kondo, github-actions

1.8.0 (2026-05-01)

  • Merge remote-tracking branch 'origin/main' into tmp/bot/bump_version_base
  • refactor(autoware_core): add USE_SCOPED_HEADER_INSTALL_DIR to common and testing packages (#967) Co-authored-by: github-actions <<github-actions@github.com>> Co-authored-by: Junya Sasaki <<j2sasaki1990@gmail.com>>
  • Contributors: Vishal Chauhan, github-actions

1.7.0 (2026-02-14)

1.6.0 (2025-12-30)

  • Merge remote-tracking branch 'origin/main' into tmp/bot/bump_version_base
  • docs: fix broken links (#779)

File truncated at 100 lines see the full file

Launch files

No launch files found

Messages

No message files found.

Services

No service files found

Plugins

No plugins found.

Recent questions tagged autoware_vehicle_info_utils at Robotics Stack Exchange

No version for distro rolling showing humble. Known supported distros are highlighted in the buttons above.
Package symbol

autoware_vehicle_info_utils package from autoware_core repo

autoware_adapi_adaptors autoware_adapi_specs autoware_core_api autoware_default_adapi autoware_core autoware_agnocast_wrapper autoware_component_interface_specs autoware_geography_utils autoware_global_parameter_loader autoware_interpolation autoware_kalman_filter autoware_lanelet2_utils autoware_marker_utils autoware_motion_utils autoware_node autoware_object_recognition_utils autoware_osqp_interface autoware_point_types autoware_qos_utils autoware_qp_interface autoware_signal_processing autoware_trajectory autoware_vehicle_info_utils autoware_command_gate autoware_core_control autoware_simple_pure_pursuit autoware_awsim_sensor_kit_description autoware_sample_sensor_kit_description autoware_sample_vehicle_description autoware_core_localization autoware_ekf_localizer autoware_gyro_odometer autoware_localization_util autoware_ndt_scan_matcher autoware_pose_initializer autoware_stop_filter autoware_twist2accel autoware_core_map autoware_lanelet2_map_visualizer autoware_map_height_fitter autoware_map_loader autoware_map_projection_loader autoware_core_perception autoware_euclidean_cluster_object_detector autoware_ground_filter autoware_perception_objects_converter autoware_core_planning autoware_mission_planner autoware_objects_of_interest_marker_interface autoware_path_generator autoware_planning_factor_interface autoware_planning_topic_converter autoware_route_handler autoware_velocity_smoother autoware_behavior_velocity_planner autoware_behavior_velocity_planner_common autoware_behavior_velocity_stop_line_module autoware_motion_velocity_obstacle_stop_module autoware_motion_velocity_planner autoware_motion_velocity_planner_common autoware_core_sensing autoware_crop_box_filter autoware_downsample_filters autoware_gnss_poser autoware_vehicle_velocity_converter autoware_planning_test_manager autoware_pyplot autoware_test_node autoware_test_utils autoware_testing autoware_core_vehicle

ROS Distro
humble

Package Summary

Version 1.9.0
License Apache License 2.0
Build type AMENT_CMAKE
Use RECOMMENDED

Repository Summary

Checkout URI https://github.com/autowarefoundation/autoware_core.git
VCS Type git
VCS Version main
Last Updated 2026-07-03
Dev Status DEVELOPED
Released RELEASED
Contributing Help Wanted (-)
Good First Issues (-)
Pull Requests to Review (-)

Package Description

The autoware_vehicle_info_utils package

Maintainers

  • Taiki Tanaka
  • Tomoya Kimura
  • Shumpei Wakabayashi
  • Mamoru Sobue
  • Jian Kang

Authors

  • Yamato ANDO

Vehicle Info Util

Purpose

This package is to get vehicle info parameters.

Description

In here, you can check the vehicle dimensions with more detail. The current format supports only the Ackermann model. This file defines the model assumed in autoware path planning, control, etc. and does not represent the exact physical model. If a model other than the Ackermann model is used, it is assumed that a vehicle interface will be designed to change the control output for the model.

Versioning Policy

We have implemented a versioning system for the vehicle_info.param.yaml file to ensure clarity and consistency in file format across different versions of Autoware and its external applications. Please see discussion for the details.

How to Operate

  • The current file format is set as an unversioned base version (version: field is commented out).
  • For the next update involving changes (such as additions, deletions, or modifications):
    • Uncomment and update the version line at the beginning of the file.
    • Initiate versioning by assigning a version number, starting from 0.1.0. Follow the semantic versioning format (MAJOR.MINOR.PATCH).
    • Update this Readme.md too.
  • For subsequent updates, continue incrementing the version number in accordance with the changes made.
    • Discuss how to increment version depending on the amount of changes made to the file.
/**:
  ros__parameters:
    # version: 0.1.0 # Uncomment and update this line for future format changes.
    wheel_radius: 0.383
    ...

Why Versioning?

  • Consistency Across Updates: Implementing version control will allow accurate tracking of changes over time and changes in vehicle information parameters.
  • Clarity for External Applications: External applications that depend on vehicle_info.param.yaml need to reference the correct file version for optimal compatibility and functionality.
  • Simplified Management for Customized Branches: Assigning versions directly to the vehicle_info.param.yaml file simplifies management compared to maintaining separate versions for multiple customized Autoware branches. This approach streamlines version tracking and reduces complexity.

Scripts

Minimum turning radius

$ ros2 run autoware_vehicle_info_utils min_turning_radius_calculator.py
yaml path is /home/autoware/pilot-auto/install/autoware_vehicle_info_utils/share/autoware_vehicle_info_utils/config/vehicle_info.param.yaml
Minimum turning radius is 3.253042620027102 [m] for rear, 4.253220695862465 [m] for front.

You can designate yaml file with -y option as follows.

ros2 run autoware_vehicle_info_utils min_turning_radius_calculator.py -y <path-to-yaml>

Assumptions / Known limits

TBD.

CHANGELOG

Changelog for package autoware_vehicle_info_utils

1.1.0 (2025-05-01)

  • refactor(autoware_vehicle_info_utils): rewrite using modern C++ without API breakage (#343)
  • Contributors: Yutaka Kondo

1.9.0 (2026-06-24)

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

  • test(autoware_vehicle_info_utils): cover pure paths and reuse get_or_declare_parameter (#1105)

    * test(autoware_vehicle_info_utils): cover pure paths and reuse get_or_declare_parameter Add no-ROS unit tests for the pure VehicleInfo helpers that were previously untested: createVehicleInfo's wheel_base/max_steer clamping and has_non_positive_values branches, calcMaxMinDimension's two branches, extendVehicleInfo's margin distribution, the full 5-margin createFootprint overload (asymmetric margins plus center_at_base_link, asserting all seven ring points), and calcCurvatureFromSteerAngle's NaN guard. These run directly against the free functions / VehicleInfo methods without rclcpp. Replace the file-local getParameter<T> helper in VehicleInfoUtils with autoware_utils_rclcpp::get_or_declare_parameter<T>, which has identical has_parameter/get/declare semantics, and add the autoware_utils_rclcpp dependency. The throwing behavior on a parameter type mismatch is preserved (declare_parameter still throws); only the redundant local RCLCPP_ERROR log line on that path is dropped. No public API change. Refs: autowarefoundation/autoware_core#1096

    * test(autoware_vehicle_info_utils): de-tautologize vehicle_info test oracles (#79) Replace expected values that mirrored the implementation's formula or were read back from the output fields under test with independently hand-computed concrete literals (or stdlib-only computations in the std::hypot style). This makes the assertions verify the calculation instead of re-deriving the same potentially-wrong value. Refs: autowarefoundation/autoware_core#1096

    * test(autoware_vehicle_info_utils): use independent oracles for derived-value asserts (#86) Replace test expected values that mirrored the implementation's own formulas with concrete, independently hand-computed literals so the assertions can no longer pass on a wrong production calculation.

    - extendVehicleInfo: assert hardcoded 4.4 / 2.4 / 1.2 instead of reconstructing 'length + margin' / 'base2back + margin / 2'.

    - calcMaxMinDimension branch guards: drop the ASSERTs that recomputed base2front from the output fields; the branch is fixed by the test-chosen inputs and documented in comments. std::hypot-style expected values (inputs picked by the test, stdlib as the only shared dependency) and the existing hardcoded literals are kept. No production code changed. Refs: autowarefoundation/autoware_core#1096 ---------

  • feat(vehicle_info_utils): adjust [VehicleInfo]{.title-ref} to cover [VehicleShape]{.title-ref} (#1083)

    • add function to help replacing VehicleShape

    * remove defaulted function ---------Co-authored-by: Junya Sasaki <<j2sasaki1990@gmail.com>>

  • feat(autoware_vehicle_info_utils): add base_pose to createFootprint (#1072)

  • Contributors: Sarun MUKDAPITAK, Yutaka Kondo, github-actions

1.8.0 (2026-05-01)

  • Merge remote-tracking branch 'origin/main' into tmp/bot/bump_version_base
  • refactor(autoware_core): add USE_SCOPED_HEADER_INSTALL_DIR to common and testing packages (#967) Co-authored-by: github-actions <<github-actions@github.com>> Co-authored-by: Junya Sasaki <<j2sasaki1990@gmail.com>>
  • Contributors: Vishal Chauhan, github-actions

1.7.0 (2026-02-14)

1.6.0 (2025-12-30)

  • Merge remote-tracking branch 'origin/main' into tmp/bot/bump_version_base
  • docs: fix broken links (#779)

File truncated at 100 lines see the full file

Launch files

No launch files found

Messages

No message files found.

Services

No service files found

Plugins

No plugins found.

Recent questions tagged autoware_vehicle_info_utils at Robotics Stack Exchange

No version for distro ardent showing humble. Known supported distros are highlighted in the buttons above.
Package symbol

autoware_vehicle_info_utils package from autoware_core repo

autoware_adapi_adaptors autoware_adapi_specs autoware_core_api autoware_default_adapi autoware_core autoware_agnocast_wrapper autoware_component_interface_specs autoware_geography_utils autoware_global_parameter_loader autoware_interpolation autoware_kalman_filter autoware_lanelet2_utils autoware_marker_utils autoware_motion_utils autoware_node autoware_object_recognition_utils autoware_osqp_interface autoware_point_types autoware_qos_utils autoware_qp_interface autoware_signal_processing autoware_trajectory autoware_vehicle_info_utils autoware_command_gate autoware_core_control autoware_simple_pure_pursuit autoware_awsim_sensor_kit_description autoware_sample_sensor_kit_description autoware_sample_vehicle_description autoware_core_localization autoware_ekf_localizer autoware_gyro_odometer autoware_localization_util autoware_ndt_scan_matcher autoware_pose_initializer autoware_stop_filter autoware_twist2accel autoware_core_map autoware_lanelet2_map_visualizer autoware_map_height_fitter autoware_map_loader autoware_map_projection_loader autoware_core_perception autoware_euclidean_cluster_object_detector autoware_ground_filter autoware_perception_objects_converter autoware_core_planning autoware_mission_planner autoware_objects_of_interest_marker_interface autoware_path_generator autoware_planning_factor_interface autoware_planning_topic_converter autoware_route_handler autoware_velocity_smoother autoware_behavior_velocity_planner autoware_behavior_velocity_planner_common autoware_behavior_velocity_stop_line_module autoware_motion_velocity_obstacle_stop_module autoware_motion_velocity_planner autoware_motion_velocity_planner_common autoware_core_sensing autoware_crop_box_filter autoware_downsample_filters autoware_gnss_poser autoware_vehicle_velocity_converter autoware_planning_test_manager autoware_pyplot autoware_test_node autoware_test_utils autoware_testing autoware_core_vehicle

ROS Distro
humble

Package Summary

Version 1.9.0
License Apache License 2.0
Build type AMENT_CMAKE
Use RECOMMENDED

Repository Summary

Checkout URI https://github.com/autowarefoundation/autoware_core.git
VCS Type git
VCS Version main
Last Updated 2026-07-03
Dev Status DEVELOPED
Released RELEASED
Contributing Help Wanted (-)
Good First Issues (-)
Pull Requests to Review (-)

Package Description

The autoware_vehicle_info_utils package

Maintainers

  • Taiki Tanaka
  • Tomoya Kimura
  • Shumpei Wakabayashi
  • Mamoru Sobue
  • Jian Kang

Authors

  • Yamato ANDO

Vehicle Info Util

Purpose

This package is to get vehicle info parameters.

Description

In here, you can check the vehicle dimensions with more detail. The current format supports only the Ackermann model. This file defines the model assumed in autoware path planning, control, etc. and does not represent the exact physical model. If a model other than the Ackermann model is used, it is assumed that a vehicle interface will be designed to change the control output for the model.

Versioning Policy

We have implemented a versioning system for the vehicle_info.param.yaml file to ensure clarity and consistency in file format across different versions of Autoware and its external applications. Please see discussion for the details.

How to Operate

  • The current file format is set as an unversioned base version (version: field is commented out).
  • For the next update involving changes (such as additions, deletions, or modifications):
    • Uncomment and update the version line at the beginning of the file.
    • Initiate versioning by assigning a version number, starting from 0.1.0. Follow the semantic versioning format (MAJOR.MINOR.PATCH).
    • Update this Readme.md too.
  • For subsequent updates, continue incrementing the version number in accordance with the changes made.
    • Discuss how to increment version depending on the amount of changes made to the file.
/**:
  ros__parameters:
    # version: 0.1.0 # Uncomment and update this line for future format changes.
    wheel_radius: 0.383
    ...

Why Versioning?

  • Consistency Across Updates: Implementing version control will allow accurate tracking of changes over time and changes in vehicle information parameters.
  • Clarity for External Applications: External applications that depend on vehicle_info.param.yaml need to reference the correct file version for optimal compatibility and functionality.
  • Simplified Management for Customized Branches: Assigning versions directly to the vehicle_info.param.yaml file simplifies management compared to maintaining separate versions for multiple customized Autoware branches. This approach streamlines version tracking and reduces complexity.

Scripts

Minimum turning radius

$ ros2 run autoware_vehicle_info_utils min_turning_radius_calculator.py
yaml path is /home/autoware/pilot-auto/install/autoware_vehicle_info_utils/share/autoware_vehicle_info_utils/config/vehicle_info.param.yaml
Minimum turning radius is 3.253042620027102 [m] for rear, 4.253220695862465 [m] for front.

You can designate yaml file with -y option as follows.

ros2 run autoware_vehicle_info_utils min_turning_radius_calculator.py -y <path-to-yaml>

Assumptions / Known limits

TBD.

CHANGELOG

Changelog for package autoware_vehicle_info_utils

1.1.0 (2025-05-01)

  • refactor(autoware_vehicle_info_utils): rewrite using modern C++ without API breakage (#343)
  • Contributors: Yutaka Kondo

1.9.0 (2026-06-24)

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

  • test(autoware_vehicle_info_utils): cover pure paths and reuse get_or_declare_parameter (#1105)

    * test(autoware_vehicle_info_utils): cover pure paths and reuse get_or_declare_parameter Add no-ROS unit tests for the pure VehicleInfo helpers that were previously untested: createVehicleInfo's wheel_base/max_steer clamping and has_non_positive_values branches, calcMaxMinDimension's two branches, extendVehicleInfo's margin distribution, the full 5-margin createFootprint overload (asymmetric margins plus center_at_base_link, asserting all seven ring points), and calcCurvatureFromSteerAngle's NaN guard. These run directly against the free functions / VehicleInfo methods without rclcpp. Replace the file-local getParameter<T> helper in VehicleInfoUtils with autoware_utils_rclcpp::get_or_declare_parameter<T>, which has identical has_parameter/get/declare semantics, and add the autoware_utils_rclcpp dependency. The throwing behavior on a parameter type mismatch is preserved (declare_parameter still throws); only the redundant local RCLCPP_ERROR log line on that path is dropped. No public API change. Refs: autowarefoundation/autoware_core#1096

    * test(autoware_vehicle_info_utils): de-tautologize vehicle_info test oracles (#79) Replace expected values that mirrored the implementation's formula or were read back from the output fields under test with independently hand-computed concrete literals (or stdlib-only computations in the std::hypot style). This makes the assertions verify the calculation instead of re-deriving the same potentially-wrong value. Refs: autowarefoundation/autoware_core#1096

    * test(autoware_vehicle_info_utils): use independent oracles for derived-value asserts (#86) Replace test expected values that mirrored the implementation's own formulas with concrete, independently hand-computed literals so the assertions can no longer pass on a wrong production calculation.

    - extendVehicleInfo: assert hardcoded 4.4 / 2.4 / 1.2 instead of reconstructing 'length + margin' / 'base2back + margin / 2'.

    - calcMaxMinDimension branch guards: drop the ASSERTs that recomputed base2front from the output fields; the branch is fixed by the test-chosen inputs and documented in comments. std::hypot-style expected values (inputs picked by the test, stdlib as the only shared dependency) and the existing hardcoded literals are kept. No production code changed. Refs: autowarefoundation/autoware_core#1096 ---------

  • feat(vehicle_info_utils): adjust [VehicleInfo]{.title-ref} to cover [VehicleShape]{.title-ref} (#1083)

    • add function to help replacing VehicleShape

    * remove defaulted function ---------Co-authored-by: Junya Sasaki <<j2sasaki1990@gmail.com>>

  • feat(autoware_vehicle_info_utils): add base_pose to createFootprint (#1072)

  • Contributors: Sarun MUKDAPITAK, Yutaka Kondo, github-actions

1.8.0 (2026-05-01)

  • Merge remote-tracking branch 'origin/main' into tmp/bot/bump_version_base
  • refactor(autoware_core): add USE_SCOPED_HEADER_INSTALL_DIR to common and testing packages (#967) Co-authored-by: github-actions <<github-actions@github.com>> Co-authored-by: Junya Sasaki <<j2sasaki1990@gmail.com>>
  • Contributors: Vishal Chauhan, github-actions

1.7.0 (2026-02-14)

1.6.0 (2025-12-30)

  • Merge remote-tracking branch 'origin/main' into tmp/bot/bump_version_base
  • docs: fix broken links (#779)

File truncated at 100 lines see the full file

Launch files

No launch files found

Messages

No message files found.

Services

No service files found

Plugins

No plugins found.

Recent questions tagged autoware_vehicle_info_utils at Robotics Stack Exchange

No version for distro bouncy showing humble. Known supported distros are highlighted in the buttons above.
Package symbol

autoware_vehicle_info_utils package from autoware_core repo

autoware_adapi_adaptors autoware_adapi_specs autoware_core_api autoware_default_adapi autoware_core autoware_agnocast_wrapper autoware_component_interface_specs autoware_geography_utils autoware_global_parameter_loader autoware_interpolation autoware_kalman_filter autoware_lanelet2_utils autoware_marker_utils autoware_motion_utils autoware_node autoware_object_recognition_utils autoware_osqp_interface autoware_point_types autoware_qos_utils autoware_qp_interface autoware_signal_processing autoware_trajectory autoware_vehicle_info_utils autoware_command_gate autoware_core_control autoware_simple_pure_pursuit autoware_awsim_sensor_kit_description autoware_sample_sensor_kit_description autoware_sample_vehicle_description autoware_core_localization autoware_ekf_localizer autoware_gyro_odometer autoware_localization_util autoware_ndt_scan_matcher autoware_pose_initializer autoware_stop_filter autoware_twist2accel autoware_core_map autoware_lanelet2_map_visualizer autoware_map_height_fitter autoware_map_loader autoware_map_projection_loader autoware_core_perception autoware_euclidean_cluster_object_detector autoware_ground_filter autoware_perception_objects_converter autoware_core_planning autoware_mission_planner autoware_objects_of_interest_marker_interface autoware_path_generator autoware_planning_factor_interface autoware_planning_topic_converter autoware_route_handler autoware_velocity_smoother autoware_behavior_velocity_planner autoware_behavior_velocity_planner_common autoware_behavior_velocity_stop_line_module autoware_motion_velocity_obstacle_stop_module autoware_motion_velocity_planner autoware_motion_velocity_planner_common autoware_core_sensing autoware_crop_box_filter autoware_downsample_filters autoware_gnss_poser autoware_vehicle_velocity_converter autoware_planning_test_manager autoware_pyplot autoware_test_node autoware_test_utils autoware_testing autoware_core_vehicle

ROS Distro
humble

Package Summary

Version 1.9.0
License Apache License 2.0
Build type AMENT_CMAKE
Use RECOMMENDED

Repository Summary

Checkout URI https://github.com/autowarefoundation/autoware_core.git
VCS Type git
VCS Version main
Last Updated 2026-07-03
Dev Status DEVELOPED
Released RELEASED
Contributing Help Wanted (-)
Good First Issues (-)
Pull Requests to Review (-)

Package Description

The autoware_vehicle_info_utils package

Maintainers

  • Taiki Tanaka
  • Tomoya Kimura
  • Shumpei Wakabayashi
  • Mamoru Sobue
  • Jian Kang

Authors

  • Yamato ANDO

Vehicle Info Util

Purpose

This package is to get vehicle info parameters.

Description

In here, you can check the vehicle dimensions with more detail. The current format supports only the Ackermann model. This file defines the model assumed in autoware path planning, control, etc. and does not represent the exact physical model. If a model other than the Ackermann model is used, it is assumed that a vehicle interface will be designed to change the control output for the model.

Versioning Policy

We have implemented a versioning system for the vehicle_info.param.yaml file to ensure clarity and consistency in file format across different versions of Autoware and its external applications. Please see discussion for the details.

How to Operate

  • The current file format is set as an unversioned base version (version: field is commented out).
  • For the next update involving changes (such as additions, deletions, or modifications):
    • Uncomment and update the version line at the beginning of the file.
    • Initiate versioning by assigning a version number, starting from 0.1.0. Follow the semantic versioning format (MAJOR.MINOR.PATCH).
    • Update this Readme.md too.
  • For subsequent updates, continue incrementing the version number in accordance with the changes made.
    • Discuss how to increment version depending on the amount of changes made to the file.
/**:
  ros__parameters:
    # version: 0.1.0 # Uncomment and update this line for future format changes.
    wheel_radius: 0.383
    ...

Why Versioning?

  • Consistency Across Updates: Implementing version control will allow accurate tracking of changes over time and changes in vehicle information parameters.
  • Clarity for External Applications: External applications that depend on vehicle_info.param.yaml need to reference the correct file version for optimal compatibility and functionality.
  • Simplified Management for Customized Branches: Assigning versions directly to the vehicle_info.param.yaml file simplifies management compared to maintaining separate versions for multiple customized Autoware branches. This approach streamlines version tracking and reduces complexity.

Scripts

Minimum turning radius

$ ros2 run autoware_vehicle_info_utils min_turning_radius_calculator.py
yaml path is /home/autoware/pilot-auto/install/autoware_vehicle_info_utils/share/autoware_vehicle_info_utils/config/vehicle_info.param.yaml
Minimum turning radius is 3.253042620027102 [m] for rear, 4.253220695862465 [m] for front.

You can designate yaml file with -y option as follows.

ros2 run autoware_vehicle_info_utils min_turning_radius_calculator.py -y <path-to-yaml>

Assumptions / Known limits

TBD.

CHANGELOG

Changelog for package autoware_vehicle_info_utils

1.1.0 (2025-05-01)

  • refactor(autoware_vehicle_info_utils): rewrite using modern C++ without API breakage (#343)
  • Contributors: Yutaka Kondo

1.9.0 (2026-06-24)

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

  • test(autoware_vehicle_info_utils): cover pure paths and reuse get_or_declare_parameter (#1105)

    * test(autoware_vehicle_info_utils): cover pure paths and reuse get_or_declare_parameter Add no-ROS unit tests for the pure VehicleInfo helpers that were previously untested: createVehicleInfo's wheel_base/max_steer clamping and has_non_positive_values branches, calcMaxMinDimension's two branches, extendVehicleInfo's margin distribution, the full 5-margin createFootprint overload (asymmetric margins plus center_at_base_link, asserting all seven ring points), and calcCurvatureFromSteerAngle's NaN guard. These run directly against the free functions / VehicleInfo methods without rclcpp. Replace the file-local getParameter<T> helper in VehicleInfoUtils with autoware_utils_rclcpp::get_or_declare_parameter<T>, which has identical has_parameter/get/declare semantics, and add the autoware_utils_rclcpp dependency. The throwing behavior on a parameter type mismatch is preserved (declare_parameter still throws); only the redundant local RCLCPP_ERROR log line on that path is dropped. No public API change. Refs: autowarefoundation/autoware_core#1096

    * test(autoware_vehicle_info_utils): de-tautologize vehicle_info test oracles (#79) Replace expected values that mirrored the implementation's formula or were read back from the output fields under test with independently hand-computed concrete literals (or stdlib-only computations in the std::hypot style). This makes the assertions verify the calculation instead of re-deriving the same potentially-wrong value. Refs: autowarefoundation/autoware_core#1096

    * test(autoware_vehicle_info_utils): use independent oracles for derived-value asserts (#86) Replace test expected values that mirrored the implementation's own formulas with concrete, independently hand-computed literals so the assertions can no longer pass on a wrong production calculation.

    - extendVehicleInfo: assert hardcoded 4.4 / 2.4 / 1.2 instead of reconstructing 'length + margin' / 'base2back + margin / 2'.

    - calcMaxMinDimension branch guards: drop the ASSERTs that recomputed base2front from the output fields; the branch is fixed by the test-chosen inputs and documented in comments. std::hypot-style expected values (inputs picked by the test, stdlib as the only shared dependency) and the existing hardcoded literals are kept. No production code changed. Refs: autowarefoundation/autoware_core#1096 ---------

  • feat(vehicle_info_utils): adjust [VehicleInfo]{.title-ref} to cover [VehicleShape]{.title-ref} (#1083)

    • add function to help replacing VehicleShape

    * remove defaulted function ---------Co-authored-by: Junya Sasaki <<j2sasaki1990@gmail.com>>

  • feat(autoware_vehicle_info_utils): add base_pose to createFootprint (#1072)

  • Contributors: Sarun MUKDAPITAK, Yutaka Kondo, github-actions

1.8.0 (2026-05-01)

  • Merge remote-tracking branch 'origin/main' into tmp/bot/bump_version_base
  • refactor(autoware_core): add USE_SCOPED_HEADER_INSTALL_DIR to common and testing packages (#967) Co-authored-by: github-actions <<github-actions@github.com>> Co-authored-by: Junya Sasaki <<j2sasaki1990@gmail.com>>
  • Contributors: Vishal Chauhan, github-actions

1.7.0 (2026-02-14)

1.6.0 (2025-12-30)

  • Merge remote-tracking branch 'origin/main' into tmp/bot/bump_version_base
  • docs: fix broken links (#779)

File truncated at 100 lines see the full file

Launch files

No launch files found

Messages

No message files found.

Services

No service files found

Plugins

No plugins found.

Recent questions tagged autoware_vehicle_info_utils at Robotics Stack Exchange

No version for distro crystal showing humble. Known supported distros are highlighted in the buttons above.
Package symbol

autoware_vehicle_info_utils package from autoware_core repo

autoware_adapi_adaptors autoware_adapi_specs autoware_core_api autoware_default_adapi autoware_core autoware_agnocast_wrapper autoware_component_interface_specs autoware_geography_utils autoware_global_parameter_loader autoware_interpolation autoware_kalman_filter autoware_lanelet2_utils autoware_marker_utils autoware_motion_utils autoware_node autoware_object_recognition_utils autoware_osqp_interface autoware_point_types autoware_qos_utils autoware_qp_interface autoware_signal_processing autoware_trajectory autoware_vehicle_info_utils autoware_command_gate autoware_core_control autoware_simple_pure_pursuit autoware_awsim_sensor_kit_description autoware_sample_sensor_kit_description autoware_sample_vehicle_description autoware_core_localization autoware_ekf_localizer autoware_gyro_odometer autoware_localization_util autoware_ndt_scan_matcher autoware_pose_initializer autoware_stop_filter autoware_twist2accel autoware_core_map autoware_lanelet2_map_visualizer autoware_map_height_fitter autoware_map_loader autoware_map_projection_loader autoware_core_perception autoware_euclidean_cluster_object_detector autoware_ground_filter autoware_perception_objects_converter autoware_core_planning autoware_mission_planner autoware_objects_of_interest_marker_interface autoware_path_generator autoware_planning_factor_interface autoware_planning_topic_converter autoware_route_handler autoware_velocity_smoother autoware_behavior_velocity_planner autoware_behavior_velocity_planner_common autoware_behavior_velocity_stop_line_module autoware_motion_velocity_obstacle_stop_module autoware_motion_velocity_planner autoware_motion_velocity_planner_common autoware_core_sensing autoware_crop_box_filter autoware_downsample_filters autoware_gnss_poser autoware_vehicle_velocity_converter autoware_planning_test_manager autoware_pyplot autoware_test_node autoware_test_utils autoware_testing autoware_core_vehicle

ROS Distro
humble

Package Summary

Version 1.9.0
License Apache License 2.0
Build type AMENT_CMAKE
Use RECOMMENDED

Repository Summary

Checkout URI https://github.com/autowarefoundation/autoware_core.git
VCS Type git
VCS Version main
Last Updated 2026-07-03
Dev Status DEVELOPED
Released RELEASED
Contributing Help Wanted (-)
Good First Issues (-)
Pull Requests to Review (-)

Package Description

The autoware_vehicle_info_utils package

Maintainers

  • Taiki Tanaka
  • Tomoya Kimura
  • Shumpei Wakabayashi
  • Mamoru Sobue
  • Jian Kang

Authors

  • Yamato ANDO

Vehicle Info Util

Purpose

This package is to get vehicle info parameters.

Description

In here, you can check the vehicle dimensions with more detail. The current format supports only the Ackermann model. This file defines the model assumed in autoware path planning, control, etc. and does not represent the exact physical model. If a model other than the Ackermann model is used, it is assumed that a vehicle interface will be designed to change the control output for the model.

Versioning Policy

We have implemented a versioning system for the vehicle_info.param.yaml file to ensure clarity and consistency in file format across different versions of Autoware and its external applications. Please see discussion for the details.

How to Operate

  • The current file format is set as an unversioned base version (version: field is commented out).
  • For the next update involving changes (such as additions, deletions, or modifications):
    • Uncomment and update the version line at the beginning of the file.
    • Initiate versioning by assigning a version number, starting from 0.1.0. Follow the semantic versioning format (MAJOR.MINOR.PATCH).
    • Update this Readme.md too.
  • For subsequent updates, continue incrementing the version number in accordance with the changes made.
    • Discuss how to increment version depending on the amount of changes made to the file.
/**:
  ros__parameters:
    # version: 0.1.0 # Uncomment and update this line for future format changes.
    wheel_radius: 0.383
    ...

Why Versioning?

  • Consistency Across Updates: Implementing version control will allow accurate tracking of changes over time and changes in vehicle information parameters.
  • Clarity for External Applications: External applications that depend on vehicle_info.param.yaml need to reference the correct file version for optimal compatibility and functionality.
  • Simplified Management for Customized Branches: Assigning versions directly to the vehicle_info.param.yaml file simplifies management compared to maintaining separate versions for multiple customized Autoware branches. This approach streamlines version tracking and reduces complexity.

Scripts

Minimum turning radius

$ ros2 run autoware_vehicle_info_utils min_turning_radius_calculator.py
yaml path is /home/autoware/pilot-auto/install/autoware_vehicle_info_utils/share/autoware_vehicle_info_utils/config/vehicle_info.param.yaml
Minimum turning radius is 3.253042620027102 [m] for rear, 4.253220695862465 [m] for front.

You can designate yaml file with -y option as follows.

ros2 run autoware_vehicle_info_utils min_turning_radius_calculator.py -y <path-to-yaml>

Assumptions / Known limits

TBD.

CHANGELOG

Changelog for package autoware_vehicle_info_utils

1.1.0 (2025-05-01)

  • refactor(autoware_vehicle_info_utils): rewrite using modern C++ without API breakage (#343)
  • Contributors: Yutaka Kondo

1.9.0 (2026-06-24)

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

  • test(autoware_vehicle_info_utils): cover pure paths and reuse get_or_declare_parameter (#1105)

    * test(autoware_vehicle_info_utils): cover pure paths and reuse get_or_declare_parameter Add no-ROS unit tests for the pure VehicleInfo helpers that were previously untested: createVehicleInfo's wheel_base/max_steer clamping and has_non_positive_values branches, calcMaxMinDimension's two branches, extendVehicleInfo's margin distribution, the full 5-margin createFootprint overload (asymmetric margins plus center_at_base_link, asserting all seven ring points), and calcCurvatureFromSteerAngle's NaN guard. These run directly against the free functions / VehicleInfo methods without rclcpp. Replace the file-local getParameter<T> helper in VehicleInfoUtils with autoware_utils_rclcpp::get_or_declare_parameter<T>, which has identical has_parameter/get/declare semantics, and add the autoware_utils_rclcpp dependency. The throwing behavior on a parameter type mismatch is preserved (declare_parameter still throws); only the redundant local RCLCPP_ERROR log line on that path is dropped. No public API change. Refs: autowarefoundation/autoware_core#1096

    * test(autoware_vehicle_info_utils): de-tautologize vehicle_info test oracles (#79) Replace expected values that mirrored the implementation's formula or were read back from the output fields under test with independently hand-computed concrete literals (or stdlib-only computations in the std::hypot style). This makes the assertions verify the calculation instead of re-deriving the same potentially-wrong value. Refs: autowarefoundation/autoware_core#1096

    * test(autoware_vehicle_info_utils): use independent oracles for derived-value asserts (#86) Replace test expected values that mirrored the implementation's own formulas with concrete, independently hand-computed literals so the assertions can no longer pass on a wrong production calculation.

    - extendVehicleInfo: assert hardcoded 4.4 / 2.4 / 1.2 instead of reconstructing 'length + margin' / 'base2back + margin / 2'.

    - calcMaxMinDimension branch guards: drop the ASSERTs that recomputed base2front from the output fields; the branch is fixed by the test-chosen inputs and documented in comments. std::hypot-style expected values (inputs picked by the test, stdlib as the only shared dependency) and the existing hardcoded literals are kept. No production code changed. Refs: autowarefoundation/autoware_core#1096 ---------

  • feat(vehicle_info_utils): adjust [VehicleInfo]{.title-ref} to cover [VehicleShape]{.title-ref} (#1083)

    • add function to help replacing VehicleShape

    * remove defaulted function ---------Co-authored-by: Junya Sasaki <<j2sasaki1990@gmail.com>>

  • feat(autoware_vehicle_info_utils): add base_pose to createFootprint (#1072)

  • Contributors: Sarun MUKDAPITAK, Yutaka Kondo, github-actions

1.8.0 (2026-05-01)

  • Merge remote-tracking branch 'origin/main' into tmp/bot/bump_version_base
  • refactor(autoware_core): add USE_SCOPED_HEADER_INSTALL_DIR to common and testing packages (#967) Co-authored-by: github-actions <<github-actions@github.com>> Co-authored-by: Junya Sasaki <<j2sasaki1990@gmail.com>>
  • Contributors: Vishal Chauhan, github-actions

1.7.0 (2026-02-14)

1.6.0 (2025-12-30)

  • Merge remote-tracking branch 'origin/main' into tmp/bot/bump_version_base
  • docs: fix broken links (#779)

File truncated at 100 lines see the full file

Launch files

No launch files found

Messages

No message files found.

Services

No service files found

Plugins

No plugins found.

Recent questions tagged autoware_vehicle_info_utils at Robotics Stack Exchange

No version for distro eloquent showing humble. Known supported distros are highlighted in the buttons above.
Package symbol

autoware_vehicle_info_utils package from autoware_core repo

autoware_adapi_adaptors autoware_adapi_specs autoware_core_api autoware_default_adapi autoware_core autoware_agnocast_wrapper autoware_component_interface_specs autoware_geography_utils autoware_global_parameter_loader autoware_interpolation autoware_kalman_filter autoware_lanelet2_utils autoware_marker_utils autoware_motion_utils autoware_node autoware_object_recognition_utils autoware_osqp_interface autoware_point_types autoware_qos_utils autoware_qp_interface autoware_signal_processing autoware_trajectory autoware_vehicle_info_utils autoware_command_gate autoware_core_control autoware_simple_pure_pursuit autoware_awsim_sensor_kit_description autoware_sample_sensor_kit_description autoware_sample_vehicle_description autoware_core_localization autoware_ekf_localizer autoware_gyro_odometer autoware_localization_util autoware_ndt_scan_matcher autoware_pose_initializer autoware_stop_filter autoware_twist2accel autoware_core_map autoware_lanelet2_map_visualizer autoware_map_height_fitter autoware_map_loader autoware_map_projection_loader autoware_core_perception autoware_euclidean_cluster_object_detector autoware_ground_filter autoware_perception_objects_converter autoware_core_planning autoware_mission_planner autoware_objects_of_interest_marker_interface autoware_path_generator autoware_planning_factor_interface autoware_planning_topic_converter autoware_route_handler autoware_velocity_smoother autoware_behavior_velocity_planner autoware_behavior_velocity_planner_common autoware_behavior_velocity_stop_line_module autoware_motion_velocity_obstacle_stop_module autoware_motion_velocity_planner autoware_motion_velocity_planner_common autoware_core_sensing autoware_crop_box_filter autoware_downsample_filters autoware_gnss_poser autoware_vehicle_velocity_converter autoware_planning_test_manager autoware_pyplot autoware_test_node autoware_test_utils autoware_testing autoware_core_vehicle

ROS Distro
humble

Package Summary

Version 1.9.0
License Apache License 2.0
Build type AMENT_CMAKE
Use RECOMMENDED

Repository Summary

Checkout URI https://github.com/autowarefoundation/autoware_core.git
VCS Type git
VCS Version main
Last Updated 2026-07-03
Dev Status DEVELOPED
Released RELEASED
Contributing Help Wanted (-)
Good First Issues (-)
Pull Requests to Review (-)

Package Description

The autoware_vehicle_info_utils package

Maintainers

  • Taiki Tanaka
  • Tomoya Kimura
  • Shumpei Wakabayashi
  • Mamoru Sobue
  • Jian Kang

Authors

  • Yamato ANDO

Vehicle Info Util

Purpose

This package is to get vehicle info parameters.

Description

In here, you can check the vehicle dimensions with more detail. The current format supports only the Ackermann model. This file defines the model assumed in autoware path planning, control, etc. and does not represent the exact physical model. If a model other than the Ackermann model is used, it is assumed that a vehicle interface will be designed to change the control output for the model.

Versioning Policy

We have implemented a versioning system for the vehicle_info.param.yaml file to ensure clarity and consistency in file format across different versions of Autoware and its external applications. Please see discussion for the details.

How to Operate

  • The current file format is set as an unversioned base version (version: field is commented out).
  • For the next update involving changes (such as additions, deletions, or modifications):
    • Uncomment and update the version line at the beginning of the file.
    • Initiate versioning by assigning a version number, starting from 0.1.0. Follow the semantic versioning format (MAJOR.MINOR.PATCH).
    • Update this Readme.md too.
  • For subsequent updates, continue incrementing the version number in accordance with the changes made.
    • Discuss how to increment version depending on the amount of changes made to the file.
/**:
  ros__parameters:
    # version: 0.1.0 # Uncomment and update this line for future format changes.
    wheel_radius: 0.383
    ...

Why Versioning?

  • Consistency Across Updates: Implementing version control will allow accurate tracking of changes over time and changes in vehicle information parameters.
  • Clarity for External Applications: External applications that depend on vehicle_info.param.yaml need to reference the correct file version for optimal compatibility and functionality.
  • Simplified Management for Customized Branches: Assigning versions directly to the vehicle_info.param.yaml file simplifies management compared to maintaining separate versions for multiple customized Autoware branches. This approach streamlines version tracking and reduces complexity.

Scripts

Minimum turning radius

$ ros2 run autoware_vehicle_info_utils min_turning_radius_calculator.py
yaml path is /home/autoware/pilot-auto/install/autoware_vehicle_info_utils/share/autoware_vehicle_info_utils/config/vehicle_info.param.yaml
Minimum turning radius is 3.253042620027102 [m] for rear, 4.253220695862465 [m] for front.

You can designate yaml file with -y option as follows.

ros2 run autoware_vehicle_info_utils min_turning_radius_calculator.py -y <path-to-yaml>

Assumptions / Known limits

TBD.

CHANGELOG

Changelog for package autoware_vehicle_info_utils

1.1.0 (2025-05-01)

  • refactor(autoware_vehicle_info_utils): rewrite using modern C++ without API breakage (#343)
  • Contributors: Yutaka Kondo

1.9.0 (2026-06-24)

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

  • test(autoware_vehicle_info_utils): cover pure paths and reuse get_or_declare_parameter (#1105)

    * test(autoware_vehicle_info_utils): cover pure paths and reuse get_or_declare_parameter Add no-ROS unit tests for the pure VehicleInfo helpers that were previously untested: createVehicleInfo's wheel_base/max_steer clamping and has_non_positive_values branches, calcMaxMinDimension's two branches, extendVehicleInfo's margin distribution, the full 5-margin createFootprint overload (asymmetric margins plus center_at_base_link, asserting all seven ring points), and calcCurvatureFromSteerAngle's NaN guard. These run directly against the free functions / VehicleInfo methods without rclcpp. Replace the file-local getParameter<T> helper in VehicleInfoUtils with autoware_utils_rclcpp::get_or_declare_parameter<T>, which has identical has_parameter/get/declare semantics, and add the autoware_utils_rclcpp dependency. The throwing behavior on a parameter type mismatch is preserved (declare_parameter still throws); only the redundant local RCLCPP_ERROR log line on that path is dropped. No public API change. Refs: autowarefoundation/autoware_core#1096

    * test(autoware_vehicle_info_utils): de-tautologize vehicle_info test oracles (#79) Replace expected values that mirrored the implementation's formula or were read back from the output fields under test with independently hand-computed concrete literals (or stdlib-only computations in the std::hypot style). This makes the assertions verify the calculation instead of re-deriving the same potentially-wrong value. Refs: autowarefoundation/autoware_core#1096

    * test(autoware_vehicle_info_utils): use independent oracles for derived-value asserts (#86) Replace test expected values that mirrored the implementation's own formulas with concrete, independently hand-computed literals so the assertions can no longer pass on a wrong production calculation.

    - extendVehicleInfo: assert hardcoded 4.4 / 2.4 / 1.2 instead of reconstructing 'length + margin' / 'base2back + margin / 2'.

    - calcMaxMinDimension branch guards: drop the ASSERTs that recomputed base2front from the output fields; the branch is fixed by the test-chosen inputs and documented in comments. std::hypot-style expected values (inputs picked by the test, stdlib as the only shared dependency) and the existing hardcoded literals are kept. No production code changed. Refs: autowarefoundation/autoware_core#1096 ---------

  • feat(vehicle_info_utils): adjust [VehicleInfo]{.title-ref} to cover [VehicleShape]{.title-ref} (#1083)

    • add function to help replacing VehicleShape

    * remove defaulted function ---------Co-authored-by: Junya Sasaki <<j2sasaki1990@gmail.com>>

  • feat(autoware_vehicle_info_utils): add base_pose to createFootprint (#1072)

  • Contributors: Sarun MUKDAPITAK, Yutaka Kondo, github-actions

1.8.0 (2026-05-01)

  • Merge remote-tracking branch 'origin/main' into tmp/bot/bump_version_base
  • refactor(autoware_core): add USE_SCOPED_HEADER_INSTALL_DIR to common and testing packages (#967) Co-authored-by: github-actions <<github-actions@github.com>> Co-authored-by: Junya Sasaki <<j2sasaki1990@gmail.com>>
  • Contributors: Vishal Chauhan, github-actions

1.7.0 (2026-02-14)

1.6.0 (2025-12-30)

  • Merge remote-tracking branch 'origin/main' into tmp/bot/bump_version_base
  • docs: fix broken links (#779)

File truncated at 100 lines see the full file

Launch files

No launch files found

Messages

No message files found.

Services

No service files found

Plugins

No plugins found.

Recent questions tagged autoware_vehicle_info_utils at Robotics Stack Exchange

No version for distro dashing showing humble. Known supported distros are highlighted in the buttons above.
Package symbol

autoware_vehicle_info_utils package from autoware_core repo

autoware_adapi_adaptors autoware_adapi_specs autoware_core_api autoware_default_adapi autoware_core autoware_agnocast_wrapper autoware_component_interface_specs autoware_geography_utils autoware_global_parameter_loader autoware_interpolation autoware_kalman_filter autoware_lanelet2_utils autoware_marker_utils autoware_motion_utils autoware_node autoware_object_recognition_utils autoware_osqp_interface autoware_point_types autoware_qos_utils autoware_qp_interface autoware_signal_processing autoware_trajectory autoware_vehicle_info_utils autoware_command_gate autoware_core_control autoware_simple_pure_pursuit autoware_awsim_sensor_kit_description autoware_sample_sensor_kit_description autoware_sample_vehicle_description autoware_core_localization autoware_ekf_localizer autoware_gyro_odometer autoware_localization_util autoware_ndt_scan_matcher autoware_pose_initializer autoware_stop_filter autoware_twist2accel autoware_core_map autoware_lanelet2_map_visualizer autoware_map_height_fitter autoware_map_loader autoware_map_projection_loader autoware_core_perception autoware_euclidean_cluster_object_detector autoware_ground_filter autoware_perception_objects_converter autoware_core_planning autoware_mission_planner autoware_objects_of_interest_marker_interface autoware_path_generator autoware_planning_factor_interface autoware_planning_topic_converter autoware_route_handler autoware_velocity_smoother autoware_behavior_velocity_planner autoware_behavior_velocity_planner_common autoware_behavior_velocity_stop_line_module autoware_motion_velocity_obstacle_stop_module autoware_motion_velocity_planner autoware_motion_velocity_planner_common autoware_core_sensing autoware_crop_box_filter autoware_downsample_filters autoware_gnss_poser autoware_vehicle_velocity_converter autoware_planning_test_manager autoware_pyplot autoware_test_node autoware_test_utils autoware_testing autoware_core_vehicle

ROS Distro
humble

Package Summary

Version 1.9.0
License Apache License 2.0
Build type AMENT_CMAKE
Use RECOMMENDED

Repository Summary

Checkout URI https://github.com/autowarefoundation/autoware_core.git
VCS Type git
VCS Version main
Last Updated 2026-07-03
Dev Status DEVELOPED
Released RELEASED
Contributing Help Wanted (-)
Good First Issues (-)
Pull Requests to Review (-)

Package Description

The autoware_vehicle_info_utils package

Maintainers

  • Taiki Tanaka
  • Tomoya Kimura
  • Shumpei Wakabayashi
  • Mamoru Sobue
  • Jian Kang

Authors

  • Yamato ANDO

Vehicle Info Util

Purpose

This package is to get vehicle info parameters.

Description

In here, you can check the vehicle dimensions with more detail. The current format supports only the Ackermann model. This file defines the model assumed in autoware path planning, control, etc. and does not represent the exact physical model. If a model other than the Ackermann model is used, it is assumed that a vehicle interface will be designed to change the control output for the model.

Versioning Policy

We have implemented a versioning system for the vehicle_info.param.yaml file to ensure clarity and consistency in file format across different versions of Autoware and its external applications. Please see discussion for the details.

How to Operate

  • The current file format is set as an unversioned base version (version: field is commented out).
  • For the next update involving changes (such as additions, deletions, or modifications):
    • Uncomment and update the version line at the beginning of the file.
    • Initiate versioning by assigning a version number, starting from 0.1.0. Follow the semantic versioning format (MAJOR.MINOR.PATCH).
    • Update this Readme.md too.
  • For subsequent updates, continue incrementing the version number in accordance with the changes made.
    • Discuss how to increment version depending on the amount of changes made to the file.
/**:
  ros__parameters:
    # version: 0.1.0 # Uncomment and update this line for future format changes.
    wheel_radius: 0.383
    ...

Why Versioning?

  • Consistency Across Updates: Implementing version control will allow accurate tracking of changes over time and changes in vehicle information parameters.
  • Clarity for External Applications: External applications that depend on vehicle_info.param.yaml need to reference the correct file version for optimal compatibility and functionality.
  • Simplified Management for Customized Branches: Assigning versions directly to the vehicle_info.param.yaml file simplifies management compared to maintaining separate versions for multiple customized Autoware branches. This approach streamlines version tracking and reduces complexity.

Scripts

Minimum turning radius

$ ros2 run autoware_vehicle_info_utils min_turning_radius_calculator.py
yaml path is /home/autoware/pilot-auto/install/autoware_vehicle_info_utils/share/autoware_vehicle_info_utils/config/vehicle_info.param.yaml
Minimum turning radius is 3.253042620027102 [m] for rear, 4.253220695862465 [m] for front.

You can designate yaml file with -y option as follows.

ros2 run autoware_vehicle_info_utils min_turning_radius_calculator.py -y <path-to-yaml>

Assumptions / Known limits

TBD.

CHANGELOG

Changelog for package autoware_vehicle_info_utils

1.1.0 (2025-05-01)

  • refactor(autoware_vehicle_info_utils): rewrite using modern C++ without API breakage (#343)
  • Contributors: Yutaka Kondo

1.9.0 (2026-06-24)

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

  • test(autoware_vehicle_info_utils): cover pure paths and reuse get_or_declare_parameter (#1105)

    * test(autoware_vehicle_info_utils): cover pure paths and reuse get_or_declare_parameter Add no-ROS unit tests for the pure VehicleInfo helpers that were previously untested: createVehicleInfo's wheel_base/max_steer clamping and has_non_positive_values branches, calcMaxMinDimension's two branches, extendVehicleInfo's margin distribution, the full 5-margin createFootprint overload (asymmetric margins plus center_at_base_link, asserting all seven ring points), and calcCurvatureFromSteerAngle's NaN guard. These run directly against the free functions / VehicleInfo methods without rclcpp. Replace the file-local getParameter<T> helper in VehicleInfoUtils with autoware_utils_rclcpp::get_or_declare_parameter<T>, which has identical has_parameter/get/declare semantics, and add the autoware_utils_rclcpp dependency. The throwing behavior on a parameter type mismatch is preserved (declare_parameter still throws); only the redundant local RCLCPP_ERROR log line on that path is dropped. No public API change. Refs: autowarefoundation/autoware_core#1096

    * test(autoware_vehicle_info_utils): de-tautologize vehicle_info test oracles (#79) Replace expected values that mirrored the implementation's formula or were read back from the output fields under test with independently hand-computed concrete literals (or stdlib-only computations in the std::hypot style). This makes the assertions verify the calculation instead of re-deriving the same potentially-wrong value. Refs: autowarefoundation/autoware_core#1096

    * test(autoware_vehicle_info_utils): use independent oracles for derived-value asserts (#86) Replace test expected values that mirrored the implementation's own formulas with concrete, independently hand-computed literals so the assertions can no longer pass on a wrong production calculation.

    - extendVehicleInfo: assert hardcoded 4.4 / 2.4 / 1.2 instead of reconstructing 'length + margin' / 'base2back + margin / 2'.

    - calcMaxMinDimension branch guards: drop the ASSERTs that recomputed base2front from the output fields; the branch is fixed by the test-chosen inputs and documented in comments. std::hypot-style expected values (inputs picked by the test, stdlib as the only shared dependency) and the existing hardcoded literals are kept. No production code changed. Refs: autowarefoundation/autoware_core#1096 ---------

  • feat(vehicle_info_utils): adjust [VehicleInfo]{.title-ref} to cover [VehicleShape]{.title-ref} (#1083)

    • add function to help replacing VehicleShape

    * remove defaulted function ---------Co-authored-by: Junya Sasaki <<j2sasaki1990@gmail.com>>

  • feat(autoware_vehicle_info_utils): add base_pose to createFootprint (#1072)

  • Contributors: Sarun MUKDAPITAK, Yutaka Kondo, github-actions

1.8.0 (2026-05-01)

  • Merge remote-tracking branch 'origin/main' into tmp/bot/bump_version_base
  • refactor(autoware_core): add USE_SCOPED_HEADER_INSTALL_DIR to common and testing packages (#967) Co-authored-by: github-actions <<github-actions@github.com>> Co-authored-by: Junya Sasaki <<j2sasaki1990@gmail.com>>
  • Contributors: Vishal Chauhan, github-actions

1.7.0 (2026-02-14)

1.6.0 (2025-12-30)

  • Merge remote-tracking branch 'origin/main' into tmp/bot/bump_version_base
  • docs: fix broken links (#779)

File truncated at 100 lines see the full file

Launch files

No launch files found

Messages

No message files found.

Services

No service files found

Plugins

No plugins found.

Recent questions tagged autoware_vehicle_info_utils at Robotics Stack Exchange

No version for distro galactic showing humble. Known supported distros are highlighted in the buttons above.
Package symbol

autoware_vehicle_info_utils package from autoware_core repo

autoware_adapi_adaptors autoware_adapi_specs autoware_core_api autoware_default_adapi autoware_core autoware_agnocast_wrapper autoware_component_interface_specs autoware_geography_utils autoware_global_parameter_loader autoware_interpolation autoware_kalman_filter autoware_lanelet2_utils autoware_marker_utils autoware_motion_utils autoware_node autoware_object_recognition_utils autoware_osqp_interface autoware_point_types autoware_qos_utils autoware_qp_interface autoware_signal_processing autoware_trajectory autoware_vehicle_info_utils autoware_command_gate autoware_core_control autoware_simple_pure_pursuit autoware_awsim_sensor_kit_description autoware_sample_sensor_kit_description autoware_sample_vehicle_description autoware_core_localization autoware_ekf_localizer autoware_gyro_odometer autoware_localization_util autoware_ndt_scan_matcher autoware_pose_initializer autoware_stop_filter autoware_twist2accel autoware_core_map autoware_lanelet2_map_visualizer autoware_map_height_fitter autoware_map_loader autoware_map_projection_loader autoware_core_perception autoware_euclidean_cluster_object_detector autoware_ground_filter autoware_perception_objects_converter autoware_core_planning autoware_mission_planner autoware_objects_of_interest_marker_interface autoware_path_generator autoware_planning_factor_interface autoware_planning_topic_converter autoware_route_handler autoware_velocity_smoother autoware_behavior_velocity_planner autoware_behavior_velocity_planner_common autoware_behavior_velocity_stop_line_module autoware_motion_velocity_obstacle_stop_module autoware_motion_velocity_planner autoware_motion_velocity_planner_common autoware_core_sensing autoware_crop_box_filter autoware_downsample_filters autoware_gnss_poser autoware_vehicle_velocity_converter autoware_planning_test_manager autoware_pyplot autoware_test_node autoware_test_utils autoware_testing autoware_core_vehicle

ROS Distro
humble

Package Summary

Version 1.9.0
License Apache License 2.0
Build type AMENT_CMAKE
Use RECOMMENDED

Repository Summary

Checkout URI https://github.com/autowarefoundation/autoware_core.git
VCS Type git
VCS Version main
Last Updated 2026-07-03
Dev Status DEVELOPED
Released RELEASED
Contributing Help Wanted (-)
Good First Issues (-)
Pull Requests to Review (-)

Package Description

The autoware_vehicle_info_utils package

Maintainers

  • Taiki Tanaka
  • Tomoya Kimura
  • Shumpei Wakabayashi
  • Mamoru Sobue
  • Jian Kang

Authors

  • Yamato ANDO

Vehicle Info Util

Purpose

This package is to get vehicle info parameters.

Description

In here, you can check the vehicle dimensions with more detail. The current format supports only the Ackermann model. This file defines the model assumed in autoware path planning, control, etc. and does not represent the exact physical model. If a model other than the Ackermann model is used, it is assumed that a vehicle interface will be designed to change the control output for the model.

Versioning Policy

We have implemented a versioning system for the vehicle_info.param.yaml file to ensure clarity and consistency in file format across different versions of Autoware and its external applications. Please see discussion for the details.

How to Operate

  • The current file format is set as an unversioned base version (version: field is commented out).
  • For the next update involving changes (such as additions, deletions, or modifications):
    • Uncomment and update the version line at the beginning of the file.
    • Initiate versioning by assigning a version number, starting from 0.1.0. Follow the semantic versioning format (MAJOR.MINOR.PATCH).
    • Update this Readme.md too.
  • For subsequent updates, continue incrementing the version number in accordance with the changes made.
    • Discuss how to increment version depending on the amount of changes made to the file.
/**:
  ros__parameters:
    # version: 0.1.0 # Uncomment and update this line for future format changes.
    wheel_radius: 0.383
    ...

Why Versioning?

  • Consistency Across Updates: Implementing version control will allow accurate tracking of changes over time and changes in vehicle information parameters.
  • Clarity for External Applications: External applications that depend on vehicle_info.param.yaml need to reference the correct file version for optimal compatibility and functionality.
  • Simplified Management for Customized Branches: Assigning versions directly to the vehicle_info.param.yaml file simplifies management compared to maintaining separate versions for multiple customized Autoware branches. This approach streamlines version tracking and reduces complexity.

Scripts

Minimum turning radius

$ ros2 run autoware_vehicle_info_utils min_turning_radius_calculator.py
yaml path is /home/autoware/pilot-auto/install/autoware_vehicle_info_utils/share/autoware_vehicle_info_utils/config/vehicle_info.param.yaml
Minimum turning radius is 3.253042620027102 [m] for rear, 4.253220695862465 [m] for front.

You can designate yaml file with -y option as follows.

ros2 run autoware_vehicle_info_utils min_turning_radius_calculator.py -y <path-to-yaml>

Assumptions / Known limits

TBD.

CHANGELOG

Changelog for package autoware_vehicle_info_utils

1.1.0 (2025-05-01)

  • refactor(autoware_vehicle_info_utils): rewrite using modern C++ without API breakage (#343)
  • Contributors: Yutaka Kondo

1.9.0 (2026-06-24)

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

  • test(autoware_vehicle_info_utils): cover pure paths and reuse get_or_declare_parameter (#1105)

    * test(autoware_vehicle_info_utils): cover pure paths and reuse get_or_declare_parameter Add no-ROS unit tests for the pure VehicleInfo helpers that were previously untested: createVehicleInfo's wheel_base/max_steer clamping and has_non_positive_values branches, calcMaxMinDimension's two branches, extendVehicleInfo's margin distribution, the full 5-margin createFootprint overload (asymmetric margins plus center_at_base_link, asserting all seven ring points), and calcCurvatureFromSteerAngle's NaN guard. These run directly against the free functions / VehicleInfo methods without rclcpp. Replace the file-local getParameter<T> helper in VehicleInfoUtils with autoware_utils_rclcpp::get_or_declare_parameter<T>, which has identical has_parameter/get/declare semantics, and add the autoware_utils_rclcpp dependency. The throwing behavior on a parameter type mismatch is preserved (declare_parameter still throws); only the redundant local RCLCPP_ERROR log line on that path is dropped. No public API change. Refs: autowarefoundation/autoware_core#1096

    * test(autoware_vehicle_info_utils): de-tautologize vehicle_info test oracles (#79) Replace expected values that mirrored the implementation's formula or were read back from the output fields under test with independently hand-computed concrete literals (or stdlib-only computations in the std::hypot style). This makes the assertions verify the calculation instead of re-deriving the same potentially-wrong value. Refs: autowarefoundation/autoware_core#1096

    * test(autoware_vehicle_info_utils): use independent oracles for derived-value asserts (#86) Replace test expected values that mirrored the implementation's own formulas with concrete, independently hand-computed literals so the assertions can no longer pass on a wrong production calculation.

    - extendVehicleInfo: assert hardcoded 4.4 / 2.4 / 1.2 instead of reconstructing 'length + margin' / 'base2back + margin / 2'.

    - calcMaxMinDimension branch guards: drop the ASSERTs that recomputed base2front from the output fields; the branch is fixed by the test-chosen inputs and documented in comments. std::hypot-style expected values (inputs picked by the test, stdlib as the only shared dependency) and the existing hardcoded literals are kept. No production code changed. Refs: autowarefoundation/autoware_core#1096 ---------

  • feat(vehicle_info_utils): adjust [VehicleInfo]{.title-ref} to cover [VehicleShape]{.title-ref} (#1083)

    • add function to help replacing VehicleShape

    * remove defaulted function ---------Co-authored-by: Junya Sasaki <<j2sasaki1990@gmail.com>>

  • feat(autoware_vehicle_info_utils): add base_pose to createFootprint (#1072)

  • Contributors: Sarun MUKDAPITAK, Yutaka Kondo, github-actions

1.8.0 (2026-05-01)

  • Merge remote-tracking branch 'origin/main' into tmp/bot/bump_version_base
  • refactor(autoware_core): add USE_SCOPED_HEADER_INSTALL_DIR to common and testing packages (#967) Co-authored-by: github-actions <<github-actions@github.com>> Co-authored-by: Junya Sasaki <<j2sasaki1990@gmail.com>>
  • Contributors: Vishal Chauhan, github-actions

1.7.0 (2026-02-14)

1.6.0 (2025-12-30)

  • Merge remote-tracking branch 'origin/main' into tmp/bot/bump_version_base
  • docs: fix broken links (#779)

File truncated at 100 lines see the full file

Launch files

No launch files found

Messages

No message files found.

Services

No service files found

Plugins

No plugins found.

Recent questions tagged autoware_vehicle_info_utils at Robotics Stack Exchange

No version for distro foxy showing humble. Known supported distros are highlighted in the buttons above.
Package symbol

autoware_vehicle_info_utils package from autoware_core repo

autoware_adapi_adaptors autoware_adapi_specs autoware_core_api autoware_default_adapi autoware_core autoware_agnocast_wrapper autoware_component_interface_specs autoware_geography_utils autoware_global_parameter_loader autoware_interpolation autoware_kalman_filter autoware_lanelet2_utils autoware_marker_utils autoware_motion_utils autoware_node autoware_object_recognition_utils autoware_osqp_interface autoware_point_types autoware_qos_utils autoware_qp_interface autoware_signal_processing autoware_trajectory autoware_vehicle_info_utils autoware_command_gate autoware_core_control autoware_simple_pure_pursuit autoware_awsim_sensor_kit_description autoware_sample_sensor_kit_description autoware_sample_vehicle_description autoware_core_localization autoware_ekf_localizer autoware_gyro_odometer autoware_localization_util autoware_ndt_scan_matcher autoware_pose_initializer autoware_stop_filter autoware_twist2accel autoware_core_map autoware_lanelet2_map_visualizer autoware_map_height_fitter autoware_map_loader autoware_map_projection_loader autoware_core_perception autoware_euclidean_cluster_object_detector autoware_ground_filter autoware_perception_objects_converter autoware_core_planning autoware_mission_planner autoware_objects_of_interest_marker_interface autoware_path_generator autoware_planning_factor_interface autoware_planning_topic_converter autoware_route_handler autoware_velocity_smoother autoware_behavior_velocity_planner autoware_behavior_velocity_planner_common autoware_behavior_velocity_stop_line_module autoware_motion_velocity_obstacle_stop_module autoware_motion_velocity_planner autoware_motion_velocity_planner_common autoware_core_sensing autoware_crop_box_filter autoware_downsample_filters autoware_gnss_poser autoware_vehicle_velocity_converter autoware_planning_test_manager autoware_pyplot autoware_test_node autoware_test_utils autoware_testing autoware_core_vehicle

ROS Distro
humble

Package Summary

Version 1.9.0
License Apache License 2.0
Build type AMENT_CMAKE
Use RECOMMENDED

Repository Summary

Checkout URI https://github.com/autowarefoundation/autoware_core.git
VCS Type git
VCS Version main
Last Updated 2026-07-03
Dev Status DEVELOPED
Released RELEASED
Contributing Help Wanted (-)
Good First Issues (-)
Pull Requests to Review (-)

Package Description

The autoware_vehicle_info_utils package

Maintainers

  • Taiki Tanaka
  • Tomoya Kimura
  • Shumpei Wakabayashi
  • Mamoru Sobue
  • Jian Kang

Authors

  • Yamato ANDO

Vehicle Info Util

Purpose

This package is to get vehicle info parameters.

Description

In here, you can check the vehicle dimensions with more detail. The current format supports only the Ackermann model. This file defines the model assumed in autoware path planning, control, etc. and does not represent the exact physical model. If a model other than the Ackermann model is used, it is assumed that a vehicle interface will be designed to change the control output for the model.

Versioning Policy

We have implemented a versioning system for the vehicle_info.param.yaml file to ensure clarity and consistency in file format across different versions of Autoware and its external applications. Please see discussion for the details.

How to Operate

  • The current file format is set as an unversioned base version (version: field is commented out).
  • For the next update involving changes (such as additions, deletions, or modifications):
    • Uncomment and update the version line at the beginning of the file.
    • Initiate versioning by assigning a version number, starting from 0.1.0. Follow the semantic versioning format (MAJOR.MINOR.PATCH).
    • Update this Readme.md too.
  • For subsequent updates, continue incrementing the version number in accordance with the changes made.
    • Discuss how to increment version depending on the amount of changes made to the file.
/**:
  ros__parameters:
    # version: 0.1.0 # Uncomment and update this line for future format changes.
    wheel_radius: 0.383
    ...

Why Versioning?

  • Consistency Across Updates: Implementing version control will allow accurate tracking of changes over time and changes in vehicle information parameters.
  • Clarity for External Applications: External applications that depend on vehicle_info.param.yaml need to reference the correct file version for optimal compatibility and functionality.
  • Simplified Management for Customized Branches: Assigning versions directly to the vehicle_info.param.yaml file simplifies management compared to maintaining separate versions for multiple customized Autoware branches. This approach streamlines version tracking and reduces complexity.

Scripts

Minimum turning radius

$ ros2 run autoware_vehicle_info_utils min_turning_radius_calculator.py
yaml path is /home/autoware/pilot-auto/install/autoware_vehicle_info_utils/share/autoware_vehicle_info_utils/config/vehicle_info.param.yaml
Minimum turning radius is 3.253042620027102 [m] for rear, 4.253220695862465 [m] for front.

You can designate yaml file with -y option as follows.

ros2 run autoware_vehicle_info_utils min_turning_radius_calculator.py -y <path-to-yaml>

Assumptions / Known limits

TBD.

CHANGELOG

Changelog for package autoware_vehicle_info_utils

1.1.0 (2025-05-01)

  • refactor(autoware_vehicle_info_utils): rewrite using modern C++ without API breakage (#343)
  • Contributors: Yutaka Kondo

1.9.0 (2026-06-24)

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

  • test(autoware_vehicle_info_utils): cover pure paths and reuse get_or_declare_parameter (#1105)

    * test(autoware_vehicle_info_utils): cover pure paths and reuse get_or_declare_parameter Add no-ROS unit tests for the pure VehicleInfo helpers that were previously untested: createVehicleInfo's wheel_base/max_steer clamping and has_non_positive_values branches, calcMaxMinDimension's two branches, extendVehicleInfo's margin distribution, the full 5-margin createFootprint overload (asymmetric margins plus center_at_base_link, asserting all seven ring points), and calcCurvatureFromSteerAngle's NaN guard. These run directly against the free functions / VehicleInfo methods without rclcpp. Replace the file-local getParameter<T> helper in VehicleInfoUtils with autoware_utils_rclcpp::get_or_declare_parameter<T>, which has identical has_parameter/get/declare semantics, and add the autoware_utils_rclcpp dependency. The throwing behavior on a parameter type mismatch is preserved (declare_parameter still throws); only the redundant local RCLCPP_ERROR log line on that path is dropped. No public API change. Refs: autowarefoundation/autoware_core#1096

    * test(autoware_vehicle_info_utils): de-tautologize vehicle_info test oracles (#79) Replace expected values that mirrored the implementation's formula or were read back from the output fields under test with independently hand-computed concrete literals (or stdlib-only computations in the std::hypot style). This makes the assertions verify the calculation instead of re-deriving the same potentially-wrong value. Refs: autowarefoundation/autoware_core#1096

    * test(autoware_vehicle_info_utils): use independent oracles for derived-value asserts (#86) Replace test expected values that mirrored the implementation's own formulas with concrete, independently hand-computed literals so the assertions can no longer pass on a wrong production calculation.

    - extendVehicleInfo: assert hardcoded 4.4 / 2.4 / 1.2 instead of reconstructing 'length + margin' / 'base2back + margin / 2'.

    - calcMaxMinDimension branch guards: drop the ASSERTs that recomputed base2front from the output fields; the branch is fixed by the test-chosen inputs and documented in comments. std::hypot-style expected values (inputs picked by the test, stdlib as the only shared dependency) and the existing hardcoded literals are kept. No production code changed. Refs: autowarefoundation/autoware_core#1096 ---------

  • feat(vehicle_info_utils): adjust [VehicleInfo]{.title-ref} to cover [VehicleShape]{.title-ref} (#1083)

    • add function to help replacing VehicleShape

    * remove defaulted function ---------Co-authored-by: Junya Sasaki <<j2sasaki1990@gmail.com>>

  • feat(autoware_vehicle_info_utils): add base_pose to createFootprint (#1072)

  • Contributors: Sarun MUKDAPITAK, Yutaka Kondo, github-actions

1.8.0 (2026-05-01)

  • Merge remote-tracking branch 'origin/main' into tmp/bot/bump_version_base
  • refactor(autoware_core): add USE_SCOPED_HEADER_INSTALL_DIR to common and testing packages (#967) Co-authored-by: github-actions <<github-actions@github.com>> Co-authored-by: Junya Sasaki <<j2sasaki1990@gmail.com>>
  • Contributors: Vishal Chauhan, github-actions

1.7.0 (2026-02-14)

1.6.0 (2025-12-30)

  • Merge remote-tracking branch 'origin/main' into tmp/bot/bump_version_base
  • docs: fix broken links (#779)

File truncated at 100 lines see the full file

Launch files

No launch files found

Messages

No message files found.

Services

No service files found

Plugins

No plugins found.

Recent questions tagged autoware_vehicle_info_utils at Robotics Stack Exchange

No version for distro iron showing humble. Known supported distros are highlighted in the buttons above.
Package symbol

autoware_vehicle_info_utils package from autoware_core repo

autoware_adapi_adaptors autoware_adapi_specs autoware_core_api autoware_default_adapi autoware_core autoware_agnocast_wrapper autoware_component_interface_specs autoware_geography_utils autoware_global_parameter_loader autoware_interpolation autoware_kalman_filter autoware_lanelet2_utils autoware_marker_utils autoware_motion_utils autoware_node autoware_object_recognition_utils autoware_osqp_interface autoware_point_types autoware_qos_utils autoware_qp_interface autoware_signal_processing autoware_trajectory autoware_vehicle_info_utils autoware_command_gate autoware_core_control autoware_simple_pure_pursuit autoware_awsim_sensor_kit_description autoware_sample_sensor_kit_description autoware_sample_vehicle_description autoware_core_localization autoware_ekf_localizer autoware_gyro_odometer autoware_localization_util autoware_ndt_scan_matcher autoware_pose_initializer autoware_stop_filter autoware_twist2accel autoware_core_map autoware_lanelet2_map_visualizer autoware_map_height_fitter autoware_map_loader autoware_map_projection_loader autoware_core_perception autoware_euclidean_cluster_object_detector autoware_ground_filter autoware_perception_objects_converter autoware_core_planning autoware_mission_planner autoware_objects_of_interest_marker_interface autoware_path_generator autoware_planning_factor_interface autoware_planning_topic_converter autoware_route_handler autoware_velocity_smoother autoware_behavior_velocity_planner autoware_behavior_velocity_planner_common autoware_behavior_velocity_stop_line_module autoware_motion_velocity_obstacle_stop_module autoware_motion_velocity_planner autoware_motion_velocity_planner_common autoware_core_sensing autoware_crop_box_filter autoware_downsample_filters autoware_gnss_poser autoware_vehicle_velocity_converter autoware_planning_test_manager autoware_pyplot autoware_test_node autoware_test_utils autoware_testing autoware_core_vehicle

ROS Distro
humble

Package Summary

Version 1.9.0
License Apache License 2.0
Build type AMENT_CMAKE
Use RECOMMENDED

Repository Summary

Checkout URI https://github.com/autowarefoundation/autoware_core.git
VCS Type git
VCS Version main
Last Updated 2026-07-03
Dev Status DEVELOPED
Released RELEASED
Contributing Help Wanted (-)
Good First Issues (-)
Pull Requests to Review (-)

Package Description

The autoware_vehicle_info_utils package

Maintainers

  • Taiki Tanaka
  • Tomoya Kimura
  • Shumpei Wakabayashi
  • Mamoru Sobue
  • Jian Kang

Authors

  • Yamato ANDO

Vehicle Info Util

Purpose

This package is to get vehicle info parameters.

Description

In here, you can check the vehicle dimensions with more detail. The current format supports only the Ackermann model. This file defines the model assumed in autoware path planning, control, etc. and does not represent the exact physical model. If a model other than the Ackermann model is used, it is assumed that a vehicle interface will be designed to change the control output for the model.

Versioning Policy

We have implemented a versioning system for the vehicle_info.param.yaml file to ensure clarity and consistency in file format across different versions of Autoware and its external applications. Please see discussion for the details.

How to Operate

  • The current file format is set as an unversioned base version (version: field is commented out).
  • For the next update involving changes (such as additions, deletions, or modifications):
    • Uncomment and update the version line at the beginning of the file.
    • Initiate versioning by assigning a version number, starting from 0.1.0. Follow the semantic versioning format (MAJOR.MINOR.PATCH).
    • Update this Readme.md too.
  • For subsequent updates, continue incrementing the version number in accordance with the changes made.
    • Discuss how to increment version depending on the amount of changes made to the file.
/**:
  ros__parameters:
    # version: 0.1.0 # Uncomment and update this line for future format changes.
    wheel_radius: 0.383
    ...

Why Versioning?

  • Consistency Across Updates: Implementing version control will allow accurate tracking of changes over time and changes in vehicle information parameters.
  • Clarity for External Applications: External applications that depend on vehicle_info.param.yaml need to reference the correct file version for optimal compatibility and functionality.
  • Simplified Management for Customized Branches: Assigning versions directly to the vehicle_info.param.yaml file simplifies management compared to maintaining separate versions for multiple customized Autoware branches. This approach streamlines version tracking and reduces complexity.

Scripts

Minimum turning radius

$ ros2 run autoware_vehicle_info_utils min_turning_radius_calculator.py
yaml path is /home/autoware/pilot-auto/install/autoware_vehicle_info_utils/share/autoware_vehicle_info_utils/config/vehicle_info.param.yaml
Minimum turning radius is 3.253042620027102 [m] for rear, 4.253220695862465 [m] for front.

You can designate yaml file with -y option as follows.

ros2 run autoware_vehicle_info_utils min_turning_radius_calculator.py -y <path-to-yaml>

Assumptions / Known limits

TBD.

CHANGELOG

Changelog for package autoware_vehicle_info_utils

1.1.0 (2025-05-01)

  • refactor(autoware_vehicle_info_utils): rewrite using modern C++ without API breakage (#343)
  • Contributors: Yutaka Kondo

1.9.0 (2026-06-24)

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

  • test(autoware_vehicle_info_utils): cover pure paths and reuse get_or_declare_parameter (#1105)

    * test(autoware_vehicle_info_utils): cover pure paths and reuse get_or_declare_parameter Add no-ROS unit tests for the pure VehicleInfo helpers that were previously untested: createVehicleInfo's wheel_base/max_steer clamping and has_non_positive_values branches, calcMaxMinDimension's two branches, extendVehicleInfo's margin distribution, the full 5-margin createFootprint overload (asymmetric margins plus center_at_base_link, asserting all seven ring points), and calcCurvatureFromSteerAngle's NaN guard. These run directly against the free functions / VehicleInfo methods without rclcpp. Replace the file-local getParameter<T> helper in VehicleInfoUtils with autoware_utils_rclcpp::get_or_declare_parameter<T>, which has identical has_parameter/get/declare semantics, and add the autoware_utils_rclcpp dependency. The throwing behavior on a parameter type mismatch is preserved (declare_parameter still throws); only the redundant local RCLCPP_ERROR log line on that path is dropped. No public API change. Refs: autowarefoundation/autoware_core#1096

    * test(autoware_vehicle_info_utils): de-tautologize vehicle_info test oracles (#79) Replace expected values that mirrored the implementation's formula or were read back from the output fields under test with independently hand-computed concrete literals (or stdlib-only computations in the std::hypot style). This makes the assertions verify the calculation instead of re-deriving the same potentially-wrong value. Refs: autowarefoundation/autoware_core#1096

    * test(autoware_vehicle_info_utils): use independent oracles for derived-value asserts (#86) Replace test expected values that mirrored the implementation's own formulas with concrete, independently hand-computed literals so the assertions can no longer pass on a wrong production calculation.

    - extendVehicleInfo: assert hardcoded 4.4 / 2.4 / 1.2 instead of reconstructing 'length + margin' / 'base2back + margin / 2'.

    - calcMaxMinDimension branch guards: drop the ASSERTs that recomputed base2front from the output fields; the branch is fixed by the test-chosen inputs and documented in comments. std::hypot-style expected values (inputs picked by the test, stdlib as the only shared dependency) and the existing hardcoded literals are kept. No production code changed. Refs: autowarefoundation/autoware_core#1096 ---------

  • feat(vehicle_info_utils): adjust [VehicleInfo]{.title-ref} to cover [VehicleShape]{.title-ref} (#1083)

    • add function to help replacing VehicleShape

    * remove defaulted function ---------Co-authored-by: Junya Sasaki <<j2sasaki1990@gmail.com>>

  • feat(autoware_vehicle_info_utils): add base_pose to createFootprint (#1072)

  • Contributors: Sarun MUKDAPITAK, Yutaka Kondo, github-actions

1.8.0 (2026-05-01)

  • Merge remote-tracking branch 'origin/main' into tmp/bot/bump_version_base
  • refactor(autoware_core): add USE_SCOPED_HEADER_INSTALL_DIR to common and testing packages (#967) Co-authored-by: github-actions <<github-actions@github.com>> Co-authored-by: Junya Sasaki <<j2sasaki1990@gmail.com>>
  • Contributors: Vishal Chauhan, github-actions

1.7.0 (2026-02-14)

1.6.0 (2025-12-30)

  • Merge remote-tracking branch 'origin/main' into tmp/bot/bump_version_base
  • docs: fix broken links (#779)

File truncated at 100 lines see the full file

Launch files

No launch files found

Messages

No message files found.

Services

No service files found

Plugins

No plugins found.

Recent questions tagged autoware_vehicle_info_utils at Robotics Stack Exchange

No version for distro lunar showing humble. Known supported distros are highlighted in the buttons above.
Package symbol

autoware_vehicle_info_utils package from autoware_core repo

autoware_adapi_adaptors autoware_adapi_specs autoware_core_api autoware_default_adapi autoware_core autoware_agnocast_wrapper autoware_component_interface_specs autoware_geography_utils autoware_global_parameter_loader autoware_interpolation autoware_kalman_filter autoware_lanelet2_utils autoware_marker_utils autoware_motion_utils autoware_node autoware_object_recognition_utils autoware_osqp_interface autoware_point_types autoware_qos_utils autoware_qp_interface autoware_signal_processing autoware_trajectory autoware_vehicle_info_utils autoware_command_gate autoware_core_control autoware_simple_pure_pursuit autoware_awsim_sensor_kit_description autoware_sample_sensor_kit_description autoware_sample_vehicle_description autoware_core_localization autoware_ekf_localizer autoware_gyro_odometer autoware_localization_util autoware_ndt_scan_matcher autoware_pose_initializer autoware_stop_filter autoware_twist2accel autoware_core_map autoware_lanelet2_map_visualizer autoware_map_height_fitter autoware_map_loader autoware_map_projection_loader autoware_core_perception autoware_euclidean_cluster_object_detector autoware_ground_filter autoware_perception_objects_converter autoware_core_planning autoware_mission_planner autoware_objects_of_interest_marker_interface autoware_path_generator autoware_planning_factor_interface autoware_planning_topic_converter autoware_route_handler autoware_velocity_smoother autoware_behavior_velocity_planner autoware_behavior_velocity_planner_common autoware_behavior_velocity_stop_line_module autoware_motion_velocity_obstacle_stop_module autoware_motion_velocity_planner autoware_motion_velocity_planner_common autoware_core_sensing autoware_crop_box_filter autoware_downsample_filters autoware_gnss_poser autoware_vehicle_velocity_converter autoware_planning_test_manager autoware_pyplot autoware_test_node autoware_test_utils autoware_testing autoware_core_vehicle

ROS Distro
humble

Package Summary

Version 1.9.0
License Apache License 2.0
Build type AMENT_CMAKE
Use RECOMMENDED

Repository Summary

Checkout URI https://github.com/autowarefoundation/autoware_core.git
VCS Type git
VCS Version main
Last Updated 2026-07-03
Dev Status DEVELOPED
Released RELEASED
Contributing Help Wanted (-)
Good First Issues (-)
Pull Requests to Review (-)

Package Description

The autoware_vehicle_info_utils package

Maintainers

  • Taiki Tanaka
  • Tomoya Kimura
  • Shumpei Wakabayashi
  • Mamoru Sobue
  • Jian Kang

Authors

  • Yamato ANDO

Vehicle Info Util

Purpose

This package is to get vehicle info parameters.

Description

In here, you can check the vehicle dimensions with more detail. The current format supports only the Ackermann model. This file defines the model assumed in autoware path planning, control, etc. and does not represent the exact physical model. If a model other than the Ackermann model is used, it is assumed that a vehicle interface will be designed to change the control output for the model.

Versioning Policy

We have implemented a versioning system for the vehicle_info.param.yaml file to ensure clarity and consistency in file format across different versions of Autoware and its external applications. Please see discussion for the details.

How to Operate

  • The current file format is set as an unversioned base version (version: field is commented out).
  • For the next update involving changes (such as additions, deletions, or modifications):
    • Uncomment and update the version line at the beginning of the file.
    • Initiate versioning by assigning a version number, starting from 0.1.0. Follow the semantic versioning format (MAJOR.MINOR.PATCH).
    • Update this Readme.md too.
  • For subsequent updates, continue incrementing the version number in accordance with the changes made.
    • Discuss how to increment version depending on the amount of changes made to the file.
/**:
  ros__parameters:
    # version: 0.1.0 # Uncomment and update this line for future format changes.
    wheel_radius: 0.383
    ...

Why Versioning?

  • Consistency Across Updates: Implementing version control will allow accurate tracking of changes over time and changes in vehicle information parameters.
  • Clarity for External Applications: External applications that depend on vehicle_info.param.yaml need to reference the correct file version for optimal compatibility and functionality.
  • Simplified Management for Customized Branches: Assigning versions directly to the vehicle_info.param.yaml file simplifies management compared to maintaining separate versions for multiple customized Autoware branches. This approach streamlines version tracking and reduces complexity.

Scripts

Minimum turning radius

$ ros2 run autoware_vehicle_info_utils min_turning_radius_calculator.py
yaml path is /home/autoware/pilot-auto/install/autoware_vehicle_info_utils/share/autoware_vehicle_info_utils/config/vehicle_info.param.yaml
Minimum turning radius is 3.253042620027102 [m] for rear, 4.253220695862465 [m] for front.

You can designate yaml file with -y option as follows.

ros2 run autoware_vehicle_info_utils min_turning_radius_calculator.py -y <path-to-yaml>

Assumptions / Known limits

TBD.

CHANGELOG

Changelog for package autoware_vehicle_info_utils

1.1.0 (2025-05-01)

  • refactor(autoware_vehicle_info_utils): rewrite using modern C++ without API breakage (#343)
  • Contributors: Yutaka Kondo

1.9.0 (2026-06-24)

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

  • test(autoware_vehicle_info_utils): cover pure paths and reuse get_or_declare_parameter (#1105)

    * test(autoware_vehicle_info_utils): cover pure paths and reuse get_or_declare_parameter Add no-ROS unit tests for the pure VehicleInfo helpers that were previously untested: createVehicleInfo's wheel_base/max_steer clamping and has_non_positive_values branches, calcMaxMinDimension's two branches, extendVehicleInfo's margin distribution, the full 5-margin createFootprint overload (asymmetric margins plus center_at_base_link, asserting all seven ring points), and calcCurvatureFromSteerAngle's NaN guard. These run directly against the free functions / VehicleInfo methods without rclcpp. Replace the file-local getParameter<T> helper in VehicleInfoUtils with autoware_utils_rclcpp::get_or_declare_parameter<T>, which has identical has_parameter/get/declare semantics, and add the autoware_utils_rclcpp dependency. The throwing behavior on a parameter type mismatch is preserved (declare_parameter still throws); only the redundant local RCLCPP_ERROR log line on that path is dropped. No public API change. Refs: autowarefoundation/autoware_core#1096

    * test(autoware_vehicle_info_utils): de-tautologize vehicle_info test oracles (#79) Replace expected values that mirrored the implementation's formula or were read back from the output fields under test with independently hand-computed concrete literals (or stdlib-only computations in the std::hypot style). This makes the assertions verify the calculation instead of re-deriving the same potentially-wrong value. Refs: autowarefoundation/autoware_core#1096

    * test(autoware_vehicle_info_utils): use independent oracles for derived-value asserts (#86) Replace test expected values that mirrored the implementation's own formulas with concrete, independently hand-computed literals so the assertions can no longer pass on a wrong production calculation.

    - extendVehicleInfo: assert hardcoded 4.4 / 2.4 / 1.2 instead of reconstructing 'length + margin' / 'base2back + margin / 2'.

    - calcMaxMinDimension branch guards: drop the ASSERTs that recomputed base2front from the output fields; the branch is fixed by the test-chosen inputs and documented in comments. std::hypot-style expected values (inputs picked by the test, stdlib as the only shared dependency) and the existing hardcoded literals are kept. No production code changed. Refs: autowarefoundation/autoware_core#1096 ---------

  • feat(vehicle_info_utils): adjust [VehicleInfo]{.title-ref} to cover [VehicleShape]{.title-ref} (#1083)

    • add function to help replacing VehicleShape

    * remove defaulted function ---------Co-authored-by: Junya Sasaki <<j2sasaki1990@gmail.com>>

  • feat(autoware_vehicle_info_utils): add base_pose to createFootprint (#1072)

  • Contributors: Sarun MUKDAPITAK, Yutaka Kondo, github-actions

1.8.0 (2026-05-01)

  • Merge remote-tracking branch 'origin/main' into tmp/bot/bump_version_base
  • refactor(autoware_core): add USE_SCOPED_HEADER_INSTALL_DIR to common and testing packages (#967) Co-authored-by: github-actions <<github-actions@github.com>> Co-authored-by: Junya Sasaki <<j2sasaki1990@gmail.com>>
  • Contributors: Vishal Chauhan, github-actions

1.7.0 (2026-02-14)

1.6.0 (2025-12-30)

  • Merge remote-tracking branch 'origin/main' into tmp/bot/bump_version_base
  • docs: fix broken links (#779)

File truncated at 100 lines see the full file

Launch files

No launch files found

Messages

No message files found.

Services

No service files found

Plugins

No plugins found.

Recent questions tagged autoware_vehicle_info_utils at Robotics Stack Exchange

No version for distro jade showing humble. Known supported distros are highlighted in the buttons above.
Package symbol

autoware_vehicle_info_utils package from autoware_core repo

autoware_adapi_adaptors autoware_adapi_specs autoware_core_api autoware_default_adapi autoware_core autoware_agnocast_wrapper autoware_component_interface_specs autoware_geography_utils autoware_global_parameter_loader autoware_interpolation autoware_kalman_filter autoware_lanelet2_utils autoware_marker_utils autoware_motion_utils autoware_node autoware_object_recognition_utils autoware_osqp_interface autoware_point_types autoware_qos_utils autoware_qp_interface autoware_signal_processing autoware_trajectory autoware_vehicle_info_utils autoware_command_gate autoware_core_control autoware_simple_pure_pursuit autoware_awsim_sensor_kit_description autoware_sample_sensor_kit_description autoware_sample_vehicle_description autoware_core_localization autoware_ekf_localizer autoware_gyro_odometer autoware_localization_util autoware_ndt_scan_matcher autoware_pose_initializer autoware_stop_filter autoware_twist2accel autoware_core_map autoware_lanelet2_map_visualizer autoware_map_height_fitter autoware_map_loader autoware_map_projection_loader autoware_core_perception autoware_euclidean_cluster_object_detector autoware_ground_filter autoware_perception_objects_converter autoware_core_planning autoware_mission_planner autoware_objects_of_interest_marker_interface autoware_path_generator autoware_planning_factor_interface autoware_planning_topic_converter autoware_route_handler autoware_velocity_smoother autoware_behavior_velocity_planner autoware_behavior_velocity_planner_common autoware_behavior_velocity_stop_line_module autoware_motion_velocity_obstacle_stop_module autoware_motion_velocity_planner autoware_motion_velocity_planner_common autoware_core_sensing autoware_crop_box_filter autoware_downsample_filters autoware_gnss_poser autoware_vehicle_velocity_converter autoware_planning_test_manager autoware_pyplot autoware_test_node autoware_test_utils autoware_testing autoware_core_vehicle

ROS Distro
humble

Package Summary

Version 1.9.0
License Apache License 2.0
Build type AMENT_CMAKE
Use RECOMMENDED

Repository Summary

Checkout URI https://github.com/autowarefoundation/autoware_core.git
VCS Type git
VCS Version main
Last Updated 2026-07-03
Dev Status DEVELOPED
Released RELEASED
Contributing Help Wanted (-)
Good First Issues (-)
Pull Requests to Review (-)

Package Description

The autoware_vehicle_info_utils package

Maintainers

  • Taiki Tanaka
  • Tomoya Kimura
  • Shumpei Wakabayashi
  • Mamoru Sobue
  • Jian Kang

Authors

  • Yamato ANDO

Vehicle Info Util

Purpose

This package is to get vehicle info parameters.

Description

In here, you can check the vehicle dimensions with more detail. The current format supports only the Ackermann model. This file defines the model assumed in autoware path planning, control, etc. and does not represent the exact physical model. If a model other than the Ackermann model is used, it is assumed that a vehicle interface will be designed to change the control output for the model.

Versioning Policy

We have implemented a versioning system for the vehicle_info.param.yaml file to ensure clarity and consistency in file format across different versions of Autoware and its external applications. Please see discussion for the details.

How to Operate

  • The current file format is set as an unversioned base version (version: field is commented out).
  • For the next update involving changes (such as additions, deletions, or modifications):
    • Uncomment and update the version line at the beginning of the file.
    • Initiate versioning by assigning a version number, starting from 0.1.0. Follow the semantic versioning format (MAJOR.MINOR.PATCH).
    • Update this Readme.md too.
  • For subsequent updates, continue incrementing the version number in accordance with the changes made.
    • Discuss how to increment version depending on the amount of changes made to the file.
/**:
  ros__parameters:
    # version: 0.1.0 # Uncomment and update this line for future format changes.
    wheel_radius: 0.383
    ...

Why Versioning?

  • Consistency Across Updates: Implementing version control will allow accurate tracking of changes over time and changes in vehicle information parameters.
  • Clarity for External Applications: External applications that depend on vehicle_info.param.yaml need to reference the correct file version for optimal compatibility and functionality.
  • Simplified Management for Customized Branches: Assigning versions directly to the vehicle_info.param.yaml file simplifies management compared to maintaining separate versions for multiple customized Autoware branches. This approach streamlines version tracking and reduces complexity.

Scripts

Minimum turning radius

$ ros2 run autoware_vehicle_info_utils min_turning_radius_calculator.py
yaml path is /home/autoware/pilot-auto/install/autoware_vehicle_info_utils/share/autoware_vehicle_info_utils/config/vehicle_info.param.yaml
Minimum turning radius is 3.253042620027102 [m] for rear, 4.253220695862465 [m] for front.

You can designate yaml file with -y option as follows.

ros2 run autoware_vehicle_info_utils min_turning_radius_calculator.py -y <path-to-yaml>

Assumptions / Known limits

TBD.

CHANGELOG

Changelog for package autoware_vehicle_info_utils

1.1.0 (2025-05-01)

  • refactor(autoware_vehicle_info_utils): rewrite using modern C++ without API breakage (#343)
  • Contributors: Yutaka Kondo

1.9.0 (2026-06-24)

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

  • test(autoware_vehicle_info_utils): cover pure paths and reuse get_or_declare_parameter (#1105)

    * test(autoware_vehicle_info_utils): cover pure paths and reuse get_or_declare_parameter Add no-ROS unit tests for the pure VehicleInfo helpers that were previously untested: createVehicleInfo's wheel_base/max_steer clamping and has_non_positive_values branches, calcMaxMinDimension's two branches, extendVehicleInfo's margin distribution, the full 5-margin createFootprint overload (asymmetric margins plus center_at_base_link, asserting all seven ring points), and calcCurvatureFromSteerAngle's NaN guard. These run directly against the free functions / VehicleInfo methods without rclcpp. Replace the file-local getParameter<T> helper in VehicleInfoUtils with autoware_utils_rclcpp::get_or_declare_parameter<T>, which has identical has_parameter/get/declare semantics, and add the autoware_utils_rclcpp dependency. The throwing behavior on a parameter type mismatch is preserved (declare_parameter still throws); only the redundant local RCLCPP_ERROR log line on that path is dropped. No public API change. Refs: autowarefoundation/autoware_core#1096

    * test(autoware_vehicle_info_utils): de-tautologize vehicle_info test oracles (#79) Replace expected values that mirrored the implementation's formula or were read back from the output fields under test with independently hand-computed concrete literals (or stdlib-only computations in the std::hypot style). This makes the assertions verify the calculation instead of re-deriving the same potentially-wrong value. Refs: autowarefoundation/autoware_core#1096

    * test(autoware_vehicle_info_utils): use independent oracles for derived-value asserts (#86) Replace test expected values that mirrored the implementation's own formulas with concrete, independently hand-computed literals so the assertions can no longer pass on a wrong production calculation.

    - extendVehicleInfo: assert hardcoded 4.4 / 2.4 / 1.2 instead of reconstructing 'length + margin' / 'base2back + margin / 2'.

    - calcMaxMinDimension branch guards: drop the ASSERTs that recomputed base2front from the output fields; the branch is fixed by the test-chosen inputs and documented in comments. std::hypot-style expected values (inputs picked by the test, stdlib as the only shared dependency) and the existing hardcoded literals are kept. No production code changed. Refs: autowarefoundation/autoware_core#1096 ---------

  • feat(vehicle_info_utils): adjust [VehicleInfo]{.title-ref} to cover [VehicleShape]{.title-ref} (#1083)

    • add function to help replacing VehicleShape

    * remove defaulted function ---------Co-authored-by: Junya Sasaki <<j2sasaki1990@gmail.com>>

  • feat(autoware_vehicle_info_utils): add base_pose to createFootprint (#1072)

  • Contributors: Sarun MUKDAPITAK, Yutaka Kondo, github-actions

1.8.0 (2026-05-01)

  • Merge remote-tracking branch 'origin/main' into tmp/bot/bump_version_base
  • refactor(autoware_core): add USE_SCOPED_HEADER_INSTALL_DIR to common and testing packages (#967) Co-authored-by: github-actions <<github-actions@github.com>> Co-authored-by: Junya Sasaki <<j2sasaki1990@gmail.com>>
  • Contributors: Vishal Chauhan, github-actions

1.7.0 (2026-02-14)

1.6.0 (2025-12-30)

  • Merge remote-tracking branch 'origin/main' into tmp/bot/bump_version_base
  • docs: fix broken links (#779)

File truncated at 100 lines see the full file

Launch files

No launch files found

Messages

No message files found.

Services

No service files found

Plugins

No plugins found.

Recent questions tagged autoware_vehicle_info_utils at Robotics Stack Exchange

No version for distro indigo showing humble. Known supported distros are highlighted in the buttons above.
Package symbol

autoware_vehicle_info_utils package from autoware_core repo

autoware_adapi_adaptors autoware_adapi_specs autoware_core_api autoware_default_adapi autoware_core autoware_agnocast_wrapper autoware_component_interface_specs autoware_geography_utils autoware_global_parameter_loader autoware_interpolation autoware_kalman_filter autoware_lanelet2_utils autoware_marker_utils autoware_motion_utils autoware_node autoware_object_recognition_utils autoware_osqp_interface autoware_point_types autoware_qos_utils autoware_qp_interface autoware_signal_processing autoware_trajectory autoware_vehicle_info_utils autoware_command_gate autoware_core_control autoware_simple_pure_pursuit autoware_awsim_sensor_kit_description autoware_sample_sensor_kit_description autoware_sample_vehicle_description autoware_core_localization autoware_ekf_localizer autoware_gyro_odometer autoware_localization_util autoware_ndt_scan_matcher autoware_pose_initializer autoware_stop_filter autoware_twist2accel autoware_core_map autoware_lanelet2_map_visualizer autoware_map_height_fitter autoware_map_loader autoware_map_projection_loader autoware_core_perception autoware_euclidean_cluster_object_detector autoware_ground_filter autoware_perception_objects_converter autoware_core_planning autoware_mission_planner autoware_objects_of_interest_marker_interface autoware_path_generator autoware_planning_factor_interface autoware_planning_topic_converter autoware_route_handler autoware_velocity_smoother autoware_behavior_velocity_planner autoware_behavior_velocity_planner_common autoware_behavior_velocity_stop_line_module autoware_motion_velocity_obstacle_stop_module autoware_motion_velocity_planner autoware_motion_velocity_planner_common autoware_core_sensing autoware_crop_box_filter autoware_downsample_filters autoware_gnss_poser autoware_vehicle_velocity_converter autoware_planning_test_manager autoware_pyplot autoware_test_node autoware_test_utils autoware_testing autoware_core_vehicle

ROS Distro
humble

Package Summary

Version 1.9.0
License Apache License 2.0
Build type AMENT_CMAKE
Use RECOMMENDED

Repository Summary

Checkout URI https://github.com/autowarefoundation/autoware_core.git
VCS Type git
VCS Version main
Last Updated 2026-07-03
Dev Status DEVELOPED
Released RELEASED
Contributing Help Wanted (-)
Good First Issues (-)
Pull Requests to Review (-)

Package Description

The autoware_vehicle_info_utils package

Maintainers

  • Taiki Tanaka
  • Tomoya Kimura
  • Shumpei Wakabayashi
  • Mamoru Sobue
  • Jian Kang

Authors

  • Yamato ANDO

Vehicle Info Util

Purpose

This package is to get vehicle info parameters.

Description

In here, you can check the vehicle dimensions with more detail. The current format supports only the Ackermann model. This file defines the model assumed in autoware path planning, control, etc. and does not represent the exact physical model. If a model other than the Ackermann model is used, it is assumed that a vehicle interface will be designed to change the control output for the model.

Versioning Policy

We have implemented a versioning system for the vehicle_info.param.yaml file to ensure clarity and consistency in file format across different versions of Autoware and its external applications. Please see discussion for the details.

How to Operate

  • The current file format is set as an unversioned base version (version: field is commented out).
  • For the next update involving changes (such as additions, deletions, or modifications):
    • Uncomment and update the version line at the beginning of the file.
    • Initiate versioning by assigning a version number, starting from 0.1.0. Follow the semantic versioning format (MAJOR.MINOR.PATCH).
    • Update this Readme.md too.
  • For subsequent updates, continue incrementing the version number in accordance with the changes made.
    • Discuss how to increment version depending on the amount of changes made to the file.
/**:
  ros__parameters:
    # version: 0.1.0 # Uncomment and update this line for future format changes.
    wheel_radius: 0.383
    ...

Why Versioning?

  • Consistency Across Updates: Implementing version control will allow accurate tracking of changes over time and changes in vehicle information parameters.
  • Clarity for External Applications: External applications that depend on vehicle_info.param.yaml need to reference the correct file version for optimal compatibility and functionality.
  • Simplified Management for Customized Branches: Assigning versions directly to the vehicle_info.param.yaml file simplifies management compared to maintaining separate versions for multiple customized Autoware branches. This approach streamlines version tracking and reduces complexity.

Scripts

Minimum turning radius

$ ros2 run autoware_vehicle_info_utils min_turning_radius_calculator.py
yaml path is /home/autoware/pilot-auto/install/autoware_vehicle_info_utils/share/autoware_vehicle_info_utils/config/vehicle_info.param.yaml
Minimum turning radius is 3.253042620027102 [m] for rear, 4.253220695862465 [m] for front.

You can designate yaml file with -y option as follows.

ros2 run autoware_vehicle_info_utils min_turning_radius_calculator.py -y <path-to-yaml>

Assumptions / Known limits

TBD.

CHANGELOG

Changelog for package autoware_vehicle_info_utils

1.1.0 (2025-05-01)

  • refactor(autoware_vehicle_info_utils): rewrite using modern C++ without API breakage (#343)
  • Contributors: Yutaka Kondo

1.9.0 (2026-06-24)

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

  • test(autoware_vehicle_info_utils): cover pure paths and reuse get_or_declare_parameter (#1105)

    * test(autoware_vehicle_info_utils): cover pure paths and reuse get_or_declare_parameter Add no-ROS unit tests for the pure VehicleInfo helpers that were previously untested: createVehicleInfo's wheel_base/max_steer clamping and has_non_positive_values branches, calcMaxMinDimension's two branches, extendVehicleInfo's margin distribution, the full 5-margin createFootprint overload (asymmetric margins plus center_at_base_link, asserting all seven ring points), and calcCurvatureFromSteerAngle's NaN guard. These run directly against the free functions / VehicleInfo methods without rclcpp. Replace the file-local getParameter<T> helper in VehicleInfoUtils with autoware_utils_rclcpp::get_or_declare_parameter<T>, which has identical has_parameter/get/declare semantics, and add the autoware_utils_rclcpp dependency. The throwing behavior on a parameter type mismatch is preserved (declare_parameter still throws); only the redundant local RCLCPP_ERROR log line on that path is dropped. No public API change. Refs: autowarefoundation/autoware_core#1096

    * test(autoware_vehicle_info_utils): de-tautologize vehicle_info test oracles (#79) Replace expected values that mirrored the implementation's formula or were read back from the output fields under test with independently hand-computed concrete literals (or stdlib-only computations in the std::hypot style). This makes the assertions verify the calculation instead of re-deriving the same potentially-wrong value. Refs: autowarefoundation/autoware_core#1096

    * test(autoware_vehicle_info_utils): use independent oracles for derived-value asserts (#86) Replace test expected values that mirrored the implementation's own formulas with concrete, independently hand-computed literals so the assertions can no longer pass on a wrong production calculation.

    - extendVehicleInfo: assert hardcoded 4.4 / 2.4 / 1.2 instead of reconstructing 'length + margin' / 'base2back + margin / 2'.

    - calcMaxMinDimension branch guards: drop the ASSERTs that recomputed base2front from the output fields; the branch is fixed by the test-chosen inputs and documented in comments. std::hypot-style expected values (inputs picked by the test, stdlib as the only shared dependency) and the existing hardcoded literals are kept. No production code changed. Refs: autowarefoundation/autoware_core#1096 ---------

  • feat(vehicle_info_utils): adjust [VehicleInfo]{.title-ref} to cover [VehicleShape]{.title-ref} (#1083)

    • add function to help replacing VehicleShape

    * remove defaulted function ---------Co-authored-by: Junya Sasaki <<j2sasaki1990@gmail.com>>

  • feat(autoware_vehicle_info_utils): add base_pose to createFootprint (#1072)

  • Contributors: Sarun MUKDAPITAK, Yutaka Kondo, github-actions

1.8.0 (2026-05-01)

  • Merge remote-tracking branch 'origin/main' into tmp/bot/bump_version_base
  • refactor(autoware_core): add USE_SCOPED_HEADER_INSTALL_DIR to common and testing packages (#967) Co-authored-by: github-actions <<github-actions@github.com>> Co-authored-by: Junya Sasaki <<j2sasaki1990@gmail.com>>
  • Contributors: Vishal Chauhan, github-actions

1.7.0 (2026-02-14)

1.6.0 (2025-12-30)

  • Merge remote-tracking branch 'origin/main' into tmp/bot/bump_version_base
  • docs: fix broken links (#779)

File truncated at 100 lines see the full file

Launch files

No launch files found

Messages

No message files found.

Services

No service files found

Plugins

No plugins found.

Recent questions tagged autoware_vehicle_info_utils at Robotics Stack Exchange

No version for distro hydro showing humble. Known supported distros are highlighted in the buttons above.
Package symbol

autoware_vehicle_info_utils package from autoware_core repo

autoware_adapi_adaptors autoware_adapi_specs autoware_core_api autoware_default_adapi autoware_core autoware_agnocast_wrapper autoware_component_interface_specs autoware_geography_utils autoware_global_parameter_loader autoware_interpolation autoware_kalman_filter autoware_lanelet2_utils autoware_marker_utils autoware_motion_utils autoware_node autoware_object_recognition_utils autoware_osqp_interface autoware_point_types autoware_qos_utils autoware_qp_interface autoware_signal_processing autoware_trajectory autoware_vehicle_info_utils autoware_command_gate autoware_core_control autoware_simple_pure_pursuit autoware_awsim_sensor_kit_description autoware_sample_sensor_kit_description autoware_sample_vehicle_description autoware_core_localization autoware_ekf_localizer autoware_gyro_odometer autoware_localization_util autoware_ndt_scan_matcher autoware_pose_initializer autoware_stop_filter autoware_twist2accel autoware_core_map autoware_lanelet2_map_visualizer autoware_map_height_fitter autoware_map_loader autoware_map_projection_loader autoware_core_perception autoware_euclidean_cluster_object_detector autoware_ground_filter autoware_perception_objects_converter autoware_core_planning autoware_mission_planner autoware_objects_of_interest_marker_interface autoware_path_generator autoware_planning_factor_interface autoware_planning_topic_converter autoware_route_handler autoware_velocity_smoother autoware_behavior_velocity_planner autoware_behavior_velocity_planner_common autoware_behavior_velocity_stop_line_module autoware_motion_velocity_obstacle_stop_module autoware_motion_velocity_planner autoware_motion_velocity_planner_common autoware_core_sensing autoware_crop_box_filter autoware_downsample_filters autoware_gnss_poser autoware_vehicle_velocity_converter autoware_planning_test_manager autoware_pyplot autoware_test_node autoware_test_utils autoware_testing autoware_core_vehicle

ROS Distro
humble

Package Summary

Version 1.9.0
License Apache License 2.0
Build type AMENT_CMAKE
Use RECOMMENDED

Repository Summary

Checkout URI https://github.com/autowarefoundation/autoware_core.git
VCS Type git
VCS Version main
Last Updated 2026-07-03
Dev Status DEVELOPED
Released RELEASED
Contributing Help Wanted (-)
Good First Issues (-)
Pull Requests to Review (-)

Package Description

The autoware_vehicle_info_utils package

Maintainers

  • Taiki Tanaka
  • Tomoya Kimura
  • Shumpei Wakabayashi
  • Mamoru Sobue
  • Jian Kang

Authors

  • Yamato ANDO

Vehicle Info Util

Purpose

This package is to get vehicle info parameters.

Description

In here, you can check the vehicle dimensions with more detail. The current format supports only the Ackermann model. This file defines the model assumed in autoware path planning, control, etc. and does not represent the exact physical model. If a model other than the Ackermann model is used, it is assumed that a vehicle interface will be designed to change the control output for the model.

Versioning Policy

We have implemented a versioning system for the vehicle_info.param.yaml file to ensure clarity and consistency in file format across different versions of Autoware and its external applications. Please see discussion for the details.

How to Operate

  • The current file format is set as an unversioned base version (version: field is commented out).
  • For the next update involving changes (such as additions, deletions, or modifications):
    • Uncomment and update the version line at the beginning of the file.
    • Initiate versioning by assigning a version number, starting from 0.1.0. Follow the semantic versioning format (MAJOR.MINOR.PATCH).
    • Update this Readme.md too.
  • For subsequent updates, continue incrementing the version number in accordance with the changes made.
    • Discuss how to increment version depending on the amount of changes made to the file.
/**:
  ros__parameters:
    # version: 0.1.0 # Uncomment and update this line for future format changes.
    wheel_radius: 0.383
    ...

Why Versioning?

  • Consistency Across Updates: Implementing version control will allow accurate tracking of changes over time and changes in vehicle information parameters.
  • Clarity for External Applications: External applications that depend on vehicle_info.param.yaml need to reference the correct file version for optimal compatibility and functionality.
  • Simplified Management for Customized Branches: Assigning versions directly to the vehicle_info.param.yaml file simplifies management compared to maintaining separate versions for multiple customized Autoware branches. This approach streamlines version tracking and reduces complexity.

Scripts

Minimum turning radius

$ ros2 run autoware_vehicle_info_utils min_turning_radius_calculator.py
yaml path is /home/autoware/pilot-auto/install/autoware_vehicle_info_utils/share/autoware_vehicle_info_utils/config/vehicle_info.param.yaml
Minimum turning radius is 3.253042620027102 [m] for rear, 4.253220695862465 [m] for front.

You can designate yaml file with -y option as follows.

ros2 run autoware_vehicle_info_utils min_turning_radius_calculator.py -y <path-to-yaml>

Assumptions / Known limits

TBD.

CHANGELOG

Changelog for package autoware_vehicle_info_utils

1.1.0 (2025-05-01)

  • refactor(autoware_vehicle_info_utils): rewrite using modern C++ without API breakage (#343)
  • Contributors: Yutaka Kondo

1.9.0 (2026-06-24)

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

  • test(autoware_vehicle_info_utils): cover pure paths and reuse get_or_declare_parameter (#1105)

    * test(autoware_vehicle_info_utils): cover pure paths and reuse get_or_declare_parameter Add no-ROS unit tests for the pure VehicleInfo helpers that were previously untested: createVehicleInfo's wheel_base/max_steer clamping and has_non_positive_values branches, calcMaxMinDimension's two branches, extendVehicleInfo's margin distribution, the full 5-margin createFootprint overload (asymmetric margins plus center_at_base_link, asserting all seven ring points), and calcCurvatureFromSteerAngle's NaN guard. These run directly against the free functions / VehicleInfo methods without rclcpp. Replace the file-local getParameter<T> helper in VehicleInfoUtils with autoware_utils_rclcpp::get_or_declare_parameter<T>, which has identical has_parameter/get/declare semantics, and add the autoware_utils_rclcpp dependency. The throwing behavior on a parameter type mismatch is preserved (declare_parameter still throws); only the redundant local RCLCPP_ERROR log line on that path is dropped. No public API change. Refs: autowarefoundation/autoware_core#1096

    * test(autoware_vehicle_info_utils): de-tautologize vehicle_info test oracles (#79) Replace expected values that mirrored the implementation's formula or were read back from the output fields under test with independently hand-computed concrete literals (or stdlib-only computations in the std::hypot style). This makes the assertions verify the calculation instead of re-deriving the same potentially-wrong value. Refs: autowarefoundation/autoware_core#1096

    * test(autoware_vehicle_info_utils): use independent oracles for derived-value asserts (#86) Replace test expected values that mirrored the implementation's own formulas with concrete, independently hand-computed literals so the assertions can no longer pass on a wrong production calculation.

    - extendVehicleInfo: assert hardcoded 4.4 / 2.4 / 1.2 instead of reconstructing 'length + margin' / 'base2back + margin / 2'.

    - calcMaxMinDimension branch guards: drop the ASSERTs that recomputed base2front from the output fields; the branch is fixed by the test-chosen inputs and documented in comments. std::hypot-style expected values (inputs picked by the test, stdlib as the only shared dependency) and the existing hardcoded literals are kept. No production code changed. Refs: autowarefoundation/autoware_core#1096 ---------

  • feat(vehicle_info_utils): adjust [VehicleInfo]{.title-ref} to cover [VehicleShape]{.title-ref} (#1083)

    • add function to help replacing VehicleShape

    * remove defaulted function ---------Co-authored-by: Junya Sasaki <<j2sasaki1990@gmail.com>>

  • feat(autoware_vehicle_info_utils): add base_pose to createFootprint (#1072)

  • Contributors: Sarun MUKDAPITAK, Yutaka Kondo, github-actions

1.8.0 (2026-05-01)

  • Merge remote-tracking branch 'origin/main' into tmp/bot/bump_version_base
  • refactor(autoware_core): add USE_SCOPED_HEADER_INSTALL_DIR to common and testing packages (#967) Co-authored-by: github-actions <<github-actions@github.com>> Co-authored-by: Junya Sasaki <<j2sasaki1990@gmail.com>>
  • Contributors: Vishal Chauhan, github-actions

1.7.0 (2026-02-14)

1.6.0 (2025-12-30)

  • Merge remote-tracking branch 'origin/main' into tmp/bot/bump_version_base
  • docs: fix broken links (#779)

File truncated at 100 lines see the full file

Launch files

No launch files found

Messages

No message files found.

Services

No service files found

Plugins

No plugins found.

Recent questions tagged autoware_vehicle_info_utils at Robotics Stack Exchange

No version for distro kinetic showing humble. Known supported distros are highlighted in the buttons above.
Package symbol

autoware_vehicle_info_utils package from autoware_core repo

autoware_adapi_adaptors autoware_adapi_specs autoware_core_api autoware_default_adapi autoware_core autoware_agnocast_wrapper autoware_component_interface_specs autoware_geography_utils autoware_global_parameter_loader autoware_interpolation autoware_kalman_filter autoware_lanelet2_utils autoware_marker_utils autoware_motion_utils autoware_node autoware_object_recognition_utils autoware_osqp_interface autoware_point_types autoware_qos_utils autoware_qp_interface autoware_signal_processing autoware_trajectory autoware_vehicle_info_utils autoware_command_gate autoware_core_control autoware_simple_pure_pursuit autoware_awsim_sensor_kit_description autoware_sample_sensor_kit_description autoware_sample_vehicle_description autoware_core_localization autoware_ekf_localizer autoware_gyro_odometer autoware_localization_util autoware_ndt_scan_matcher autoware_pose_initializer autoware_stop_filter autoware_twist2accel autoware_core_map autoware_lanelet2_map_visualizer autoware_map_height_fitter autoware_map_loader autoware_map_projection_loader autoware_core_perception autoware_euclidean_cluster_object_detector autoware_ground_filter autoware_perception_objects_converter autoware_core_planning autoware_mission_planner autoware_objects_of_interest_marker_interface autoware_path_generator autoware_planning_factor_interface autoware_planning_topic_converter autoware_route_handler autoware_velocity_smoother autoware_behavior_velocity_planner autoware_behavior_velocity_planner_common autoware_behavior_velocity_stop_line_module autoware_motion_velocity_obstacle_stop_module autoware_motion_velocity_planner autoware_motion_velocity_planner_common autoware_core_sensing autoware_crop_box_filter autoware_downsample_filters autoware_gnss_poser autoware_vehicle_velocity_converter autoware_planning_test_manager autoware_pyplot autoware_test_node autoware_test_utils autoware_testing autoware_core_vehicle

ROS Distro
humble

Package Summary

Version 1.9.0
License Apache License 2.0
Build type AMENT_CMAKE
Use RECOMMENDED

Repository Summary

Checkout URI https://github.com/autowarefoundation/autoware_core.git
VCS Type git
VCS Version main
Last Updated 2026-07-03
Dev Status DEVELOPED
Released RELEASED
Contributing Help Wanted (-)
Good First Issues (-)
Pull Requests to Review (-)

Package Description

The autoware_vehicle_info_utils package

Maintainers

  • Taiki Tanaka
  • Tomoya Kimura
  • Shumpei Wakabayashi
  • Mamoru Sobue
  • Jian Kang

Authors

  • Yamato ANDO

Vehicle Info Util

Purpose

This package is to get vehicle info parameters.

Description

In here, you can check the vehicle dimensions with more detail. The current format supports only the Ackermann model. This file defines the model assumed in autoware path planning, control, etc. and does not represent the exact physical model. If a model other than the Ackermann model is used, it is assumed that a vehicle interface will be designed to change the control output for the model.

Versioning Policy

We have implemented a versioning system for the vehicle_info.param.yaml file to ensure clarity and consistency in file format across different versions of Autoware and its external applications. Please see discussion for the details.

How to Operate

  • The current file format is set as an unversioned base version (version: field is commented out).
  • For the next update involving changes (such as additions, deletions, or modifications):
    • Uncomment and update the version line at the beginning of the file.
    • Initiate versioning by assigning a version number, starting from 0.1.0. Follow the semantic versioning format (MAJOR.MINOR.PATCH).
    • Update this Readme.md too.
  • For subsequent updates, continue incrementing the version number in accordance with the changes made.
    • Discuss how to increment version depending on the amount of changes made to the file.
/**:
  ros__parameters:
    # version: 0.1.0 # Uncomment and update this line for future format changes.
    wheel_radius: 0.383
    ...

Why Versioning?

  • Consistency Across Updates: Implementing version control will allow accurate tracking of changes over time and changes in vehicle information parameters.
  • Clarity for External Applications: External applications that depend on vehicle_info.param.yaml need to reference the correct file version for optimal compatibility and functionality.
  • Simplified Management for Customized Branches: Assigning versions directly to the vehicle_info.param.yaml file simplifies management compared to maintaining separate versions for multiple customized Autoware branches. This approach streamlines version tracking and reduces complexity.

Scripts

Minimum turning radius

$ ros2 run autoware_vehicle_info_utils min_turning_radius_calculator.py
yaml path is /home/autoware/pilot-auto/install/autoware_vehicle_info_utils/share/autoware_vehicle_info_utils/config/vehicle_info.param.yaml
Minimum turning radius is 3.253042620027102 [m] for rear, 4.253220695862465 [m] for front.

You can designate yaml file with -y option as follows.

ros2 run autoware_vehicle_info_utils min_turning_radius_calculator.py -y <path-to-yaml>

Assumptions / Known limits

TBD.

CHANGELOG

Changelog for package autoware_vehicle_info_utils

1.1.0 (2025-05-01)

  • refactor(autoware_vehicle_info_utils): rewrite using modern C++ without API breakage (#343)
  • Contributors: Yutaka Kondo

1.9.0 (2026-06-24)

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

  • test(autoware_vehicle_info_utils): cover pure paths and reuse get_or_declare_parameter (#1105)

    * test(autoware_vehicle_info_utils): cover pure paths and reuse get_or_declare_parameter Add no-ROS unit tests for the pure VehicleInfo helpers that were previously untested: createVehicleInfo's wheel_base/max_steer clamping and has_non_positive_values branches, calcMaxMinDimension's two branches, extendVehicleInfo's margin distribution, the full 5-margin createFootprint overload (asymmetric margins plus center_at_base_link, asserting all seven ring points), and calcCurvatureFromSteerAngle's NaN guard. These run directly against the free functions / VehicleInfo methods without rclcpp. Replace the file-local getParameter<T> helper in VehicleInfoUtils with autoware_utils_rclcpp::get_or_declare_parameter<T>, which has identical has_parameter/get/declare semantics, and add the autoware_utils_rclcpp dependency. The throwing behavior on a parameter type mismatch is preserved (declare_parameter still throws); only the redundant local RCLCPP_ERROR log line on that path is dropped. No public API change. Refs: autowarefoundation/autoware_core#1096

    * test(autoware_vehicle_info_utils): de-tautologize vehicle_info test oracles (#79) Replace expected values that mirrored the implementation's formula or were read back from the output fields under test with independently hand-computed concrete literals (or stdlib-only computations in the std::hypot style). This makes the assertions verify the calculation instead of re-deriving the same potentially-wrong value. Refs: autowarefoundation/autoware_core#1096

    * test(autoware_vehicle_info_utils): use independent oracles for derived-value asserts (#86) Replace test expected values that mirrored the implementation's own formulas with concrete, independently hand-computed literals so the assertions can no longer pass on a wrong production calculation.

    - extendVehicleInfo: assert hardcoded 4.4 / 2.4 / 1.2 instead of reconstructing 'length + margin' / 'base2back + margin / 2'.

    - calcMaxMinDimension branch guards: drop the ASSERTs that recomputed base2front from the output fields; the branch is fixed by the test-chosen inputs and documented in comments. std::hypot-style expected values (inputs picked by the test, stdlib as the only shared dependency) and the existing hardcoded literals are kept. No production code changed. Refs: autowarefoundation/autoware_core#1096 ---------

  • feat(vehicle_info_utils): adjust [VehicleInfo]{.title-ref} to cover [VehicleShape]{.title-ref} (#1083)

    • add function to help replacing VehicleShape

    * remove defaulted function ---------Co-authored-by: Junya Sasaki <<j2sasaki1990@gmail.com>>

  • feat(autoware_vehicle_info_utils): add base_pose to createFootprint (#1072)

  • Contributors: Sarun MUKDAPITAK, Yutaka Kondo, github-actions

1.8.0 (2026-05-01)

  • Merge remote-tracking branch 'origin/main' into tmp/bot/bump_version_base
  • refactor(autoware_core): add USE_SCOPED_HEADER_INSTALL_DIR to common and testing packages (#967) Co-authored-by: github-actions <<github-actions@github.com>> Co-authored-by: Junya Sasaki <<j2sasaki1990@gmail.com>>
  • Contributors: Vishal Chauhan, github-actions

1.7.0 (2026-02-14)

1.6.0 (2025-12-30)

  • Merge remote-tracking branch 'origin/main' into tmp/bot/bump_version_base
  • docs: fix broken links (#779)

File truncated at 100 lines see the full file

Launch files

No launch files found

Messages

No message files found.

Services

No service files found

Plugins

No plugins found.

Recent questions tagged autoware_vehicle_info_utils at Robotics Stack Exchange

No version for distro melodic showing humble. Known supported distros are highlighted in the buttons above.
Package symbol

autoware_vehicle_info_utils package from autoware_core repo

autoware_adapi_adaptors autoware_adapi_specs autoware_core_api autoware_default_adapi autoware_core autoware_agnocast_wrapper autoware_component_interface_specs autoware_geography_utils autoware_global_parameter_loader autoware_interpolation autoware_kalman_filter autoware_lanelet2_utils autoware_marker_utils autoware_motion_utils autoware_node autoware_object_recognition_utils autoware_osqp_interface autoware_point_types autoware_qos_utils autoware_qp_interface autoware_signal_processing autoware_trajectory autoware_vehicle_info_utils autoware_command_gate autoware_core_control autoware_simple_pure_pursuit autoware_awsim_sensor_kit_description autoware_sample_sensor_kit_description autoware_sample_vehicle_description autoware_core_localization autoware_ekf_localizer autoware_gyro_odometer autoware_localization_util autoware_ndt_scan_matcher autoware_pose_initializer autoware_stop_filter autoware_twist2accel autoware_core_map autoware_lanelet2_map_visualizer autoware_map_height_fitter autoware_map_loader autoware_map_projection_loader autoware_core_perception autoware_euclidean_cluster_object_detector autoware_ground_filter autoware_perception_objects_converter autoware_core_planning autoware_mission_planner autoware_objects_of_interest_marker_interface autoware_path_generator autoware_planning_factor_interface autoware_planning_topic_converter autoware_route_handler autoware_velocity_smoother autoware_behavior_velocity_planner autoware_behavior_velocity_planner_common autoware_behavior_velocity_stop_line_module autoware_motion_velocity_obstacle_stop_module autoware_motion_velocity_planner autoware_motion_velocity_planner_common autoware_core_sensing autoware_crop_box_filter autoware_downsample_filters autoware_gnss_poser autoware_vehicle_velocity_converter autoware_planning_test_manager autoware_pyplot autoware_test_node autoware_test_utils autoware_testing autoware_core_vehicle

ROS Distro
humble

Package Summary

Version 1.9.0
License Apache License 2.0
Build type AMENT_CMAKE
Use RECOMMENDED

Repository Summary

Checkout URI https://github.com/autowarefoundation/autoware_core.git
VCS Type git
VCS Version main
Last Updated 2026-07-03
Dev Status DEVELOPED
Released RELEASED
Contributing Help Wanted (-)
Good First Issues (-)
Pull Requests to Review (-)

Package Description

The autoware_vehicle_info_utils package

Maintainers

  • Taiki Tanaka
  • Tomoya Kimura
  • Shumpei Wakabayashi
  • Mamoru Sobue
  • Jian Kang

Authors

  • Yamato ANDO

Vehicle Info Util

Purpose

This package is to get vehicle info parameters.

Description

In here, you can check the vehicle dimensions with more detail. The current format supports only the Ackermann model. This file defines the model assumed in autoware path planning, control, etc. and does not represent the exact physical model. If a model other than the Ackermann model is used, it is assumed that a vehicle interface will be designed to change the control output for the model.

Versioning Policy

We have implemented a versioning system for the vehicle_info.param.yaml file to ensure clarity and consistency in file format across different versions of Autoware and its external applications. Please see discussion for the details.

How to Operate

  • The current file format is set as an unversioned base version (version: field is commented out).
  • For the next update involving changes (such as additions, deletions, or modifications):
    • Uncomment and update the version line at the beginning of the file.
    • Initiate versioning by assigning a version number, starting from 0.1.0. Follow the semantic versioning format (MAJOR.MINOR.PATCH).
    • Update this Readme.md too.
  • For subsequent updates, continue incrementing the version number in accordance with the changes made.
    • Discuss how to increment version depending on the amount of changes made to the file.
/**:
  ros__parameters:
    # version: 0.1.0 # Uncomment and update this line for future format changes.
    wheel_radius: 0.383
    ...

Why Versioning?

  • Consistency Across Updates: Implementing version control will allow accurate tracking of changes over time and changes in vehicle information parameters.
  • Clarity for External Applications: External applications that depend on vehicle_info.param.yaml need to reference the correct file version for optimal compatibility and functionality.
  • Simplified Management for Customized Branches: Assigning versions directly to the vehicle_info.param.yaml file simplifies management compared to maintaining separate versions for multiple customized Autoware branches. This approach streamlines version tracking and reduces complexity.

Scripts

Minimum turning radius

$ ros2 run autoware_vehicle_info_utils min_turning_radius_calculator.py
yaml path is /home/autoware/pilot-auto/install/autoware_vehicle_info_utils/share/autoware_vehicle_info_utils/config/vehicle_info.param.yaml
Minimum turning radius is 3.253042620027102 [m] for rear, 4.253220695862465 [m] for front.

You can designate yaml file with -y option as follows.

ros2 run autoware_vehicle_info_utils min_turning_radius_calculator.py -y <path-to-yaml>

Assumptions / Known limits

TBD.

CHANGELOG

Changelog for package autoware_vehicle_info_utils

1.1.0 (2025-05-01)

  • refactor(autoware_vehicle_info_utils): rewrite using modern C++ without API breakage (#343)
  • Contributors: Yutaka Kondo

1.9.0 (2026-06-24)

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

  • test(autoware_vehicle_info_utils): cover pure paths and reuse get_or_declare_parameter (#1105)

    * test(autoware_vehicle_info_utils): cover pure paths and reuse get_or_declare_parameter Add no-ROS unit tests for the pure VehicleInfo helpers that were previously untested: createVehicleInfo's wheel_base/max_steer clamping and has_non_positive_values branches, calcMaxMinDimension's two branches, extendVehicleInfo's margin distribution, the full 5-margin createFootprint overload (asymmetric margins plus center_at_base_link, asserting all seven ring points), and calcCurvatureFromSteerAngle's NaN guard. These run directly against the free functions / VehicleInfo methods without rclcpp. Replace the file-local getParameter<T> helper in VehicleInfoUtils with autoware_utils_rclcpp::get_or_declare_parameter<T>, which has identical has_parameter/get/declare semantics, and add the autoware_utils_rclcpp dependency. The throwing behavior on a parameter type mismatch is preserved (declare_parameter still throws); only the redundant local RCLCPP_ERROR log line on that path is dropped. No public API change. Refs: autowarefoundation/autoware_core#1096

    * test(autoware_vehicle_info_utils): de-tautologize vehicle_info test oracles (#79) Replace expected values that mirrored the implementation's formula or were read back from the output fields under test with independently hand-computed concrete literals (or stdlib-only computations in the std::hypot style). This makes the assertions verify the calculation instead of re-deriving the same potentially-wrong value. Refs: autowarefoundation/autoware_core#1096

    * test(autoware_vehicle_info_utils): use independent oracles for derived-value asserts (#86) Replace test expected values that mirrored the implementation's own formulas with concrete, independently hand-computed literals so the assertions can no longer pass on a wrong production calculation.

    - extendVehicleInfo: assert hardcoded 4.4 / 2.4 / 1.2 instead of reconstructing 'length + margin' / 'base2back + margin / 2'.

    - calcMaxMinDimension branch guards: drop the ASSERTs that recomputed base2front from the output fields; the branch is fixed by the test-chosen inputs and documented in comments. std::hypot-style expected values (inputs picked by the test, stdlib as the only shared dependency) and the existing hardcoded literals are kept. No production code changed. Refs: autowarefoundation/autoware_core#1096 ---------

  • feat(vehicle_info_utils): adjust [VehicleInfo]{.title-ref} to cover [VehicleShape]{.title-ref} (#1083)

    • add function to help replacing VehicleShape

    * remove defaulted function ---------Co-authored-by: Junya Sasaki <<j2sasaki1990@gmail.com>>

  • feat(autoware_vehicle_info_utils): add base_pose to createFootprint (#1072)

  • Contributors: Sarun MUKDAPITAK, Yutaka Kondo, github-actions

1.8.0 (2026-05-01)

  • Merge remote-tracking branch 'origin/main' into tmp/bot/bump_version_base
  • refactor(autoware_core): add USE_SCOPED_HEADER_INSTALL_DIR to common and testing packages (#967) Co-authored-by: github-actions <<github-actions@github.com>> Co-authored-by: Junya Sasaki <<j2sasaki1990@gmail.com>>
  • Contributors: Vishal Chauhan, github-actions

1.7.0 (2026-02-14)

1.6.0 (2025-12-30)

  • Merge remote-tracking branch 'origin/main' into tmp/bot/bump_version_base
  • docs: fix broken links (#779)

File truncated at 100 lines see the full file

Launch files

No launch files found

Messages

No message files found.

Services

No service files found

Plugins

No plugins found.

Recent questions tagged autoware_vehicle_info_utils at Robotics Stack Exchange

No version for distro noetic showing humble. Known supported distros are highlighted in the buttons above.
Package symbol

autoware_vehicle_info_utils package from autoware_core repo

autoware_adapi_adaptors autoware_adapi_specs autoware_core_api autoware_default_adapi autoware_core autoware_agnocast_wrapper autoware_component_interface_specs autoware_geography_utils autoware_global_parameter_loader autoware_interpolation autoware_kalman_filter autoware_lanelet2_utils autoware_marker_utils autoware_motion_utils autoware_node autoware_object_recognition_utils autoware_osqp_interface autoware_point_types autoware_qos_utils autoware_qp_interface autoware_signal_processing autoware_trajectory autoware_vehicle_info_utils autoware_command_gate autoware_core_control autoware_simple_pure_pursuit autoware_awsim_sensor_kit_description autoware_sample_sensor_kit_description autoware_sample_vehicle_description autoware_core_localization autoware_ekf_localizer autoware_gyro_odometer autoware_localization_util autoware_ndt_scan_matcher autoware_pose_initializer autoware_stop_filter autoware_twist2accel autoware_core_map autoware_lanelet2_map_visualizer autoware_map_height_fitter autoware_map_loader autoware_map_projection_loader autoware_core_perception autoware_euclidean_cluster_object_detector autoware_ground_filter autoware_perception_objects_converter autoware_core_planning autoware_mission_planner autoware_objects_of_interest_marker_interface autoware_path_generator autoware_planning_factor_interface autoware_planning_topic_converter autoware_route_handler autoware_velocity_smoother autoware_behavior_velocity_planner autoware_behavior_velocity_planner_common autoware_behavior_velocity_stop_line_module autoware_motion_velocity_obstacle_stop_module autoware_motion_velocity_planner autoware_motion_velocity_planner_common autoware_core_sensing autoware_crop_box_filter autoware_downsample_filters autoware_gnss_poser autoware_vehicle_velocity_converter autoware_planning_test_manager autoware_pyplot autoware_test_node autoware_test_utils autoware_testing autoware_core_vehicle

ROS Distro
humble

Package Summary

Version 1.9.0
License Apache License 2.0
Build type AMENT_CMAKE
Use RECOMMENDED

Repository Summary

Checkout URI https://github.com/autowarefoundation/autoware_core.git
VCS Type git
VCS Version main
Last Updated 2026-07-03
Dev Status DEVELOPED
Released RELEASED
Contributing Help Wanted (-)
Good First Issues (-)
Pull Requests to Review (-)

Package Description

The autoware_vehicle_info_utils package

Maintainers

  • Taiki Tanaka
  • Tomoya Kimura
  • Shumpei Wakabayashi
  • Mamoru Sobue
  • Jian Kang

Authors

  • Yamato ANDO

Vehicle Info Util

Purpose

This package is to get vehicle info parameters.

Description

In here, you can check the vehicle dimensions with more detail. The current format supports only the Ackermann model. This file defines the model assumed in autoware path planning, control, etc. and does not represent the exact physical model. If a model other than the Ackermann model is used, it is assumed that a vehicle interface will be designed to change the control output for the model.

Versioning Policy

We have implemented a versioning system for the vehicle_info.param.yaml file to ensure clarity and consistency in file format across different versions of Autoware and its external applications. Please see discussion for the details.

How to Operate

  • The current file format is set as an unversioned base version (version: field is commented out).
  • For the next update involving changes (such as additions, deletions, or modifications):
    • Uncomment and update the version line at the beginning of the file.
    • Initiate versioning by assigning a version number, starting from 0.1.0. Follow the semantic versioning format (MAJOR.MINOR.PATCH).
    • Update this Readme.md too.
  • For subsequent updates, continue incrementing the version number in accordance with the changes made.
    • Discuss how to increment version depending on the amount of changes made to the file.
/**:
  ros__parameters:
    # version: 0.1.0 # Uncomment and update this line for future format changes.
    wheel_radius: 0.383
    ...

Why Versioning?

  • Consistency Across Updates: Implementing version control will allow accurate tracking of changes over time and changes in vehicle information parameters.
  • Clarity for External Applications: External applications that depend on vehicle_info.param.yaml need to reference the correct file version for optimal compatibility and functionality.
  • Simplified Management for Customized Branches: Assigning versions directly to the vehicle_info.param.yaml file simplifies management compared to maintaining separate versions for multiple customized Autoware branches. This approach streamlines version tracking and reduces complexity.

Scripts

Minimum turning radius

$ ros2 run autoware_vehicle_info_utils min_turning_radius_calculator.py
yaml path is /home/autoware/pilot-auto/install/autoware_vehicle_info_utils/share/autoware_vehicle_info_utils/config/vehicle_info.param.yaml
Minimum turning radius is 3.253042620027102 [m] for rear, 4.253220695862465 [m] for front.

You can designate yaml file with -y option as follows.

ros2 run autoware_vehicle_info_utils min_turning_radius_calculator.py -y <path-to-yaml>

Assumptions / Known limits

TBD.

CHANGELOG

Changelog for package autoware_vehicle_info_utils

1.1.0 (2025-05-01)

  • refactor(autoware_vehicle_info_utils): rewrite using modern C++ without API breakage (#343)
  • Contributors: Yutaka Kondo

1.9.0 (2026-06-24)

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

  • test(autoware_vehicle_info_utils): cover pure paths and reuse get_or_declare_parameter (#1105)

    * test(autoware_vehicle_info_utils): cover pure paths and reuse get_or_declare_parameter Add no-ROS unit tests for the pure VehicleInfo helpers that were previously untested: createVehicleInfo's wheel_base/max_steer clamping and has_non_positive_values branches, calcMaxMinDimension's two branches, extendVehicleInfo's margin distribution, the full 5-margin createFootprint overload (asymmetric margins plus center_at_base_link, asserting all seven ring points), and calcCurvatureFromSteerAngle's NaN guard. These run directly against the free functions / VehicleInfo methods without rclcpp. Replace the file-local getParameter<T> helper in VehicleInfoUtils with autoware_utils_rclcpp::get_or_declare_parameter<T>, which has identical has_parameter/get/declare semantics, and add the autoware_utils_rclcpp dependency. The throwing behavior on a parameter type mismatch is preserved (declare_parameter still throws); only the redundant local RCLCPP_ERROR log line on that path is dropped. No public API change. Refs: autowarefoundation/autoware_core#1096

    * test(autoware_vehicle_info_utils): de-tautologize vehicle_info test oracles (#79) Replace expected values that mirrored the implementation's formula or were read back from the output fields under test with independently hand-computed concrete literals (or stdlib-only computations in the std::hypot style). This makes the assertions verify the calculation instead of re-deriving the same potentially-wrong value. Refs: autowarefoundation/autoware_core#1096

    * test(autoware_vehicle_info_utils): use independent oracles for derived-value asserts (#86) Replace test expected values that mirrored the implementation's own formulas with concrete, independently hand-computed literals so the assertions can no longer pass on a wrong production calculation.

    - extendVehicleInfo: assert hardcoded 4.4 / 2.4 / 1.2 instead of reconstructing 'length + margin' / 'base2back + margin / 2'.

    - calcMaxMinDimension branch guards: drop the ASSERTs that recomputed base2front from the output fields; the branch is fixed by the test-chosen inputs and documented in comments. std::hypot-style expected values (inputs picked by the test, stdlib as the only shared dependency) and the existing hardcoded literals are kept. No production code changed. Refs: autowarefoundation/autoware_core#1096 ---------

  • feat(vehicle_info_utils): adjust [VehicleInfo]{.title-ref} to cover [VehicleShape]{.title-ref} (#1083)

    • add function to help replacing VehicleShape

    * remove defaulted function ---------Co-authored-by: Junya Sasaki <<j2sasaki1990@gmail.com>>

  • feat(autoware_vehicle_info_utils): add base_pose to createFootprint (#1072)

  • Contributors: Sarun MUKDAPITAK, Yutaka Kondo, github-actions

1.8.0 (2026-05-01)

  • Merge remote-tracking branch 'origin/main' into tmp/bot/bump_version_base
  • refactor(autoware_core): add USE_SCOPED_HEADER_INSTALL_DIR to common and testing packages (#967) Co-authored-by: github-actions <<github-actions@github.com>> Co-authored-by: Junya Sasaki <<j2sasaki1990@gmail.com>>
  • Contributors: Vishal Chauhan, github-actions

1.7.0 (2026-02-14)

1.6.0 (2025-12-30)

  • Merge remote-tracking branch 'origin/main' into tmp/bot/bump_version_base
  • docs: fix broken links (#779)

File truncated at 100 lines see the full file

Launch files

No launch files found

Messages

No message files found.

Services

No service files found

Plugins

No plugins found.

Recent questions tagged autoware_vehicle_info_utils at Robotics Stack Exchange