Package Summary
Tags | No category tags. |
Version | 0.1.0 |
License | Apache License 2.0 |
Build type | AMENT_CMAKE |
Use | RECOMMENDED |
Repository Summary
Description | |
Checkout URI | https://github.com/ieiauto/autodrrt.git |
VCS Type | git |
VCS Version | main |
Last Updated | 2025-05-30 |
Dev Status | UNKNOWN |
Released | UNRELEASED |
Tags | No category tags. |
Contributing |
Help Wanted (-)
Good First Issues (-) Pull Requests to Review (-) |
Package Description
Additional Links
Maintainers
- Tomoya Kimura
- Taiki Tanaka
- Takeshi Miura
Authors
accel_brake_map_calibrator
The role of this node is to automatically calibrate accel_map.csv
/ brake_map.csv
used in the raw_vehicle_cmd_converter
node.
The base map, which is lexus’s one by default, is updated iteratively with the loaded driving data.
How to calibrate
Launch Calibrator
After launching Autoware, run the accel_brake_map_calibrator
by the following command and then perform autonomous driving. Note: You can collect data with manual driving if it is possible to use the same vehicle interface as during autonomous driving (e.g. using a joystick).
ros2 launch accel_brake_map_calibrator accel_brake_map_calibrator.launch.xml rviz:=true
Or if you want to use rosbag files, run the following commands.
ros2 launch accel_brake_map_calibrator accel_brake_map_calibrator.launch.xml rviz:=true use_sim_time:=true
ros2 bag play <rosbag_file> --clock
During the calibration with setting the parameter progress_file_output
to true, the log file is output in [directory of accel_brake_map_calibrator]/config/ . You can also see accel and brake maps in [directory of accel_brake_map_calibrator]/config/accel_map.csv and [directory of accel_brake_map_calibrator]/config/brake_map.csv after calibration.
Calibration plugin
The rviz:=true
option displays the RViz with a calibration plugin as below.
The current status (velocity and pedal) is shown in the plugin. The color on the current cell varies green/red depending on the current data is valid/invalid. The data that doesn’t satisfy the following conditions are considered invalid and will not be used for estimation since aggressive data (e.g. when the pedal is moving fast) causes bad calibration accuracy.
- The velocity and pedal conditions are within certain ranges from the index values.
- The steer value, pedal speed, pitch value, etc. are less than corresponding thresholds.
- The velocity is higher than a threshold.
The detailed parameters are described in the parameter section.
Note: You don’t need to worry about whether the current state is red or green during calibration. Just keep getting data until all the cells turn red.
The value of each cell in the map is gray at first, and it changes from blue to red as the number of valid data in the cell accumulates. It is preferable to continue the calibration until each cell of the map becomes close to red. In particular, the performance near the stop depends strongly on the velocity of 0 ~ 6m/s range and the pedal value of +0.2 ~ -0.4, range so it is desirable to focus on those areas.
Diagnostics
The accel brake map_calibrator
publishes diagnostics message depending on the calibration status.
Diagnostic type WARN
indicates that the current accel/brake map is estimated to be inaccurate. In this situation, it is strongly recommended to perform a re-calibration of the accel/brake map.
Status | Diagnostics Type | Diagnostics message | Description |
---|---|---|---|
No calibration required | OK |
“OK” | |
Calibration Required | WARN |
“Accel/brake map Calibration is required.” | The accuracy of current accel/brake map may be low. |
This diagnostics status can be also checked on the following ROS topic.
ros2 topic echo /accel_brake_map_calibrator/output/update_suggest
When the diagnostics type is WARN
, True
is published on this topic and the update of the accel/brake map is suggested.
Evaluation of the accel / brake map accuracy
The accuracy of map is evaluated by the Root Mean Squared Error (RMSE) between the observed acceleration and predicted acceleration.
TERMS:
-
Observed acceleration
: the current vehicle acceleration which is calculated as a derivative value of the wheel speed. -
Predicted acceleration
: the output of the original accel/brake map, which the Autoware is expecting. The value is calculated using the current pedal and velocity.
You can check additional error information with the following topics.
-
/accel_brake_map_calibrator/output/current_map_error
: The error of the original map set in thecsv_path_accel/brake_map
path. The original map is not accurate if this value is large. -
/accel_brake_map_calibrator/output/updated_map_error
: The error of the map calibrated in this node. The calibration quality is low if this value is large. -
/accel_brake_map_calibrator/output/map_error_ratio
: The error ratio between the original map and updated map (ratio = updated / current). If this value is less than 1, it is desirable to update the map.
How to visualize calibration data
The process of calibration can be visualized as below. Since these scripts need the log output of the calibration, the pedal_accel_graph_output
parameter must be set to true while the calibration is running for the visualization.
Visualize plot of relation between acceleration and pedal
The following command shows the plot of used data in the calibration. In each plot of velocity ranges, you can see the distribution of the relationship between pedal and acceleration, and raw data points with colors according to their pitch angles.
ros2 run accel_brake_map_calibrator view_plot.py
Visualize statistics about acceleration/velocity/pedal data
The following command shows the statistics of the calibration:
- mean value
- standard deviation
- number of data
File truncated at 100 lines see the full file
Package Dependencies
System Dependencies
Dependant Packages
Launch files
- launch/accel_brake_map_calibrator.launch.xml
-
- accel_brake_map_calib_param [default: $(find-pkg-share accel_brake_map_calibrator)/config/accel_brake_map_calibrator.param.yaml]
- csv_default_map_dir [default: $(find-pkg-share raw_vehicle_cmd_converter)/data/default/]
- csv_calibrated_map_dir [default: $(find-pkg-share accel_brake_map_calibrator)/config/]
- logger_level [default: info]
- rviz [default: true]
- pedal_accel_graph_output [default: true]
- progress_file_output [default: false]
- use_sim_time [default: false]
- calibration_method [default: each_cell]
Messages
Services
Plugins
Recent questions tagged accel_brake_map_calibrator at Robotics Stack Exchange
Package Summary
Tags | No category tags. |
Version | 0.1.0 |
License | Apache License 2.0 |
Build type | AMENT_CMAKE |
Use | RECOMMENDED |
Repository Summary
Description | |
Checkout URI | https://github.com/ieiauto/autodrrt.git |
VCS Type | git |
VCS Version | main |
Last Updated | 2025-05-30 |
Dev Status | UNKNOWN |
Released | UNRELEASED |
Tags | No category tags. |
Contributing |
Help Wanted (-)
Good First Issues (-) Pull Requests to Review (-) |
Package Description
Additional Links
Maintainers
- Tomoya Kimura
- Taiki Tanaka
- Takeshi Miura
Authors
accel_brake_map_calibrator
The role of this node is to automatically calibrate accel_map.csv
/ brake_map.csv
used in the raw_vehicle_cmd_converter
node.
The base map, which is lexus’s one by default, is updated iteratively with the loaded driving data.
How to calibrate
Launch Calibrator
After launching Autoware, run the accel_brake_map_calibrator
by the following command and then perform autonomous driving. Note: You can collect data with manual driving if it is possible to use the same vehicle interface as during autonomous driving (e.g. using a joystick).
ros2 launch accel_brake_map_calibrator accel_brake_map_calibrator.launch.xml rviz:=true
Or if you want to use rosbag files, run the following commands.
ros2 launch accel_brake_map_calibrator accel_brake_map_calibrator.launch.xml rviz:=true use_sim_time:=true
ros2 bag play <rosbag_file> --clock
During the calibration with setting the parameter progress_file_output
to true, the log file is output in [directory of accel_brake_map_calibrator]/config/ . You can also see accel and brake maps in [directory of accel_brake_map_calibrator]/config/accel_map.csv and [directory of accel_brake_map_calibrator]/config/brake_map.csv after calibration.
Calibration plugin
The rviz:=true
option displays the RViz with a calibration plugin as below.
The current status (velocity and pedal) is shown in the plugin. The color on the current cell varies green/red depending on the current data is valid/invalid. The data that doesn’t satisfy the following conditions are considered invalid and will not be used for estimation since aggressive data (e.g. when the pedal is moving fast) causes bad calibration accuracy.
- The velocity and pedal conditions are within certain ranges from the index values.
- The steer value, pedal speed, pitch value, etc. are less than corresponding thresholds.
- The velocity is higher than a threshold.
The detailed parameters are described in the parameter section.
Note: You don’t need to worry about whether the current state is red or green during calibration. Just keep getting data until all the cells turn red.
The value of each cell in the map is gray at first, and it changes from blue to red as the number of valid data in the cell accumulates. It is preferable to continue the calibration until each cell of the map becomes close to red. In particular, the performance near the stop depends strongly on the velocity of 0 ~ 6m/s range and the pedal value of +0.2 ~ -0.4, range so it is desirable to focus on those areas.
Diagnostics
The accel brake map_calibrator
publishes diagnostics message depending on the calibration status.
Diagnostic type WARN
indicates that the current accel/brake map is estimated to be inaccurate. In this situation, it is strongly recommended to perform a re-calibration of the accel/brake map.
Status | Diagnostics Type | Diagnostics message | Description |
---|---|---|---|
No calibration required | OK |
“OK” | |
Calibration Required | WARN |
“Accel/brake map Calibration is required.” | The accuracy of current accel/brake map may be low. |
This diagnostics status can be also checked on the following ROS topic.
ros2 topic echo /accel_brake_map_calibrator/output/update_suggest
When the diagnostics type is WARN
, True
is published on this topic and the update of the accel/brake map is suggested.
Evaluation of the accel / brake map accuracy
The accuracy of map is evaluated by the Root Mean Squared Error (RMSE) between the observed acceleration and predicted acceleration.
TERMS:
-
Observed acceleration
: the current vehicle acceleration which is calculated as a derivative value of the wheel speed. -
Predicted acceleration
: the output of the original accel/brake map, which the Autoware is expecting. The value is calculated using the current pedal and velocity.
You can check additional error information with the following topics.
-
/accel_brake_map_calibrator/output/current_map_error
: The error of the original map set in thecsv_path_accel/brake_map
path. The original map is not accurate if this value is large. -
/accel_brake_map_calibrator/output/updated_map_error
: The error of the map calibrated in this node. The calibration quality is low if this value is large. -
/accel_brake_map_calibrator/output/map_error_ratio
: The error ratio between the original map and updated map (ratio = updated / current). If this value is less than 1, it is desirable to update the map.
How to visualize calibration data
The process of calibration can be visualized as below. Since these scripts need the log output of the calibration, the pedal_accel_graph_output
parameter must be set to true while the calibration is running for the visualization.
Visualize plot of relation between acceleration and pedal
The following command shows the plot of used data in the calibration. In each plot of velocity ranges, you can see the distribution of the relationship between pedal and acceleration, and raw data points with colors according to their pitch angles.
ros2 run accel_brake_map_calibrator view_plot.py
Visualize statistics about acceleration/velocity/pedal data
The following command shows the statistics of the calibration:
- mean value
- standard deviation
- number of data
File truncated at 100 lines see the full file
Package Dependencies
System Dependencies
Dependant Packages
Launch files
- launch/accel_brake_map_calibrator.launch.xml
-
- accel_brake_map_calib_param [default: $(find-pkg-share accel_brake_map_calibrator)/config/accel_brake_map_calibrator.param.yaml]
- csv_default_map_dir [default: $(find-pkg-share raw_vehicle_cmd_converter)/data/default/]
- csv_calibrated_map_dir [default: $(find-pkg-share accel_brake_map_calibrator)/config/]
- logger_level [default: info]
- rviz [default: true]
- pedal_accel_graph_output [default: true]
- progress_file_output [default: false]
- use_sim_time [default: false]
- calibration_method [default: each_cell]
Messages
Services
Plugins
Recent questions tagged accel_brake_map_calibrator at Robotics Stack Exchange
Package Summary
Tags | No category tags. |
Version | 0.1.0 |
License | Apache License 2.0 |
Build type | AMENT_CMAKE |
Use | RECOMMENDED |
Repository Summary
Description | |
Checkout URI | https://github.com/ieiauto/autodrrt.git |
VCS Type | git |
VCS Version | main |
Last Updated | 2025-05-30 |
Dev Status | UNKNOWN |
Released | UNRELEASED |
Tags | No category tags. |
Contributing |
Help Wanted (-)
Good First Issues (-) Pull Requests to Review (-) |
Package Description
Additional Links
Maintainers
- Tomoya Kimura
- Taiki Tanaka
- Takeshi Miura
Authors
accel_brake_map_calibrator
The role of this node is to automatically calibrate accel_map.csv
/ brake_map.csv
used in the raw_vehicle_cmd_converter
node.
The base map, which is lexus’s one by default, is updated iteratively with the loaded driving data.
How to calibrate
Launch Calibrator
After launching Autoware, run the accel_brake_map_calibrator
by the following command and then perform autonomous driving. Note: You can collect data with manual driving if it is possible to use the same vehicle interface as during autonomous driving (e.g. using a joystick).
ros2 launch accel_brake_map_calibrator accel_brake_map_calibrator.launch.xml rviz:=true
Or if you want to use rosbag files, run the following commands.
ros2 launch accel_brake_map_calibrator accel_brake_map_calibrator.launch.xml rviz:=true use_sim_time:=true
ros2 bag play <rosbag_file> --clock
During the calibration with setting the parameter progress_file_output
to true, the log file is output in [directory of accel_brake_map_calibrator]/config/ . You can also see accel and brake maps in [directory of accel_brake_map_calibrator]/config/accel_map.csv and [directory of accel_brake_map_calibrator]/config/brake_map.csv after calibration.
Calibration plugin
The rviz:=true
option displays the RViz with a calibration plugin as below.
The current status (velocity and pedal) is shown in the plugin. The color on the current cell varies green/red depending on the current data is valid/invalid. The data that doesn’t satisfy the following conditions are considered invalid and will not be used for estimation since aggressive data (e.g. when the pedal is moving fast) causes bad calibration accuracy.
- The velocity and pedal conditions are within certain ranges from the index values.
- The steer value, pedal speed, pitch value, etc. are less than corresponding thresholds.
- The velocity is higher than a threshold.
The detailed parameters are described in the parameter section.
Note: You don’t need to worry about whether the current state is red or green during calibration. Just keep getting data until all the cells turn red.
The value of each cell in the map is gray at first, and it changes from blue to red as the number of valid data in the cell accumulates. It is preferable to continue the calibration until each cell of the map becomes close to red. In particular, the performance near the stop depends strongly on the velocity of 0 ~ 6m/s range and the pedal value of +0.2 ~ -0.4, range so it is desirable to focus on those areas.
Diagnostics
The accel brake map_calibrator
publishes diagnostics message depending on the calibration status.
Diagnostic type WARN
indicates that the current accel/brake map is estimated to be inaccurate. In this situation, it is strongly recommended to perform a re-calibration of the accel/brake map.
Status | Diagnostics Type | Diagnostics message | Description |
---|---|---|---|
No calibration required | OK |
“OK” | |
Calibration Required | WARN |
“Accel/brake map Calibration is required.” | The accuracy of current accel/brake map may be low. |
This diagnostics status can be also checked on the following ROS topic.
ros2 topic echo /accel_brake_map_calibrator/output/update_suggest
When the diagnostics type is WARN
, True
is published on this topic and the update of the accel/brake map is suggested.
Evaluation of the accel / brake map accuracy
The accuracy of map is evaluated by the Root Mean Squared Error (RMSE) between the observed acceleration and predicted acceleration.
TERMS:
-
Observed acceleration
: the current vehicle acceleration which is calculated as a derivative value of the wheel speed. -
Predicted acceleration
: the output of the original accel/brake map, which the Autoware is expecting. The value is calculated using the current pedal and velocity.
You can check additional error information with the following topics.
-
/accel_brake_map_calibrator/output/current_map_error
: The error of the original map set in thecsv_path_accel/brake_map
path. The original map is not accurate if this value is large. -
/accel_brake_map_calibrator/output/updated_map_error
: The error of the map calibrated in this node. The calibration quality is low if this value is large. -
/accel_brake_map_calibrator/output/map_error_ratio
: The error ratio between the original map and updated map (ratio = updated / current). If this value is less than 1, it is desirable to update the map.
How to visualize calibration data
The process of calibration can be visualized as below. Since these scripts need the log output of the calibration, the pedal_accel_graph_output
parameter must be set to true while the calibration is running for the visualization.
Visualize plot of relation between acceleration and pedal
The following command shows the plot of used data in the calibration. In each plot of velocity ranges, you can see the distribution of the relationship between pedal and acceleration, and raw data points with colors according to their pitch angles.
ros2 run accel_brake_map_calibrator view_plot.py
Visualize statistics about acceleration/velocity/pedal data
The following command shows the statistics of the calibration:
- mean value
- standard deviation
- number of data
File truncated at 100 lines see the full file
Package Dependencies
System Dependencies
Dependant Packages
Launch files
- launch/accel_brake_map_calibrator.launch.xml
-
- accel_brake_map_calib_param [default: $(find-pkg-share accel_brake_map_calibrator)/config/accel_brake_map_calibrator.param.yaml]
- csv_default_map_dir [default: $(find-pkg-share raw_vehicle_cmd_converter)/data/default/]
- csv_calibrated_map_dir [default: $(find-pkg-share accel_brake_map_calibrator)/config/]
- logger_level [default: info]
- rviz [default: true]
- pedal_accel_graph_output [default: true]
- progress_file_output [default: false]
- use_sim_time [default: false]
- calibration_method [default: each_cell]
Messages
Services
Plugins
Recent questions tagged accel_brake_map_calibrator at Robotics Stack Exchange
Package Summary
Tags | No category tags. |
Version | 0.1.0 |
License | Apache License 2.0 |
Build type | AMENT_CMAKE |
Use | RECOMMENDED |
Repository Summary
Description | |
Checkout URI | https://github.com/ieiauto/autodrrt.git |
VCS Type | git |
VCS Version | main |
Last Updated | 2025-05-30 |
Dev Status | UNKNOWN |
Released | UNRELEASED |
Tags | No category tags. |
Contributing |
Help Wanted (-)
Good First Issues (-) Pull Requests to Review (-) |
Package Description
Additional Links
Maintainers
- Tomoya Kimura
- Taiki Tanaka
- Takeshi Miura
Authors
accel_brake_map_calibrator
The role of this node is to automatically calibrate accel_map.csv
/ brake_map.csv
used in the raw_vehicle_cmd_converter
node.
The base map, which is lexus’s one by default, is updated iteratively with the loaded driving data.
How to calibrate
Launch Calibrator
After launching Autoware, run the accel_brake_map_calibrator
by the following command and then perform autonomous driving. Note: You can collect data with manual driving if it is possible to use the same vehicle interface as during autonomous driving (e.g. using a joystick).
ros2 launch accel_brake_map_calibrator accel_brake_map_calibrator.launch.xml rviz:=true
Or if you want to use rosbag files, run the following commands.
ros2 launch accel_brake_map_calibrator accel_brake_map_calibrator.launch.xml rviz:=true use_sim_time:=true
ros2 bag play <rosbag_file> --clock
During the calibration with setting the parameter progress_file_output
to true, the log file is output in [directory of accel_brake_map_calibrator]/config/ . You can also see accel and brake maps in [directory of accel_brake_map_calibrator]/config/accel_map.csv and [directory of accel_brake_map_calibrator]/config/brake_map.csv after calibration.
Calibration plugin
The rviz:=true
option displays the RViz with a calibration plugin as below.
The current status (velocity and pedal) is shown in the plugin. The color on the current cell varies green/red depending on the current data is valid/invalid. The data that doesn’t satisfy the following conditions are considered invalid and will not be used for estimation since aggressive data (e.g. when the pedal is moving fast) causes bad calibration accuracy.
- The velocity and pedal conditions are within certain ranges from the index values.
- The steer value, pedal speed, pitch value, etc. are less than corresponding thresholds.
- The velocity is higher than a threshold.
The detailed parameters are described in the parameter section.
Note: You don’t need to worry about whether the current state is red or green during calibration. Just keep getting data until all the cells turn red.
The value of each cell in the map is gray at first, and it changes from blue to red as the number of valid data in the cell accumulates. It is preferable to continue the calibration until each cell of the map becomes close to red. In particular, the performance near the stop depends strongly on the velocity of 0 ~ 6m/s range and the pedal value of +0.2 ~ -0.4, range so it is desirable to focus on those areas.
Diagnostics
The accel brake map_calibrator
publishes diagnostics message depending on the calibration status.
Diagnostic type WARN
indicates that the current accel/brake map is estimated to be inaccurate. In this situation, it is strongly recommended to perform a re-calibration of the accel/brake map.
Status | Diagnostics Type | Diagnostics message | Description |
---|---|---|---|
No calibration required | OK |
“OK” | |
Calibration Required | WARN |
“Accel/brake map Calibration is required.” | The accuracy of current accel/brake map may be low. |
This diagnostics status can be also checked on the following ROS topic.
ros2 topic echo /accel_brake_map_calibrator/output/update_suggest
When the diagnostics type is WARN
, True
is published on this topic and the update of the accel/brake map is suggested.
Evaluation of the accel / brake map accuracy
The accuracy of map is evaluated by the Root Mean Squared Error (RMSE) between the observed acceleration and predicted acceleration.
TERMS:
-
Observed acceleration
: the current vehicle acceleration which is calculated as a derivative value of the wheel speed. -
Predicted acceleration
: the output of the original accel/brake map, which the Autoware is expecting. The value is calculated using the current pedal and velocity.
You can check additional error information with the following topics.
-
/accel_brake_map_calibrator/output/current_map_error
: The error of the original map set in thecsv_path_accel/brake_map
path. The original map is not accurate if this value is large. -
/accel_brake_map_calibrator/output/updated_map_error
: The error of the map calibrated in this node. The calibration quality is low if this value is large. -
/accel_brake_map_calibrator/output/map_error_ratio
: The error ratio between the original map and updated map (ratio = updated / current). If this value is less than 1, it is desirable to update the map.
How to visualize calibration data
The process of calibration can be visualized as below. Since these scripts need the log output of the calibration, the pedal_accel_graph_output
parameter must be set to true while the calibration is running for the visualization.
Visualize plot of relation between acceleration and pedal
The following command shows the plot of used data in the calibration. In each plot of velocity ranges, you can see the distribution of the relationship between pedal and acceleration, and raw data points with colors according to their pitch angles.
ros2 run accel_brake_map_calibrator view_plot.py
Visualize statistics about acceleration/velocity/pedal data
The following command shows the statistics of the calibration:
- mean value
- standard deviation
- number of data
File truncated at 100 lines see the full file
Package Dependencies
System Dependencies
Dependant Packages
Launch files
- launch/accel_brake_map_calibrator.launch.xml
-
- accel_brake_map_calib_param [default: $(find-pkg-share accel_brake_map_calibrator)/config/accel_brake_map_calibrator.param.yaml]
- csv_default_map_dir [default: $(find-pkg-share raw_vehicle_cmd_converter)/data/default/]
- csv_calibrated_map_dir [default: $(find-pkg-share accel_brake_map_calibrator)/config/]
- logger_level [default: info]
- rviz [default: true]
- pedal_accel_graph_output [default: true]
- progress_file_output [default: false]
- use_sim_time [default: false]
- calibration_method [default: each_cell]
Messages
Services
Plugins
Recent questions tagged accel_brake_map_calibrator at Robotics Stack Exchange
Package Summary
Tags | No category tags. |
Version | 0.1.0 |
License | Apache License 2.0 |
Build type | AMENT_CMAKE |
Use | RECOMMENDED |
Repository Summary
Description | |
Checkout URI | https://github.com/ieiauto/autodrrt.git |
VCS Type | git |
VCS Version | main |
Last Updated | 2025-05-30 |
Dev Status | UNKNOWN |
Released | UNRELEASED |
Tags | No category tags. |
Contributing |
Help Wanted (-)
Good First Issues (-) Pull Requests to Review (-) |
Package Description
Additional Links
Maintainers
- Tomoya Kimura
- Taiki Tanaka
- Takeshi Miura
Authors
accel_brake_map_calibrator
The role of this node is to automatically calibrate accel_map.csv
/ brake_map.csv
used in the raw_vehicle_cmd_converter
node.
The base map, which is lexus’s one by default, is updated iteratively with the loaded driving data.
How to calibrate
Launch Calibrator
After launching Autoware, run the accel_brake_map_calibrator
by the following command and then perform autonomous driving. Note: You can collect data with manual driving if it is possible to use the same vehicle interface as during autonomous driving (e.g. using a joystick).
ros2 launch accel_brake_map_calibrator accel_brake_map_calibrator.launch.xml rviz:=true
Or if you want to use rosbag files, run the following commands.
ros2 launch accel_brake_map_calibrator accel_brake_map_calibrator.launch.xml rviz:=true use_sim_time:=true
ros2 bag play <rosbag_file> --clock
During the calibration with setting the parameter progress_file_output
to true, the log file is output in [directory of accel_brake_map_calibrator]/config/ . You can also see accel and brake maps in [directory of accel_brake_map_calibrator]/config/accel_map.csv and [directory of accel_brake_map_calibrator]/config/brake_map.csv after calibration.
Calibration plugin
The rviz:=true
option displays the RViz with a calibration plugin as below.
The current status (velocity and pedal) is shown in the plugin. The color on the current cell varies green/red depending on the current data is valid/invalid. The data that doesn’t satisfy the following conditions are considered invalid and will not be used for estimation since aggressive data (e.g. when the pedal is moving fast) causes bad calibration accuracy.
- The velocity and pedal conditions are within certain ranges from the index values.
- The steer value, pedal speed, pitch value, etc. are less than corresponding thresholds.
- The velocity is higher than a threshold.
The detailed parameters are described in the parameter section.
Note: You don’t need to worry about whether the current state is red or green during calibration. Just keep getting data until all the cells turn red.
The value of each cell in the map is gray at first, and it changes from blue to red as the number of valid data in the cell accumulates. It is preferable to continue the calibration until each cell of the map becomes close to red. In particular, the performance near the stop depends strongly on the velocity of 0 ~ 6m/s range and the pedal value of +0.2 ~ -0.4, range so it is desirable to focus on those areas.
Diagnostics
The accel brake map_calibrator
publishes diagnostics message depending on the calibration status.
Diagnostic type WARN
indicates that the current accel/brake map is estimated to be inaccurate. In this situation, it is strongly recommended to perform a re-calibration of the accel/brake map.
Status | Diagnostics Type | Diagnostics message | Description |
---|---|---|---|
No calibration required | OK |
“OK” | |
Calibration Required | WARN |
“Accel/brake map Calibration is required.” | The accuracy of current accel/brake map may be low. |
This diagnostics status can be also checked on the following ROS topic.
ros2 topic echo /accel_brake_map_calibrator/output/update_suggest
When the diagnostics type is WARN
, True
is published on this topic and the update of the accel/brake map is suggested.
Evaluation of the accel / brake map accuracy
The accuracy of map is evaluated by the Root Mean Squared Error (RMSE) between the observed acceleration and predicted acceleration.
TERMS:
-
Observed acceleration
: the current vehicle acceleration which is calculated as a derivative value of the wheel speed. -
Predicted acceleration
: the output of the original accel/brake map, which the Autoware is expecting. The value is calculated using the current pedal and velocity.
You can check additional error information with the following topics.
-
/accel_brake_map_calibrator/output/current_map_error
: The error of the original map set in thecsv_path_accel/brake_map
path. The original map is not accurate if this value is large. -
/accel_brake_map_calibrator/output/updated_map_error
: The error of the map calibrated in this node. The calibration quality is low if this value is large. -
/accel_brake_map_calibrator/output/map_error_ratio
: The error ratio between the original map and updated map (ratio = updated / current). If this value is less than 1, it is desirable to update the map.
How to visualize calibration data
The process of calibration can be visualized as below. Since these scripts need the log output of the calibration, the pedal_accel_graph_output
parameter must be set to true while the calibration is running for the visualization.
Visualize plot of relation between acceleration and pedal
The following command shows the plot of used data in the calibration. In each plot of velocity ranges, you can see the distribution of the relationship between pedal and acceleration, and raw data points with colors according to their pitch angles.
ros2 run accel_brake_map_calibrator view_plot.py
Visualize statistics about acceleration/velocity/pedal data
The following command shows the statistics of the calibration:
- mean value
- standard deviation
- number of data
File truncated at 100 lines see the full file
Package Dependencies
System Dependencies
Dependant Packages
Launch files
- launch/accel_brake_map_calibrator.launch.xml
-
- accel_brake_map_calib_param [default: $(find-pkg-share accel_brake_map_calibrator)/config/accel_brake_map_calibrator.param.yaml]
- csv_default_map_dir [default: $(find-pkg-share raw_vehicle_cmd_converter)/data/default/]
- csv_calibrated_map_dir [default: $(find-pkg-share accel_brake_map_calibrator)/config/]
- logger_level [default: info]
- rviz [default: true]
- pedal_accel_graph_output [default: true]
- progress_file_output [default: false]
- use_sim_time [default: false]
- calibration_method [default: each_cell]
Messages
Services
Plugins
Recent questions tagged accel_brake_map_calibrator at Robotics Stack Exchange
Package Summary
Tags | No category tags. |
Version | 0.1.0 |
License | Apache License 2.0 |
Build type | AMENT_CMAKE |
Use | RECOMMENDED |
Repository Summary
Description | |
Checkout URI | https://github.com/ieiauto/autodrrt.git |
VCS Type | git |
VCS Version | main |
Last Updated | 2025-05-30 |
Dev Status | UNKNOWN |
Released | UNRELEASED |
Tags | No category tags. |
Contributing |
Help Wanted (-)
Good First Issues (-) Pull Requests to Review (-) |
Package Description
Additional Links
Maintainers
- Tomoya Kimura
- Taiki Tanaka
- Takeshi Miura
Authors
accel_brake_map_calibrator
The role of this node is to automatically calibrate accel_map.csv
/ brake_map.csv
used in the raw_vehicle_cmd_converter
node.
The base map, which is lexus’s one by default, is updated iteratively with the loaded driving data.
How to calibrate
Launch Calibrator
After launching Autoware, run the accel_brake_map_calibrator
by the following command and then perform autonomous driving. Note: You can collect data with manual driving if it is possible to use the same vehicle interface as during autonomous driving (e.g. using a joystick).
ros2 launch accel_brake_map_calibrator accel_brake_map_calibrator.launch.xml rviz:=true
Or if you want to use rosbag files, run the following commands.
ros2 launch accel_brake_map_calibrator accel_brake_map_calibrator.launch.xml rviz:=true use_sim_time:=true
ros2 bag play <rosbag_file> --clock
During the calibration with setting the parameter progress_file_output
to true, the log file is output in [directory of accel_brake_map_calibrator]/config/ . You can also see accel and brake maps in [directory of accel_brake_map_calibrator]/config/accel_map.csv and [directory of accel_brake_map_calibrator]/config/brake_map.csv after calibration.
Calibration plugin
The rviz:=true
option displays the RViz with a calibration plugin as below.
The current status (velocity and pedal) is shown in the plugin. The color on the current cell varies green/red depending on the current data is valid/invalid. The data that doesn’t satisfy the following conditions are considered invalid and will not be used for estimation since aggressive data (e.g. when the pedal is moving fast) causes bad calibration accuracy.
- The velocity and pedal conditions are within certain ranges from the index values.
- The steer value, pedal speed, pitch value, etc. are less than corresponding thresholds.
- The velocity is higher than a threshold.
The detailed parameters are described in the parameter section.
Note: You don’t need to worry about whether the current state is red or green during calibration. Just keep getting data until all the cells turn red.
The value of each cell in the map is gray at first, and it changes from blue to red as the number of valid data in the cell accumulates. It is preferable to continue the calibration until each cell of the map becomes close to red. In particular, the performance near the stop depends strongly on the velocity of 0 ~ 6m/s range and the pedal value of +0.2 ~ -0.4, range so it is desirable to focus on those areas.
Diagnostics
The accel brake map_calibrator
publishes diagnostics message depending on the calibration status.
Diagnostic type WARN
indicates that the current accel/brake map is estimated to be inaccurate. In this situation, it is strongly recommended to perform a re-calibration of the accel/brake map.
Status | Diagnostics Type | Diagnostics message | Description |
---|---|---|---|
No calibration required | OK |
“OK” | |
Calibration Required | WARN |
“Accel/brake map Calibration is required.” | The accuracy of current accel/brake map may be low. |
This diagnostics status can be also checked on the following ROS topic.
ros2 topic echo /accel_brake_map_calibrator/output/update_suggest
When the diagnostics type is WARN
, True
is published on this topic and the update of the accel/brake map is suggested.
Evaluation of the accel / brake map accuracy
The accuracy of map is evaluated by the Root Mean Squared Error (RMSE) between the observed acceleration and predicted acceleration.
TERMS:
-
Observed acceleration
: the current vehicle acceleration which is calculated as a derivative value of the wheel speed. -
Predicted acceleration
: the output of the original accel/brake map, which the Autoware is expecting. The value is calculated using the current pedal and velocity.
You can check additional error information with the following topics.
-
/accel_brake_map_calibrator/output/current_map_error
: The error of the original map set in thecsv_path_accel/brake_map
path. The original map is not accurate if this value is large. -
/accel_brake_map_calibrator/output/updated_map_error
: The error of the map calibrated in this node. The calibration quality is low if this value is large. -
/accel_brake_map_calibrator/output/map_error_ratio
: The error ratio between the original map and updated map (ratio = updated / current). If this value is less than 1, it is desirable to update the map.
How to visualize calibration data
The process of calibration can be visualized as below. Since these scripts need the log output of the calibration, the pedal_accel_graph_output
parameter must be set to true while the calibration is running for the visualization.
Visualize plot of relation between acceleration and pedal
The following command shows the plot of used data in the calibration. In each plot of velocity ranges, you can see the distribution of the relationship between pedal and acceleration, and raw data points with colors according to their pitch angles.
ros2 run accel_brake_map_calibrator view_plot.py
Visualize statistics about acceleration/velocity/pedal data
The following command shows the statistics of the calibration:
- mean value
- standard deviation
- number of data
File truncated at 100 lines see the full file
Package Dependencies
System Dependencies
Dependant Packages
Launch files
- launch/accel_brake_map_calibrator.launch.xml
-
- accel_brake_map_calib_param [default: $(find-pkg-share accel_brake_map_calibrator)/config/accel_brake_map_calibrator.param.yaml]
- csv_default_map_dir [default: $(find-pkg-share raw_vehicle_cmd_converter)/data/default/]
- csv_calibrated_map_dir [default: $(find-pkg-share accel_brake_map_calibrator)/config/]
- logger_level [default: info]
- rviz [default: true]
- pedal_accel_graph_output [default: true]
- progress_file_output [default: false]
- use_sim_time [default: false]
- calibration_method [default: each_cell]
Messages
Services
Plugins
Recent questions tagged accel_brake_map_calibrator at Robotics Stack Exchange
Package Summary
Tags | No category tags. |
Version | 0.1.0 |
License | Apache License 2.0 |
Build type | AMENT_CMAKE |
Use | RECOMMENDED |
Repository Summary
Description | |
Checkout URI | https://github.com/ieiauto/autodrrt.git |
VCS Type | git |
VCS Version | main |
Last Updated | 2025-05-30 |
Dev Status | UNKNOWN |
Released | UNRELEASED |
Tags | No category tags. |
Contributing |
Help Wanted (-)
Good First Issues (-) Pull Requests to Review (-) |
Package Description
Additional Links
Maintainers
- Tomoya Kimura
- Taiki Tanaka
- Takeshi Miura
Authors
accel_brake_map_calibrator
The role of this node is to automatically calibrate accel_map.csv
/ brake_map.csv
used in the raw_vehicle_cmd_converter
node.
The base map, which is lexus’s one by default, is updated iteratively with the loaded driving data.
How to calibrate
Launch Calibrator
After launching Autoware, run the accel_brake_map_calibrator
by the following command and then perform autonomous driving. Note: You can collect data with manual driving if it is possible to use the same vehicle interface as during autonomous driving (e.g. using a joystick).
ros2 launch accel_brake_map_calibrator accel_brake_map_calibrator.launch.xml rviz:=true
Or if you want to use rosbag files, run the following commands.
ros2 launch accel_brake_map_calibrator accel_brake_map_calibrator.launch.xml rviz:=true use_sim_time:=true
ros2 bag play <rosbag_file> --clock
During the calibration with setting the parameter progress_file_output
to true, the log file is output in [directory of accel_brake_map_calibrator]/config/ . You can also see accel and brake maps in [directory of accel_brake_map_calibrator]/config/accel_map.csv and [directory of accel_brake_map_calibrator]/config/brake_map.csv after calibration.
Calibration plugin
The rviz:=true
option displays the RViz with a calibration plugin as below.
The current status (velocity and pedal) is shown in the plugin. The color on the current cell varies green/red depending on the current data is valid/invalid. The data that doesn’t satisfy the following conditions are considered invalid and will not be used for estimation since aggressive data (e.g. when the pedal is moving fast) causes bad calibration accuracy.
- The velocity and pedal conditions are within certain ranges from the index values.
- The steer value, pedal speed, pitch value, etc. are less than corresponding thresholds.
- The velocity is higher than a threshold.
The detailed parameters are described in the parameter section.
Note: You don’t need to worry about whether the current state is red or green during calibration. Just keep getting data until all the cells turn red.
The value of each cell in the map is gray at first, and it changes from blue to red as the number of valid data in the cell accumulates. It is preferable to continue the calibration until each cell of the map becomes close to red. In particular, the performance near the stop depends strongly on the velocity of 0 ~ 6m/s range and the pedal value of +0.2 ~ -0.4, range so it is desirable to focus on those areas.
Diagnostics
The accel brake map_calibrator
publishes diagnostics message depending on the calibration status.
Diagnostic type WARN
indicates that the current accel/brake map is estimated to be inaccurate. In this situation, it is strongly recommended to perform a re-calibration of the accel/brake map.
Status | Diagnostics Type | Diagnostics message | Description |
---|---|---|---|
No calibration required | OK |
“OK” | |
Calibration Required | WARN |
“Accel/brake map Calibration is required.” | The accuracy of current accel/brake map may be low. |
This diagnostics status can be also checked on the following ROS topic.
ros2 topic echo /accel_brake_map_calibrator/output/update_suggest
When the diagnostics type is WARN
, True
is published on this topic and the update of the accel/brake map is suggested.
Evaluation of the accel / brake map accuracy
The accuracy of map is evaluated by the Root Mean Squared Error (RMSE) between the observed acceleration and predicted acceleration.
TERMS:
-
Observed acceleration
: the current vehicle acceleration which is calculated as a derivative value of the wheel speed. -
Predicted acceleration
: the output of the original accel/brake map, which the Autoware is expecting. The value is calculated using the current pedal and velocity.
You can check additional error information with the following topics.
-
/accel_brake_map_calibrator/output/current_map_error
: The error of the original map set in thecsv_path_accel/brake_map
path. The original map is not accurate if this value is large. -
/accel_brake_map_calibrator/output/updated_map_error
: The error of the map calibrated in this node. The calibration quality is low if this value is large. -
/accel_brake_map_calibrator/output/map_error_ratio
: The error ratio between the original map and updated map (ratio = updated / current). If this value is less than 1, it is desirable to update the map.
How to visualize calibration data
The process of calibration can be visualized as below. Since these scripts need the log output of the calibration, the pedal_accel_graph_output
parameter must be set to true while the calibration is running for the visualization.
Visualize plot of relation between acceleration and pedal
The following command shows the plot of used data in the calibration. In each plot of velocity ranges, you can see the distribution of the relationship between pedal and acceleration, and raw data points with colors according to their pitch angles.
ros2 run accel_brake_map_calibrator view_plot.py
Visualize statistics about acceleration/velocity/pedal data
The following command shows the statistics of the calibration:
- mean value
- standard deviation
- number of data
File truncated at 100 lines see the full file
Package Dependencies
System Dependencies
Dependant Packages
Launch files
- launch/accel_brake_map_calibrator.launch.xml
-
- accel_brake_map_calib_param [default: $(find-pkg-share accel_brake_map_calibrator)/config/accel_brake_map_calibrator.param.yaml]
- csv_default_map_dir [default: $(find-pkg-share raw_vehicle_cmd_converter)/data/default/]
- csv_calibrated_map_dir [default: $(find-pkg-share accel_brake_map_calibrator)/config/]
- logger_level [default: info]
- rviz [default: true]
- pedal_accel_graph_output [default: true]
- progress_file_output [default: false]
- use_sim_time [default: false]
- calibration_method [default: each_cell]
Messages
Services
Plugins
Recent questions tagged accel_brake_map_calibrator at Robotics Stack Exchange
Package Summary
Tags | No category tags. |
Version | 0.1.0 |
License | Apache License 2.0 |
Build type | AMENT_CMAKE |
Use | RECOMMENDED |
Repository Summary
Description | |
Checkout URI | https://github.com/ieiauto/autodrrt.git |
VCS Type | git |
VCS Version | main |
Last Updated | 2025-05-30 |
Dev Status | UNKNOWN |
Released | UNRELEASED |
Tags | No category tags. |
Contributing |
Help Wanted (-)
Good First Issues (-) Pull Requests to Review (-) |
Package Description
Additional Links
Maintainers
- Tomoya Kimura
- Taiki Tanaka
- Takeshi Miura
Authors
accel_brake_map_calibrator
The role of this node is to automatically calibrate accel_map.csv
/ brake_map.csv
used in the raw_vehicle_cmd_converter
node.
The base map, which is lexus’s one by default, is updated iteratively with the loaded driving data.
How to calibrate
Launch Calibrator
After launching Autoware, run the accel_brake_map_calibrator
by the following command and then perform autonomous driving. Note: You can collect data with manual driving if it is possible to use the same vehicle interface as during autonomous driving (e.g. using a joystick).
ros2 launch accel_brake_map_calibrator accel_brake_map_calibrator.launch.xml rviz:=true
Or if you want to use rosbag files, run the following commands.
ros2 launch accel_brake_map_calibrator accel_brake_map_calibrator.launch.xml rviz:=true use_sim_time:=true
ros2 bag play <rosbag_file> --clock
During the calibration with setting the parameter progress_file_output
to true, the log file is output in [directory of accel_brake_map_calibrator]/config/ . You can also see accel and brake maps in [directory of accel_brake_map_calibrator]/config/accel_map.csv and [directory of accel_brake_map_calibrator]/config/brake_map.csv after calibration.
Calibration plugin
The rviz:=true
option displays the RViz with a calibration plugin as below.
The current status (velocity and pedal) is shown in the plugin. The color on the current cell varies green/red depending on the current data is valid/invalid. The data that doesn’t satisfy the following conditions are considered invalid and will not be used for estimation since aggressive data (e.g. when the pedal is moving fast) causes bad calibration accuracy.
- The velocity and pedal conditions are within certain ranges from the index values.
- The steer value, pedal speed, pitch value, etc. are less than corresponding thresholds.
- The velocity is higher than a threshold.
The detailed parameters are described in the parameter section.
Note: You don’t need to worry about whether the current state is red or green during calibration. Just keep getting data until all the cells turn red.
The value of each cell in the map is gray at first, and it changes from blue to red as the number of valid data in the cell accumulates. It is preferable to continue the calibration until each cell of the map becomes close to red. In particular, the performance near the stop depends strongly on the velocity of 0 ~ 6m/s range and the pedal value of +0.2 ~ -0.4, range so it is desirable to focus on those areas.
Diagnostics
The accel brake map_calibrator
publishes diagnostics message depending on the calibration status.
Diagnostic type WARN
indicates that the current accel/brake map is estimated to be inaccurate. In this situation, it is strongly recommended to perform a re-calibration of the accel/brake map.
Status | Diagnostics Type | Diagnostics message | Description |
---|---|---|---|
No calibration required | OK |
“OK” | |
Calibration Required | WARN |
“Accel/brake map Calibration is required.” | The accuracy of current accel/brake map may be low. |
This diagnostics status can be also checked on the following ROS topic.
ros2 topic echo /accel_brake_map_calibrator/output/update_suggest
When the diagnostics type is WARN
, True
is published on this topic and the update of the accel/brake map is suggested.
Evaluation of the accel / brake map accuracy
The accuracy of map is evaluated by the Root Mean Squared Error (RMSE) between the observed acceleration and predicted acceleration.
TERMS:
-
Observed acceleration
: the current vehicle acceleration which is calculated as a derivative value of the wheel speed. -
Predicted acceleration
: the output of the original accel/brake map, which the Autoware is expecting. The value is calculated using the current pedal and velocity.
You can check additional error information with the following topics.
-
/accel_brake_map_calibrator/output/current_map_error
: The error of the original map set in thecsv_path_accel/brake_map
path. The original map is not accurate if this value is large. -
/accel_brake_map_calibrator/output/updated_map_error
: The error of the map calibrated in this node. The calibration quality is low if this value is large. -
/accel_brake_map_calibrator/output/map_error_ratio
: The error ratio between the original map and updated map (ratio = updated / current). If this value is less than 1, it is desirable to update the map.
How to visualize calibration data
The process of calibration can be visualized as below. Since these scripts need the log output of the calibration, the pedal_accel_graph_output
parameter must be set to true while the calibration is running for the visualization.
Visualize plot of relation between acceleration and pedal
The following command shows the plot of used data in the calibration. In each plot of velocity ranges, you can see the distribution of the relationship between pedal and acceleration, and raw data points with colors according to their pitch angles.
ros2 run accel_brake_map_calibrator view_plot.py
Visualize statistics about acceleration/velocity/pedal data
The following command shows the statistics of the calibration:
- mean value
- standard deviation
- number of data
File truncated at 100 lines see the full file
Package Dependencies
System Dependencies
Dependant Packages
Launch files
- launch/accel_brake_map_calibrator.launch.xml
-
- accel_brake_map_calib_param [default: $(find-pkg-share accel_brake_map_calibrator)/config/accel_brake_map_calibrator.param.yaml]
- csv_default_map_dir [default: $(find-pkg-share raw_vehicle_cmd_converter)/data/default/]
- csv_calibrated_map_dir [default: $(find-pkg-share accel_brake_map_calibrator)/config/]
- logger_level [default: info]
- rviz [default: true]
- pedal_accel_graph_output [default: true]
- progress_file_output [default: false]
- use_sim_time [default: false]
- calibration_method [default: each_cell]
Messages
Services
Plugins
Recent questions tagged accel_brake_map_calibrator at Robotics Stack Exchange
Package Summary
Tags | No category tags. |
Version | 0.1.0 |
License | Apache License 2.0 |
Build type | AMENT_CMAKE |
Use | RECOMMENDED |
Repository Summary
Description | |
Checkout URI | https://github.com/ieiauto/autodrrt.git |
VCS Type | git |
VCS Version | main |
Last Updated | 2025-05-30 |
Dev Status | UNKNOWN |
Released | UNRELEASED |
Tags | No category tags. |
Contributing |
Help Wanted (-)
Good First Issues (-) Pull Requests to Review (-) |
Package Description
Additional Links
Maintainers
- Tomoya Kimura
- Taiki Tanaka
- Takeshi Miura
Authors
accel_brake_map_calibrator
The role of this node is to automatically calibrate accel_map.csv
/ brake_map.csv
used in the raw_vehicle_cmd_converter
node.
The base map, which is lexus’s one by default, is updated iteratively with the loaded driving data.
How to calibrate
Launch Calibrator
After launching Autoware, run the accel_brake_map_calibrator
by the following command and then perform autonomous driving. Note: You can collect data with manual driving if it is possible to use the same vehicle interface as during autonomous driving (e.g. using a joystick).
ros2 launch accel_brake_map_calibrator accel_brake_map_calibrator.launch.xml rviz:=true
Or if you want to use rosbag files, run the following commands.
ros2 launch accel_brake_map_calibrator accel_brake_map_calibrator.launch.xml rviz:=true use_sim_time:=true
ros2 bag play <rosbag_file> --clock
During the calibration with setting the parameter progress_file_output
to true, the log file is output in [directory of accel_brake_map_calibrator]/config/ . You can also see accel and brake maps in [directory of accel_brake_map_calibrator]/config/accel_map.csv and [directory of accel_brake_map_calibrator]/config/brake_map.csv after calibration.
Calibration plugin
The rviz:=true
option displays the RViz with a calibration plugin as below.
The current status (velocity and pedal) is shown in the plugin. The color on the current cell varies green/red depending on the current data is valid/invalid. The data that doesn’t satisfy the following conditions are considered invalid and will not be used for estimation since aggressive data (e.g. when the pedal is moving fast) causes bad calibration accuracy.
- The velocity and pedal conditions are within certain ranges from the index values.
- The steer value, pedal speed, pitch value, etc. are less than corresponding thresholds.
- The velocity is higher than a threshold.
The detailed parameters are described in the parameter section.
Note: You don’t need to worry about whether the current state is red or green during calibration. Just keep getting data until all the cells turn red.
The value of each cell in the map is gray at first, and it changes from blue to red as the number of valid data in the cell accumulates. It is preferable to continue the calibration until each cell of the map becomes close to red. In particular, the performance near the stop depends strongly on the velocity of 0 ~ 6m/s range and the pedal value of +0.2 ~ -0.4, range so it is desirable to focus on those areas.
Diagnostics
The accel brake map_calibrator
publishes diagnostics message depending on the calibration status.
Diagnostic type WARN
indicates that the current accel/brake map is estimated to be inaccurate. In this situation, it is strongly recommended to perform a re-calibration of the accel/brake map.
Status | Diagnostics Type | Diagnostics message | Description |
---|---|---|---|
No calibration required | OK |
“OK” | |
Calibration Required | WARN |
“Accel/brake map Calibration is required.” | The accuracy of current accel/brake map may be low. |
This diagnostics status can be also checked on the following ROS topic.
ros2 topic echo /accel_brake_map_calibrator/output/update_suggest
When the diagnostics type is WARN
, True
is published on this topic and the update of the accel/brake map is suggested.
Evaluation of the accel / brake map accuracy
The accuracy of map is evaluated by the Root Mean Squared Error (RMSE) between the observed acceleration and predicted acceleration.
TERMS:
-
Observed acceleration
: the current vehicle acceleration which is calculated as a derivative value of the wheel speed. -
Predicted acceleration
: the output of the original accel/brake map, which the Autoware is expecting. The value is calculated using the current pedal and velocity.
You can check additional error information with the following topics.
-
/accel_brake_map_calibrator/output/current_map_error
: The error of the original map set in thecsv_path_accel/brake_map
path. The original map is not accurate if this value is large. -
/accel_brake_map_calibrator/output/updated_map_error
: The error of the map calibrated in this node. The calibration quality is low if this value is large. -
/accel_brake_map_calibrator/output/map_error_ratio
: The error ratio between the original map and updated map (ratio = updated / current). If this value is less than 1, it is desirable to update the map.
How to visualize calibration data
The process of calibration can be visualized as below. Since these scripts need the log output of the calibration, the pedal_accel_graph_output
parameter must be set to true while the calibration is running for the visualization.
Visualize plot of relation between acceleration and pedal
The following command shows the plot of used data in the calibration. In each plot of velocity ranges, you can see the distribution of the relationship between pedal and acceleration, and raw data points with colors according to their pitch angles.
ros2 run accel_brake_map_calibrator view_plot.py
Visualize statistics about acceleration/velocity/pedal data
The following command shows the statistics of the calibration:
- mean value
- standard deviation
- number of data
File truncated at 100 lines see the full file
Package Dependencies
System Dependencies
Dependant Packages
Launch files
- launch/accel_brake_map_calibrator.launch.xml
-
- accel_brake_map_calib_param [default: $(find-pkg-share accel_brake_map_calibrator)/config/accel_brake_map_calibrator.param.yaml]
- csv_default_map_dir [default: $(find-pkg-share raw_vehicle_cmd_converter)/data/default/]
- csv_calibrated_map_dir [default: $(find-pkg-share accel_brake_map_calibrator)/config/]
- logger_level [default: info]
- rviz [default: true]
- pedal_accel_graph_output [default: true]
- progress_file_output [default: false]
- use_sim_time [default: false]
- calibration_method [default: each_cell]