Package Summary
| Version | 0.53.0 |
| License | Apache License 2.0 |
| Build type | AMENT_CMAKE |
| Use | RECOMMENDED |
Repository Summary
| Description | |
| Checkout URI | https://github.com/autowarefoundation/autoware_universe.git |
| VCS Type | git |
| VCS Version | main |
| Last Updated | 2026-10-23 |
| Dev Status | UNKNOWN |
| Released | UNRELEASED |
| Contributing |
Help Wanted (-)
Good First Issues (-) Pull Requests to Review (-) |
Package Description
Maintainers
- Amadeusz Szymko
- Manato Hirabayashi
- Patiphon Narksri
Authors
- Amadeusz Szymko
autoware_calibration_status_classifier
Purpose
The autoware_calibration_status_classifier package provides real-time LiDAR-camera calibration validation using deep learning inference. It detects miscalibration between LiDAR and camera sensors by analyzing projected point clouds overlaid on camera images through a neural network-based approach.
Inner-workings / Algorithms
The calibration status detection system operates through the following pipeline:
1. Data Preprocessing (CUDA-accelerated)
- Image Undistortion: Corrects camera distortion
- Point Cloud Projection: Projects 3D LiDAR points onto undistorted 2D image plane - adds depth and intensity information
- Morphological Dilation: Enhances point visibility for neural network input
2. Neural Network Inference (TensorRT)
- Input Format: 5-channel normalized data (RGB + depth + intensity)
- Architecture: Deep neural network trained on calibrated/miscalibrated data
- Output: Binary classification with confidence scores for calibration status
3. Runtime Modes
- MANUAL: On-demand validation via service calls
- PERIODIC: Regular validation at configurable intervals
- ACTIVE: Continuous monitoring with synchronized sensor data
Inputs / Outputs
Input
| Name | Type | Description |
|---|---|---|
~/input/linear_velocity |
prerequisite.linear_velocity_check.source parameter |
Vehicle twist for linear velocity check (multiple message types supported) |
~/input/angular_velocity |
prerequisite.angular_velocity_check.source parameter |
Vehicle twist for angular velocity check (multiple message types supported) |
~/input/objects |
prerequisite.objects_check.source parameter |
Detected objects for objects check (multiple message types supported) |
input.cloud_topics |
sensor_msgs::msg::PointCloud2 |
LiDAR point cloud data |
input.image_topics |
sensor_msgs::msg::Image |
Camera image data (BGR8 format) |
| Camera info topics | sensor_msgs::msg::CameraInfo |
Camera intrinsic parameters and distortion coefficients |
Output
| Name | Type | Description |
|---|---|---|
/diagnostics |
diagnostic_msgs::msg::DiagnosticArray |
ROS diagnostics with calibration status |
~/validate_calibration_srv |
std_srvs::srv::Trigger |
Manual validation service (MANUAL mode) |
| Preview image topics | sensor_msgs::msg::Image |
Visualization images with projected points |
Services
| Name | Type | Description |
|---|---|---|
~/input/validate_calibration_srv |
std_srvs::srv::Trigger |
Manual calibration validation request |
Parameters
Node Parameters
{{ json_to_markdown(“sensing/autoware_calibration_status_classifier/schema/calibration_status_classifier.schema.json”) }}
Network Parameters
{{ json_to_markdown(“sensing/autoware_calibration_status_classifier/schema/ml_package_calibration_status_classifier.schema.json”) }}
Assumptions / Known Limits
- Input images must be in BGR8 format (8-bit per channel)
- Input point clouds should contain intensity information (XYZIRC format)
Usage Example
ros2 launch autoware_calibration_status_classifier calibration_status_classifier.launch.xml
Future Extensions / Unimplemented Parts
- Manual runtime mode with detailed response (custom srv)
- Replace filter for objects on the scene counter to objects within the camera FOV counter (raytracing)
- Multithreading for multiple camera-LiDAR pairs
- More filters (e.g. yaw rate)
- cuda_blackboard support
- Replace custom kernels with NPP functions where applicable
References
Changelog for package autoware_calibration_status_classifier
0.53.0 (2026-09-29)
- Merge remote-tracking branch 'origin/main' into prepare-0.53.0-changelog
- fix(design): align the sensing node designs with the packages they describe (#13337) CalibrationStatusClassifier declares a preview_image publisher on a hardcoded per-camera topic that the node no longer creates, and names it as the outcome of the classify process. The point cloud concatenation component is built as concatenate_pointclouds_node.
- refactor(sensing): move node design files into each package (#13105)
- Contributors: Ryohsuke Mitsudome, Taekjin LEE
0.52.0 (2026-06-30)
0.51.0 (2026-05-01)
-
Merge remote-tracking branch 'origin/main' into tmp/bot/bump_version_base
-
feat: default artifact paths to ~/autoware_data/ml_models (#12523) feat(launches,configs): default artifact paths to ~/autoware_data/ml_models Roll every per-package [data_path]{.title-ref} / [model_path]{.title-ref} launch-arg default from [$(env HOME)/autoware_data[/...]]{.title-ref} to [$(env HOME)/autoware_data/ml_models[/...]]{.title-ref} so standalone universe launches resolve artifacts under the new [~/autoware_data/ml_models/]{.title-ref} layout (autowarefoundation/autoware#7068). When invoked through autoware_launch the parent overrides cascade and already pin the new root (autowarefoundation/autoware_launch#1835); this commit closes the gap for users who launch a perception / localization / sensing / planning component directly with [ros2 launch <pkg>]{.title-ref}. 22 launch files updated (one-line default change each):
- e2e/autoware_tensorrt_vad/launch/vad_carla_tiny.launch.xml
- localization/yabloc/yabloc_pose_initializer/launch/yabloc_pose_initializer.launch.xml
- perception/autoware_bevfusion/launch/bevfusion.launch.xml
- perception/autoware_camera_streampetr/launch/streampetr.launch.xml
- perception/autoware_image_projection_based_fusion/launch/pointpainting_fusion.launch.xml
- perception/autoware_lidar_apollo_instance_segmentation/launch/lidar_apollo_instance_segmentation.launch.xml
- perception/autoware_lidar_centerpoint/launch/lidar_centerpoint.launch.xml
- perception/autoware_lidar_frnet/launch/lidar_frnet.launch.xml
- perception/autoware_lidar_transfusion/launch/lidar_transfusion.launch.xml
- perception/autoware_ptv3/launch/ptv3.launch.xml
- perception/autoware_shape_estimation/launch/shape_estimation.launch.xml
- perception/autoware_simpl_prediction/launch/simpl.launch.xml
- perception/autoware_tensorrt_bevdet/launch/tensorrt_bevdet.launch.xml
- perception/autoware_tensorrt_bevformer/launch/bevformer.launch.xml
- perception/autoware_tensorrt_yolox/launch/{yolox_traffic_light_detector,yolox_tiny,yolox_s_plus_opt}.launch.xml
- perception/autoware_traffic_light_classifier/launch/{car,pedestrian}_traffic_light_classifier.launch.xml
- perception/autoware_traffic_light_fine_detector/launch/traffic_light_fine_detector.launch.xml
- planning/autoware_diffusion_planner/launch/diffusion_planner.launch.xml
- sensing/autoware_calibration_status_classifier/launch/calibration_status_classifier.launch.xml Drive-by README and test fixes:
- e2e/autoware_tensorrt_vad/{README.md,docs/design.md}: also migrate the [$HOME/autoware_map/Town01]{.title-ref} examples to [$HOME/autoware_data/maps/Town01]{.title-ref}.
- localization/yabloc/{README.md,yabloc_pose_initializer/README.md}: also migrate [$HOME/autoware_map/sample-map-rosbag]{.title-ref} to [$HOME/autoware_data/maps/demos/sample-map-rosbag]{.title-ref}.
- control/autoware_smart_mpc_trajectory_follower/README.md: migrate the [map_path:=$HOME/autoware_map/sample-map-planning]{.title-ref} example to [$HOME/autoware_data/maps/demos/sample-map-planning]{.title-ref}.
- simulator/autoware_carla_interface/README.md: migrate every [$HOME/autoware_map/Town01/...]{.title-ref} reference to [$HOME/autoware_data/maps/Town01/...]{.title-ref}.
- perception/{autoware_bevfusion,autoware_image_projection_based_fusion,autoware_lidar_centerpoint,autoware_tensorrt_bevformer}/README.md: copy-paste examples updated to [~/autoware_data/ml_models/<pkg>]{.title-ref}.
- perception/autoware_camera_streampetr/config/ml_package_camera_streampetr.param.yaml: header comment updated.
- planning/autoware_diffusion_planner/README.md: prerequisites snippet updated.
- sensing/autoware_calibration_status_classifier/test/{test_model_inference,test_calibration_status_classifier}.cpp: hardcoded fallback ONNX path updated. Users on the legacy layout can pin the old root with [data_path:=$HOME/autoware_data]{.title-ref} (or the per-package equivalent) on the command line. Refs: https://github.com/autowarefoundation/autoware/issues/7068
-
feat(autoware_calibration_status_classifier): add angular velocity filter and refine filters design
File truncated at 100 lines see the full file
Package Dependencies
System Dependencies
| Name |
|---|
| libopencv-dev |
Dependant Packages
Launch files
- launch/calibration_status_classifier.launch.xml
-
- input_linear_velocity [default: /sensing/vehicle_velocity_converter/twist_with_covariance]
- input_angular_velocity [default: /sensing/vehicle_velocity_converter/twist_with_covariance]
- input_objects [default: /perception/object_recognition/objects]
- validate_calibration_srv [default: validate_calibration]
- data_path [default: $(env HOME)/autoware_data/ml_models]
- model_name [default: calibration_status_classifier]
- model_path [default: $(var data_path)/calibration_status_classifier]
- model_param_path [default: $(find-pkg-share autoware_calibration_status_classifier)/config/$(var model_name).param.yaml]
- ml_package_param_path [default: $(var model_path)/ml_package_$(var model_name).param.yaml]
- build_only [default: false]
- use_sim_time [default: true]
- decompressor_param_file [default: $(find-pkg-share autoware_image_transport_decompressor)/config/image_transport_decompressor.param.yaml]
Messages
Services
Plugins
Recent questions tagged autoware_calibration_status_classifier at Robotics Stack Exchange
Package Summary
| Version | 0.53.0 |
| License | Apache License 2.0 |
| Build type | AMENT_CMAKE |
| Use | RECOMMENDED |
Repository Summary
| Description | |
| Checkout URI | https://github.com/autowarefoundation/autoware_universe.git |
| VCS Type | git |
| VCS Version | main |
| Last Updated | 2026-10-23 |
| Dev Status | UNKNOWN |
| Released | UNRELEASED |
| Contributing |
Help Wanted (-)
Good First Issues (-) Pull Requests to Review (-) |
Package Description
Maintainers
- Amadeusz Szymko
- Manato Hirabayashi
- Patiphon Narksri
Authors
- Amadeusz Szymko
autoware_calibration_status_classifier
Purpose
The autoware_calibration_status_classifier package provides real-time LiDAR-camera calibration validation using deep learning inference. It detects miscalibration between LiDAR and camera sensors by analyzing projected point clouds overlaid on camera images through a neural network-based approach.
Inner-workings / Algorithms
The calibration status detection system operates through the following pipeline:
1. Data Preprocessing (CUDA-accelerated)
- Image Undistortion: Corrects camera distortion
- Point Cloud Projection: Projects 3D LiDAR points onto undistorted 2D image plane - adds depth and intensity information
- Morphological Dilation: Enhances point visibility for neural network input
2. Neural Network Inference (TensorRT)
- Input Format: 5-channel normalized data (RGB + depth + intensity)
- Architecture: Deep neural network trained on calibrated/miscalibrated data
- Output: Binary classification with confidence scores for calibration status
3. Runtime Modes
- MANUAL: On-demand validation via service calls
- PERIODIC: Regular validation at configurable intervals
- ACTIVE: Continuous monitoring with synchronized sensor data
Inputs / Outputs
Input
| Name | Type | Description |
|---|---|---|
~/input/linear_velocity |
prerequisite.linear_velocity_check.source parameter |
Vehicle twist for linear velocity check (multiple message types supported) |
~/input/angular_velocity |
prerequisite.angular_velocity_check.source parameter |
Vehicle twist for angular velocity check (multiple message types supported) |
~/input/objects |
prerequisite.objects_check.source parameter |
Detected objects for objects check (multiple message types supported) |
input.cloud_topics |
sensor_msgs::msg::PointCloud2 |
LiDAR point cloud data |
input.image_topics |
sensor_msgs::msg::Image |
Camera image data (BGR8 format) |
| Camera info topics | sensor_msgs::msg::CameraInfo |
Camera intrinsic parameters and distortion coefficients |
Output
| Name | Type | Description |
|---|---|---|
/diagnostics |
diagnostic_msgs::msg::DiagnosticArray |
ROS diagnostics with calibration status |
~/validate_calibration_srv |
std_srvs::srv::Trigger |
Manual validation service (MANUAL mode) |
| Preview image topics | sensor_msgs::msg::Image |
Visualization images with projected points |
Services
| Name | Type | Description |
|---|---|---|
~/input/validate_calibration_srv |
std_srvs::srv::Trigger |
Manual calibration validation request |
Parameters
Node Parameters
{{ json_to_markdown(“sensing/autoware_calibration_status_classifier/schema/calibration_status_classifier.schema.json”) }}
Network Parameters
{{ json_to_markdown(“sensing/autoware_calibration_status_classifier/schema/ml_package_calibration_status_classifier.schema.json”) }}
Assumptions / Known Limits
- Input images must be in BGR8 format (8-bit per channel)
- Input point clouds should contain intensity information (XYZIRC format)
Usage Example
ros2 launch autoware_calibration_status_classifier calibration_status_classifier.launch.xml
Future Extensions / Unimplemented Parts
- Manual runtime mode with detailed response (custom srv)
- Replace filter for objects on the scene counter to objects within the camera FOV counter (raytracing)
- Multithreading for multiple camera-LiDAR pairs
- More filters (e.g. yaw rate)
- cuda_blackboard support
- Replace custom kernels with NPP functions where applicable
References
Changelog for package autoware_calibration_status_classifier
0.53.0 (2026-09-29)
- Merge remote-tracking branch 'origin/main' into prepare-0.53.0-changelog
- fix(design): align the sensing node designs with the packages they describe (#13337) CalibrationStatusClassifier declares a preview_image publisher on a hardcoded per-camera topic that the node no longer creates, and names it as the outcome of the classify process. The point cloud concatenation component is built as concatenate_pointclouds_node.
- refactor(sensing): move node design files into each package (#13105)
- Contributors: Ryohsuke Mitsudome, Taekjin LEE
0.52.0 (2026-06-30)
0.51.0 (2026-05-01)
-
Merge remote-tracking branch 'origin/main' into tmp/bot/bump_version_base
-
feat: default artifact paths to ~/autoware_data/ml_models (#12523) feat(launches,configs): default artifact paths to ~/autoware_data/ml_models Roll every per-package [data_path]{.title-ref} / [model_path]{.title-ref} launch-arg default from [$(env HOME)/autoware_data[/...]]{.title-ref} to [$(env HOME)/autoware_data/ml_models[/...]]{.title-ref} so standalone universe launches resolve artifacts under the new [~/autoware_data/ml_models/]{.title-ref} layout (autowarefoundation/autoware#7068). When invoked through autoware_launch the parent overrides cascade and already pin the new root (autowarefoundation/autoware_launch#1835); this commit closes the gap for users who launch a perception / localization / sensing / planning component directly with [ros2 launch <pkg>]{.title-ref}. 22 launch files updated (one-line default change each):
- e2e/autoware_tensorrt_vad/launch/vad_carla_tiny.launch.xml
- localization/yabloc/yabloc_pose_initializer/launch/yabloc_pose_initializer.launch.xml
- perception/autoware_bevfusion/launch/bevfusion.launch.xml
- perception/autoware_camera_streampetr/launch/streampetr.launch.xml
- perception/autoware_image_projection_based_fusion/launch/pointpainting_fusion.launch.xml
- perception/autoware_lidar_apollo_instance_segmentation/launch/lidar_apollo_instance_segmentation.launch.xml
- perception/autoware_lidar_centerpoint/launch/lidar_centerpoint.launch.xml
- perception/autoware_lidar_frnet/launch/lidar_frnet.launch.xml
- perception/autoware_lidar_transfusion/launch/lidar_transfusion.launch.xml
- perception/autoware_ptv3/launch/ptv3.launch.xml
- perception/autoware_shape_estimation/launch/shape_estimation.launch.xml
- perception/autoware_simpl_prediction/launch/simpl.launch.xml
- perception/autoware_tensorrt_bevdet/launch/tensorrt_bevdet.launch.xml
- perception/autoware_tensorrt_bevformer/launch/bevformer.launch.xml
- perception/autoware_tensorrt_yolox/launch/{yolox_traffic_light_detector,yolox_tiny,yolox_s_plus_opt}.launch.xml
- perception/autoware_traffic_light_classifier/launch/{car,pedestrian}_traffic_light_classifier.launch.xml
- perception/autoware_traffic_light_fine_detector/launch/traffic_light_fine_detector.launch.xml
- planning/autoware_diffusion_planner/launch/diffusion_planner.launch.xml
- sensing/autoware_calibration_status_classifier/launch/calibration_status_classifier.launch.xml Drive-by README and test fixes:
- e2e/autoware_tensorrt_vad/{README.md,docs/design.md}: also migrate the [$HOME/autoware_map/Town01]{.title-ref} examples to [$HOME/autoware_data/maps/Town01]{.title-ref}.
- localization/yabloc/{README.md,yabloc_pose_initializer/README.md}: also migrate [$HOME/autoware_map/sample-map-rosbag]{.title-ref} to [$HOME/autoware_data/maps/demos/sample-map-rosbag]{.title-ref}.
- control/autoware_smart_mpc_trajectory_follower/README.md: migrate the [map_path:=$HOME/autoware_map/sample-map-planning]{.title-ref} example to [$HOME/autoware_data/maps/demos/sample-map-planning]{.title-ref}.
- simulator/autoware_carla_interface/README.md: migrate every [$HOME/autoware_map/Town01/...]{.title-ref} reference to [$HOME/autoware_data/maps/Town01/...]{.title-ref}.
- perception/{autoware_bevfusion,autoware_image_projection_based_fusion,autoware_lidar_centerpoint,autoware_tensorrt_bevformer}/README.md: copy-paste examples updated to [~/autoware_data/ml_models/<pkg>]{.title-ref}.
- perception/autoware_camera_streampetr/config/ml_package_camera_streampetr.param.yaml: header comment updated.
- planning/autoware_diffusion_planner/README.md: prerequisites snippet updated.
- sensing/autoware_calibration_status_classifier/test/{test_model_inference,test_calibration_status_classifier}.cpp: hardcoded fallback ONNX path updated. Users on the legacy layout can pin the old root with [data_path:=$HOME/autoware_data]{.title-ref} (or the per-package equivalent) on the command line. Refs: https://github.com/autowarefoundation/autoware/issues/7068
-
feat(autoware_calibration_status_classifier): add angular velocity filter and refine filters design
File truncated at 100 lines see the full file
Package Dependencies
System Dependencies
| Name |
|---|
| libopencv-dev |
Dependant Packages
Launch files
- launch/calibration_status_classifier.launch.xml
-
- input_linear_velocity [default: /sensing/vehicle_velocity_converter/twist_with_covariance]
- input_angular_velocity [default: /sensing/vehicle_velocity_converter/twist_with_covariance]
- input_objects [default: /perception/object_recognition/objects]
- validate_calibration_srv [default: validate_calibration]
- data_path [default: $(env HOME)/autoware_data/ml_models]
- model_name [default: calibration_status_classifier]
- model_path [default: $(var data_path)/calibration_status_classifier]
- model_param_path [default: $(find-pkg-share autoware_calibration_status_classifier)/config/$(var model_name).param.yaml]
- ml_package_param_path [default: $(var model_path)/ml_package_$(var model_name).param.yaml]
- build_only [default: false]
- use_sim_time [default: true]
- decompressor_param_file [default: $(find-pkg-share autoware_image_transport_decompressor)/config/image_transport_decompressor.param.yaml]
Messages
Services
Plugins
Recent questions tagged autoware_calibration_status_classifier at Robotics Stack Exchange
Package Summary
| Version | 0.53.0 |
| License | Apache License 2.0 |
| Build type | AMENT_CMAKE |
| Use | RECOMMENDED |
Repository Summary
| Description | |
| Checkout URI | https://github.com/autowarefoundation/autoware_universe.git |
| VCS Type | git |
| VCS Version | main |
| Last Updated | 2026-10-23 |
| Dev Status | UNKNOWN |
| Released | UNRELEASED |
| Contributing |
Help Wanted (-)
Good First Issues (-) Pull Requests to Review (-) |
Package Description
Maintainers
- Amadeusz Szymko
- Manato Hirabayashi
- Patiphon Narksri
Authors
- Amadeusz Szymko
autoware_calibration_status_classifier
Purpose
The autoware_calibration_status_classifier package provides real-time LiDAR-camera calibration validation using deep learning inference. It detects miscalibration between LiDAR and camera sensors by analyzing projected point clouds overlaid on camera images through a neural network-based approach.
Inner-workings / Algorithms
The calibration status detection system operates through the following pipeline:
1. Data Preprocessing (CUDA-accelerated)
- Image Undistortion: Corrects camera distortion
- Point Cloud Projection: Projects 3D LiDAR points onto undistorted 2D image plane - adds depth and intensity information
- Morphological Dilation: Enhances point visibility for neural network input
2. Neural Network Inference (TensorRT)
- Input Format: 5-channel normalized data (RGB + depth + intensity)
- Architecture: Deep neural network trained on calibrated/miscalibrated data
- Output: Binary classification with confidence scores for calibration status
3. Runtime Modes
- MANUAL: On-demand validation via service calls
- PERIODIC: Regular validation at configurable intervals
- ACTIVE: Continuous monitoring with synchronized sensor data
Inputs / Outputs
Input
| Name | Type | Description |
|---|---|---|
~/input/linear_velocity |
prerequisite.linear_velocity_check.source parameter |
Vehicle twist for linear velocity check (multiple message types supported) |
~/input/angular_velocity |
prerequisite.angular_velocity_check.source parameter |
Vehicle twist for angular velocity check (multiple message types supported) |
~/input/objects |
prerequisite.objects_check.source parameter |
Detected objects for objects check (multiple message types supported) |
input.cloud_topics |
sensor_msgs::msg::PointCloud2 |
LiDAR point cloud data |
input.image_topics |
sensor_msgs::msg::Image |
Camera image data (BGR8 format) |
| Camera info topics | sensor_msgs::msg::CameraInfo |
Camera intrinsic parameters and distortion coefficients |
Output
| Name | Type | Description |
|---|---|---|
/diagnostics |
diagnostic_msgs::msg::DiagnosticArray |
ROS diagnostics with calibration status |
~/validate_calibration_srv |
std_srvs::srv::Trigger |
Manual validation service (MANUAL mode) |
| Preview image topics | sensor_msgs::msg::Image |
Visualization images with projected points |
Services
| Name | Type | Description |
|---|---|---|
~/input/validate_calibration_srv |
std_srvs::srv::Trigger |
Manual calibration validation request |
Parameters
Node Parameters
{{ json_to_markdown(“sensing/autoware_calibration_status_classifier/schema/calibration_status_classifier.schema.json”) }}
Network Parameters
{{ json_to_markdown(“sensing/autoware_calibration_status_classifier/schema/ml_package_calibration_status_classifier.schema.json”) }}
Assumptions / Known Limits
- Input images must be in BGR8 format (8-bit per channel)
- Input point clouds should contain intensity information (XYZIRC format)
Usage Example
ros2 launch autoware_calibration_status_classifier calibration_status_classifier.launch.xml
Future Extensions / Unimplemented Parts
- Manual runtime mode with detailed response (custom srv)
- Replace filter for objects on the scene counter to objects within the camera FOV counter (raytracing)
- Multithreading for multiple camera-LiDAR pairs
- More filters (e.g. yaw rate)
- cuda_blackboard support
- Replace custom kernels with NPP functions where applicable
References
Changelog for package autoware_calibration_status_classifier
0.53.0 (2026-09-29)
- Merge remote-tracking branch 'origin/main' into prepare-0.53.0-changelog
- fix(design): align the sensing node designs with the packages they describe (#13337) CalibrationStatusClassifier declares a preview_image publisher on a hardcoded per-camera topic that the node no longer creates, and names it as the outcome of the classify process. The point cloud concatenation component is built as concatenate_pointclouds_node.
- refactor(sensing): move node design files into each package (#13105)
- Contributors: Ryohsuke Mitsudome, Taekjin LEE
0.52.0 (2026-06-30)
0.51.0 (2026-05-01)
-
Merge remote-tracking branch 'origin/main' into tmp/bot/bump_version_base
-
feat: default artifact paths to ~/autoware_data/ml_models (#12523) feat(launches,configs): default artifact paths to ~/autoware_data/ml_models Roll every per-package [data_path]{.title-ref} / [model_path]{.title-ref} launch-arg default from [$(env HOME)/autoware_data[/...]]{.title-ref} to [$(env HOME)/autoware_data/ml_models[/...]]{.title-ref} so standalone universe launches resolve artifacts under the new [~/autoware_data/ml_models/]{.title-ref} layout (autowarefoundation/autoware#7068). When invoked through autoware_launch the parent overrides cascade and already pin the new root (autowarefoundation/autoware_launch#1835); this commit closes the gap for users who launch a perception / localization / sensing / planning component directly with [ros2 launch <pkg>]{.title-ref}. 22 launch files updated (one-line default change each):
- e2e/autoware_tensorrt_vad/launch/vad_carla_tiny.launch.xml
- localization/yabloc/yabloc_pose_initializer/launch/yabloc_pose_initializer.launch.xml
- perception/autoware_bevfusion/launch/bevfusion.launch.xml
- perception/autoware_camera_streampetr/launch/streampetr.launch.xml
- perception/autoware_image_projection_based_fusion/launch/pointpainting_fusion.launch.xml
- perception/autoware_lidar_apollo_instance_segmentation/launch/lidar_apollo_instance_segmentation.launch.xml
- perception/autoware_lidar_centerpoint/launch/lidar_centerpoint.launch.xml
- perception/autoware_lidar_frnet/launch/lidar_frnet.launch.xml
- perception/autoware_lidar_transfusion/launch/lidar_transfusion.launch.xml
- perception/autoware_ptv3/launch/ptv3.launch.xml
- perception/autoware_shape_estimation/launch/shape_estimation.launch.xml
- perception/autoware_simpl_prediction/launch/simpl.launch.xml
- perception/autoware_tensorrt_bevdet/launch/tensorrt_bevdet.launch.xml
- perception/autoware_tensorrt_bevformer/launch/bevformer.launch.xml
- perception/autoware_tensorrt_yolox/launch/{yolox_traffic_light_detector,yolox_tiny,yolox_s_plus_opt}.launch.xml
- perception/autoware_traffic_light_classifier/launch/{car,pedestrian}_traffic_light_classifier.launch.xml
- perception/autoware_traffic_light_fine_detector/launch/traffic_light_fine_detector.launch.xml
- planning/autoware_diffusion_planner/launch/diffusion_planner.launch.xml
- sensing/autoware_calibration_status_classifier/launch/calibration_status_classifier.launch.xml Drive-by README and test fixes:
- e2e/autoware_tensorrt_vad/{README.md,docs/design.md}: also migrate the [$HOME/autoware_map/Town01]{.title-ref} examples to [$HOME/autoware_data/maps/Town01]{.title-ref}.
- localization/yabloc/{README.md,yabloc_pose_initializer/README.md}: also migrate [$HOME/autoware_map/sample-map-rosbag]{.title-ref} to [$HOME/autoware_data/maps/demos/sample-map-rosbag]{.title-ref}.
- control/autoware_smart_mpc_trajectory_follower/README.md: migrate the [map_path:=$HOME/autoware_map/sample-map-planning]{.title-ref} example to [$HOME/autoware_data/maps/demos/sample-map-planning]{.title-ref}.
- simulator/autoware_carla_interface/README.md: migrate every [$HOME/autoware_map/Town01/...]{.title-ref} reference to [$HOME/autoware_data/maps/Town01/...]{.title-ref}.
- perception/{autoware_bevfusion,autoware_image_projection_based_fusion,autoware_lidar_centerpoint,autoware_tensorrt_bevformer}/README.md: copy-paste examples updated to [~/autoware_data/ml_models/<pkg>]{.title-ref}.
- perception/autoware_camera_streampetr/config/ml_package_camera_streampetr.param.yaml: header comment updated.
- planning/autoware_diffusion_planner/README.md: prerequisites snippet updated.
- sensing/autoware_calibration_status_classifier/test/{test_model_inference,test_calibration_status_classifier}.cpp: hardcoded fallback ONNX path updated. Users on the legacy layout can pin the old root with [data_path:=$HOME/autoware_data]{.title-ref} (or the per-package equivalent) on the command line. Refs: https://github.com/autowarefoundation/autoware/issues/7068
-
feat(autoware_calibration_status_classifier): add angular velocity filter and refine filters design
File truncated at 100 lines see the full file
Package Dependencies
System Dependencies
| Name |
|---|
| libopencv-dev |
Dependant Packages
Launch files
- launch/calibration_status_classifier.launch.xml
-
- input_linear_velocity [default: /sensing/vehicle_velocity_converter/twist_with_covariance]
- input_angular_velocity [default: /sensing/vehicle_velocity_converter/twist_with_covariance]
- input_objects [default: /perception/object_recognition/objects]
- validate_calibration_srv [default: validate_calibration]
- data_path [default: $(env HOME)/autoware_data/ml_models]
- model_name [default: calibration_status_classifier]
- model_path [default: $(var data_path)/calibration_status_classifier]
- model_param_path [default: $(find-pkg-share autoware_calibration_status_classifier)/config/$(var model_name).param.yaml]
- ml_package_param_path [default: $(var model_path)/ml_package_$(var model_name).param.yaml]
- build_only [default: false]
- use_sim_time [default: true]
- decompressor_param_file [default: $(find-pkg-share autoware_image_transport_decompressor)/config/image_transport_decompressor.param.yaml]
Messages
Services
Plugins
Recent questions tagged autoware_calibration_status_classifier at Robotics Stack Exchange
Package Summary
| Version | 0.53.0 |
| License | Apache License 2.0 |
| Build type | AMENT_CMAKE |
| Use | RECOMMENDED |
Repository Summary
| Description | |
| Checkout URI | https://github.com/autowarefoundation/autoware_universe.git |
| VCS Type | git |
| VCS Version | main |
| Last Updated | 2026-10-23 |
| Dev Status | UNKNOWN |
| Released | UNRELEASED |
| Contributing |
Help Wanted (-)
Good First Issues (-) Pull Requests to Review (-) |
Package Description
Maintainers
- Amadeusz Szymko
- Manato Hirabayashi
- Patiphon Narksri
Authors
- Amadeusz Szymko
autoware_calibration_status_classifier
Purpose
The autoware_calibration_status_classifier package provides real-time LiDAR-camera calibration validation using deep learning inference. It detects miscalibration between LiDAR and camera sensors by analyzing projected point clouds overlaid on camera images through a neural network-based approach.
Inner-workings / Algorithms
The calibration status detection system operates through the following pipeline:
1. Data Preprocessing (CUDA-accelerated)
- Image Undistortion: Corrects camera distortion
- Point Cloud Projection: Projects 3D LiDAR points onto undistorted 2D image plane - adds depth and intensity information
- Morphological Dilation: Enhances point visibility for neural network input
2. Neural Network Inference (TensorRT)
- Input Format: 5-channel normalized data (RGB + depth + intensity)
- Architecture: Deep neural network trained on calibrated/miscalibrated data
- Output: Binary classification with confidence scores for calibration status
3. Runtime Modes
- MANUAL: On-demand validation via service calls
- PERIODIC: Regular validation at configurable intervals
- ACTIVE: Continuous monitoring with synchronized sensor data
Inputs / Outputs
Input
| Name | Type | Description |
|---|---|---|
~/input/linear_velocity |
prerequisite.linear_velocity_check.source parameter |
Vehicle twist for linear velocity check (multiple message types supported) |
~/input/angular_velocity |
prerequisite.angular_velocity_check.source parameter |
Vehicle twist for angular velocity check (multiple message types supported) |
~/input/objects |
prerequisite.objects_check.source parameter |
Detected objects for objects check (multiple message types supported) |
input.cloud_topics |
sensor_msgs::msg::PointCloud2 |
LiDAR point cloud data |
input.image_topics |
sensor_msgs::msg::Image |
Camera image data (BGR8 format) |
| Camera info topics | sensor_msgs::msg::CameraInfo |
Camera intrinsic parameters and distortion coefficients |
Output
| Name | Type | Description |
|---|---|---|
/diagnostics |
diagnostic_msgs::msg::DiagnosticArray |
ROS diagnostics with calibration status |
~/validate_calibration_srv |
std_srvs::srv::Trigger |
Manual validation service (MANUAL mode) |
| Preview image topics | sensor_msgs::msg::Image |
Visualization images with projected points |
Services
| Name | Type | Description |
|---|---|---|
~/input/validate_calibration_srv |
std_srvs::srv::Trigger |
Manual calibration validation request |
Parameters
Node Parameters
{{ json_to_markdown(“sensing/autoware_calibration_status_classifier/schema/calibration_status_classifier.schema.json”) }}
Network Parameters
{{ json_to_markdown(“sensing/autoware_calibration_status_classifier/schema/ml_package_calibration_status_classifier.schema.json”) }}
Assumptions / Known Limits
- Input images must be in BGR8 format (8-bit per channel)
- Input point clouds should contain intensity information (XYZIRC format)
Usage Example
ros2 launch autoware_calibration_status_classifier calibration_status_classifier.launch.xml
Future Extensions / Unimplemented Parts
- Manual runtime mode with detailed response (custom srv)
- Replace filter for objects on the scene counter to objects within the camera FOV counter (raytracing)
- Multithreading for multiple camera-LiDAR pairs
- More filters (e.g. yaw rate)
- cuda_blackboard support
- Replace custom kernels with NPP functions where applicable
References
Changelog for package autoware_calibration_status_classifier
0.53.0 (2026-09-29)
- Merge remote-tracking branch 'origin/main' into prepare-0.53.0-changelog
- fix(design): align the sensing node designs with the packages they describe (#13337) CalibrationStatusClassifier declares a preview_image publisher on a hardcoded per-camera topic that the node no longer creates, and names it as the outcome of the classify process. The point cloud concatenation component is built as concatenate_pointclouds_node.
- refactor(sensing): move node design files into each package (#13105)
- Contributors: Ryohsuke Mitsudome, Taekjin LEE
0.52.0 (2026-06-30)
0.51.0 (2026-05-01)
-
Merge remote-tracking branch 'origin/main' into tmp/bot/bump_version_base
-
feat: default artifact paths to ~/autoware_data/ml_models (#12523) feat(launches,configs): default artifact paths to ~/autoware_data/ml_models Roll every per-package [data_path]{.title-ref} / [model_path]{.title-ref} launch-arg default from [$(env HOME)/autoware_data[/...]]{.title-ref} to [$(env HOME)/autoware_data/ml_models[/...]]{.title-ref} so standalone universe launches resolve artifacts under the new [~/autoware_data/ml_models/]{.title-ref} layout (autowarefoundation/autoware#7068). When invoked through autoware_launch the parent overrides cascade and already pin the new root (autowarefoundation/autoware_launch#1835); this commit closes the gap for users who launch a perception / localization / sensing / planning component directly with [ros2 launch <pkg>]{.title-ref}. 22 launch files updated (one-line default change each):
- e2e/autoware_tensorrt_vad/launch/vad_carla_tiny.launch.xml
- localization/yabloc/yabloc_pose_initializer/launch/yabloc_pose_initializer.launch.xml
- perception/autoware_bevfusion/launch/bevfusion.launch.xml
- perception/autoware_camera_streampetr/launch/streampetr.launch.xml
- perception/autoware_image_projection_based_fusion/launch/pointpainting_fusion.launch.xml
- perception/autoware_lidar_apollo_instance_segmentation/launch/lidar_apollo_instance_segmentation.launch.xml
- perception/autoware_lidar_centerpoint/launch/lidar_centerpoint.launch.xml
- perception/autoware_lidar_frnet/launch/lidar_frnet.launch.xml
- perception/autoware_lidar_transfusion/launch/lidar_transfusion.launch.xml
- perception/autoware_ptv3/launch/ptv3.launch.xml
- perception/autoware_shape_estimation/launch/shape_estimation.launch.xml
- perception/autoware_simpl_prediction/launch/simpl.launch.xml
- perception/autoware_tensorrt_bevdet/launch/tensorrt_bevdet.launch.xml
- perception/autoware_tensorrt_bevformer/launch/bevformer.launch.xml
- perception/autoware_tensorrt_yolox/launch/{yolox_traffic_light_detector,yolox_tiny,yolox_s_plus_opt}.launch.xml
- perception/autoware_traffic_light_classifier/launch/{car,pedestrian}_traffic_light_classifier.launch.xml
- perception/autoware_traffic_light_fine_detector/launch/traffic_light_fine_detector.launch.xml
- planning/autoware_diffusion_planner/launch/diffusion_planner.launch.xml
- sensing/autoware_calibration_status_classifier/launch/calibration_status_classifier.launch.xml Drive-by README and test fixes:
- e2e/autoware_tensorrt_vad/{README.md,docs/design.md}: also migrate the [$HOME/autoware_map/Town01]{.title-ref} examples to [$HOME/autoware_data/maps/Town01]{.title-ref}.
- localization/yabloc/{README.md,yabloc_pose_initializer/README.md}: also migrate [$HOME/autoware_map/sample-map-rosbag]{.title-ref} to [$HOME/autoware_data/maps/demos/sample-map-rosbag]{.title-ref}.
- control/autoware_smart_mpc_trajectory_follower/README.md: migrate the [map_path:=$HOME/autoware_map/sample-map-planning]{.title-ref} example to [$HOME/autoware_data/maps/demos/sample-map-planning]{.title-ref}.
- simulator/autoware_carla_interface/README.md: migrate every [$HOME/autoware_map/Town01/...]{.title-ref} reference to [$HOME/autoware_data/maps/Town01/...]{.title-ref}.
- perception/{autoware_bevfusion,autoware_image_projection_based_fusion,autoware_lidar_centerpoint,autoware_tensorrt_bevformer}/README.md: copy-paste examples updated to [~/autoware_data/ml_models/<pkg>]{.title-ref}.
- perception/autoware_camera_streampetr/config/ml_package_camera_streampetr.param.yaml: header comment updated.
- planning/autoware_diffusion_planner/README.md: prerequisites snippet updated.
- sensing/autoware_calibration_status_classifier/test/{test_model_inference,test_calibration_status_classifier}.cpp: hardcoded fallback ONNX path updated. Users on the legacy layout can pin the old root with [data_path:=$HOME/autoware_data]{.title-ref} (or the per-package equivalent) on the command line. Refs: https://github.com/autowarefoundation/autoware/issues/7068
-
feat(autoware_calibration_status_classifier): add angular velocity filter and refine filters design
File truncated at 100 lines see the full file
Package Dependencies
System Dependencies
| Name |
|---|
| libopencv-dev |
Dependant Packages
Launch files
- launch/calibration_status_classifier.launch.xml
-
- input_linear_velocity [default: /sensing/vehicle_velocity_converter/twist_with_covariance]
- input_angular_velocity [default: /sensing/vehicle_velocity_converter/twist_with_covariance]
- input_objects [default: /perception/object_recognition/objects]
- validate_calibration_srv [default: validate_calibration]
- data_path [default: $(env HOME)/autoware_data/ml_models]
- model_name [default: calibration_status_classifier]
- model_path [default: $(var data_path)/calibration_status_classifier]
- model_param_path [default: $(find-pkg-share autoware_calibration_status_classifier)/config/$(var model_name).param.yaml]
- ml_package_param_path [default: $(var model_path)/ml_package_$(var model_name).param.yaml]
- build_only [default: false]
- use_sim_time [default: true]
- decompressor_param_file [default: $(find-pkg-share autoware_image_transport_decompressor)/config/image_transport_decompressor.param.yaml]
Messages
Services
Plugins
Recent questions tagged autoware_calibration_status_classifier at Robotics Stack Exchange
Package Summary
| Version | 0.53.0 |
| License | Apache License 2.0 |
| Build type | AMENT_CMAKE |
| Use | RECOMMENDED |
Repository Summary
| Description | |
| Checkout URI | https://github.com/autowarefoundation/autoware_universe.git |
| VCS Type | git |
| VCS Version | main |
| Last Updated | 2026-10-23 |
| Dev Status | UNKNOWN |
| Released | UNRELEASED |
| Contributing |
Help Wanted (-)
Good First Issues (-) Pull Requests to Review (-) |
Package Description
Maintainers
- Amadeusz Szymko
- Manato Hirabayashi
- Patiphon Narksri
Authors
- Amadeusz Szymko
autoware_calibration_status_classifier
Purpose
The autoware_calibration_status_classifier package provides real-time LiDAR-camera calibration validation using deep learning inference. It detects miscalibration between LiDAR and camera sensors by analyzing projected point clouds overlaid on camera images through a neural network-based approach.
Inner-workings / Algorithms
The calibration status detection system operates through the following pipeline:
1. Data Preprocessing (CUDA-accelerated)
- Image Undistortion: Corrects camera distortion
- Point Cloud Projection: Projects 3D LiDAR points onto undistorted 2D image plane - adds depth and intensity information
- Morphological Dilation: Enhances point visibility for neural network input
2. Neural Network Inference (TensorRT)
- Input Format: 5-channel normalized data (RGB + depth + intensity)
- Architecture: Deep neural network trained on calibrated/miscalibrated data
- Output: Binary classification with confidence scores for calibration status
3. Runtime Modes
- MANUAL: On-demand validation via service calls
- PERIODIC: Regular validation at configurable intervals
- ACTIVE: Continuous monitoring with synchronized sensor data
Inputs / Outputs
Input
| Name | Type | Description |
|---|---|---|
~/input/linear_velocity |
prerequisite.linear_velocity_check.source parameter |
Vehicle twist for linear velocity check (multiple message types supported) |
~/input/angular_velocity |
prerequisite.angular_velocity_check.source parameter |
Vehicle twist for angular velocity check (multiple message types supported) |
~/input/objects |
prerequisite.objects_check.source parameter |
Detected objects for objects check (multiple message types supported) |
input.cloud_topics |
sensor_msgs::msg::PointCloud2 |
LiDAR point cloud data |
input.image_topics |
sensor_msgs::msg::Image |
Camera image data (BGR8 format) |
| Camera info topics | sensor_msgs::msg::CameraInfo |
Camera intrinsic parameters and distortion coefficients |
Output
| Name | Type | Description |
|---|---|---|
/diagnostics |
diagnostic_msgs::msg::DiagnosticArray |
ROS diagnostics with calibration status |
~/validate_calibration_srv |
std_srvs::srv::Trigger |
Manual validation service (MANUAL mode) |
| Preview image topics | sensor_msgs::msg::Image |
Visualization images with projected points |
Services
| Name | Type | Description |
|---|---|---|
~/input/validate_calibration_srv |
std_srvs::srv::Trigger |
Manual calibration validation request |
Parameters
Node Parameters
{{ json_to_markdown(“sensing/autoware_calibration_status_classifier/schema/calibration_status_classifier.schema.json”) }}
Network Parameters
{{ json_to_markdown(“sensing/autoware_calibration_status_classifier/schema/ml_package_calibration_status_classifier.schema.json”) }}
Assumptions / Known Limits
- Input images must be in BGR8 format (8-bit per channel)
- Input point clouds should contain intensity information (XYZIRC format)
Usage Example
ros2 launch autoware_calibration_status_classifier calibration_status_classifier.launch.xml
Future Extensions / Unimplemented Parts
- Manual runtime mode with detailed response (custom srv)
- Replace filter for objects on the scene counter to objects within the camera FOV counter (raytracing)
- Multithreading for multiple camera-LiDAR pairs
- More filters (e.g. yaw rate)
- cuda_blackboard support
- Replace custom kernels with NPP functions where applicable
References
Changelog for package autoware_calibration_status_classifier
0.53.0 (2026-09-29)
- Merge remote-tracking branch 'origin/main' into prepare-0.53.0-changelog
- fix(design): align the sensing node designs with the packages they describe (#13337) CalibrationStatusClassifier declares a preview_image publisher on a hardcoded per-camera topic that the node no longer creates, and names it as the outcome of the classify process. The point cloud concatenation component is built as concatenate_pointclouds_node.
- refactor(sensing): move node design files into each package (#13105)
- Contributors: Ryohsuke Mitsudome, Taekjin LEE
0.52.0 (2026-06-30)
0.51.0 (2026-05-01)
-
Merge remote-tracking branch 'origin/main' into tmp/bot/bump_version_base
-
feat: default artifact paths to ~/autoware_data/ml_models (#12523) feat(launches,configs): default artifact paths to ~/autoware_data/ml_models Roll every per-package [data_path]{.title-ref} / [model_path]{.title-ref} launch-arg default from [$(env HOME)/autoware_data[/...]]{.title-ref} to [$(env HOME)/autoware_data/ml_models[/...]]{.title-ref} so standalone universe launches resolve artifacts under the new [~/autoware_data/ml_models/]{.title-ref} layout (autowarefoundation/autoware#7068). When invoked through autoware_launch the parent overrides cascade and already pin the new root (autowarefoundation/autoware_launch#1835); this commit closes the gap for users who launch a perception / localization / sensing / planning component directly with [ros2 launch <pkg>]{.title-ref}. 22 launch files updated (one-line default change each):
- e2e/autoware_tensorrt_vad/launch/vad_carla_tiny.launch.xml
- localization/yabloc/yabloc_pose_initializer/launch/yabloc_pose_initializer.launch.xml
- perception/autoware_bevfusion/launch/bevfusion.launch.xml
- perception/autoware_camera_streampetr/launch/streampetr.launch.xml
- perception/autoware_image_projection_based_fusion/launch/pointpainting_fusion.launch.xml
- perception/autoware_lidar_apollo_instance_segmentation/launch/lidar_apollo_instance_segmentation.launch.xml
- perception/autoware_lidar_centerpoint/launch/lidar_centerpoint.launch.xml
- perception/autoware_lidar_frnet/launch/lidar_frnet.launch.xml
- perception/autoware_lidar_transfusion/launch/lidar_transfusion.launch.xml
- perception/autoware_ptv3/launch/ptv3.launch.xml
- perception/autoware_shape_estimation/launch/shape_estimation.launch.xml
- perception/autoware_simpl_prediction/launch/simpl.launch.xml
- perception/autoware_tensorrt_bevdet/launch/tensorrt_bevdet.launch.xml
- perception/autoware_tensorrt_bevformer/launch/bevformer.launch.xml
- perception/autoware_tensorrt_yolox/launch/{yolox_traffic_light_detector,yolox_tiny,yolox_s_plus_opt}.launch.xml
- perception/autoware_traffic_light_classifier/launch/{car,pedestrian}_traffic_light_classifier.launch.xml
- perception/autoware_traffic_light_fine_detector/launch/traffic_light_fine_detector.launch.xml
- planning/autoware_diffusion_planner/launch/diffusion_planner.launch.xml
- sensing/autoware_calibration_status_classifier/launch/calibration_status_classifier.launch.xml Drive-by README and test fixes:
- e2e/autoware_tensorrt_vad/{README.md,docs/design.md}: also migrate the [$HOME/autoware_map/Town01]{.title-ref} examples to [$HOME/autoware_data/maps/Town01]{.title-ref}.
- localization/yabloc/{README.md,yabloc_pose_initializer/README.md}: also migrate [$HOME/autoware_map/sample-map-rosbag]{.title-ref} to [$HOME/autoware_data/maps/demos/sample-map-rosbag]{.title-ref}.
- control/autoware_smart_mpc_trajectory_follower/README.md: migrate the [map_path:=$HOME/autoware_map/sample-map-planning]{.title-ref} example to [$HOME/autoware_data/maps/demos/sample-map-planning]{.title-ref}.
- simulator/autoware_carla_interface/README.md: migrate every [$HOME/autoware_map/Town01/...]{.title-ref} reference to [$HOME/autoware_data/maps/Town01/...]{.title-ref}.
- perception/{autoware_bevfusion,autoware_image_projection_based_fusion,autoware_lidar_centerpoint,autoware_tensorrt_bevformer}/README.md: copy-paste examples updated to [~/autoware_data/ml_models/<pkg>]{.title-ref}.
- perception/autoware_camera_streampetr/config/ml_package_camera_streampetr.param.yaml: header comment updated.
- planning/autoware_diffusion_planner/README.md: prerequisites snippet updated.
- sensing/autoware_calibration_status_classifier/test/{test_model_inference,test_calibration_status_classifier}.cpp: hardcoded fallback ONNX path updated. Users on the legacy layout can pin the old root with [data_path:=$HOME/autoware_data]{.title-ref} (or the per-package equivalent) on the command line. Refs: https://github.com/autowarefoundation/autoware/issues/7068
-
feat(autoware_calibration_status_classifier): add angular velocity filter and refine filters design
File truncated at 100 lines see the full file
Package Dependencies
System Dependencies
| Name |
|---|
| libopencv-dev |
Dependant Packages
Launch files
- launch/calibration_status_classifier.launch.xml
-
- input_linear_velocity [default: /sensing/vehicle_velocity_converter/twist_with_covariance]
- input_angular_velocity [default: /sensing/vehicle_velocity_converter/twist_with_covariance]
- input_objects [default: /perception/object_recognition/objects]
- validate_calibration_srv [default: validate_calibration]
- data_path [default: $(env HOME)/autoware_data/ml_models]
- model_name [default: calibration_status_classifier]
- model_path [default: $(var data_path)/calibration_status_classifier]
- model_param_path [default: $(find-pkg-share autoware_calibration_status_classifier)/config/$(var model_name).param.yaml]
- ml_package_param_path [default: $(var model_path)/ml_package_$(var model_name).param.yaml]
- build_only [default: false]
- use_sim_time [default: true]
- decompressor_param_file [default: $(find-pkg-share autoware_image_transport_decompressor)/config/image_transport_decompressor.param.yaml]
Messages
Services
Plugins
Recent questions tagged autoware_calibration_status_classifier at Robotics Stack Exchange
Package Summary
| Version | 0.53.0 |
| License | Apache License 2.0 |
| Build type | AMENT_CMAKE |
| Use | RECOMMENDED |
Repository Summary
| Description | |
| Checkout URI | https://github.com/autowarefoundation/autoware_universe.git |
| VCS Type | git |
| VCS Version | main |
| Last Updated | 2026-10-23 |
| Dev Status | UNKNOWN |
| Released | UNRELEASED |
| Contributing |
Help Wanted (-)
Good First Issues (-) Pull Requests to Review (-) |
Package Description
Maintainers
- Amadeusz Szymko
- Manato Hirabayashi
- Patiphon Narksri
Authors
- Amadeusz Szymko
autoware_calibration_status_classifier
Purpose
The autoware_calibration_status_classifier package provides real-time LiDAR-camera calibration validation using deep learning inference. It detects miscalibration between LiDAR and camera sensors by analyzing projected point clouds overlaid on camera images through a neural network-based approach.
Inner-workings / Algorithms
The calibration status detection system operates through the following pipeline:
1. Data Preprocessing (CUDA-accelerated)
- Image Undistortion: Corrects camera distortion
- Point Cloud Projection: Projects 3D LiDAR points onto undistorted 2D image plane - adds depth and intensity information
- Morphological Dilation: Enhances point visibility for neural network input
2. Neural Network Inference (TensorRT)
- Input Format: 5-channel normalized data (RGB + depth + intensity)
- Architecture: Deep neural network trained on calibrated/miscalibrated data
- Output: Binary classification with confidence scores for calibration status
3. Runtime Modes
- MANUAL: On-demand validation via service calls
- PERIODIC: Regular validation at configurable intervals
- ACTIVE: Continuous monitoring with synchronized sensor data
Inputs / Outputs
Input
| Name | Type | Description |
|---|---|---|
~/input/linear_velocity |
prerequisite.linear_velocity_check.source parameter |
Vehicle twist for linear velocity check (multiple message types supported) |
~/input/angular_velocity |
prerequisite.angular_velocity_check.source parameter |
Vehicle twist for angular velocity check (multiple message types supported) |
~/input/objects |
prerequisite.objects_check.source parameter |
Detected objects for objects check (multiple message types supported) |
input.cloud_topics |
sensor_msgs::msg::PointCloud2 |
LiDAR point cloud data |
input.image_topics |
sensor_msgs::msg::Image |
Camera image data (BGR8 format) |
| Camera info topics | sensor_msgs::msg::CameraInfo |
Camera intrinsic parameters and distortion coefficients |
Output
| Name | Type | Description |
|---|---|---|
/diagnostics |
diagnostic_msgs::msg::DiagnosticArray |
ROS diagnostics with calibration status |
~/validate_calibration_srv |
std_srvs::srv::Trigger |
Manual validation service (MANUAL mode) |
| Preview image topics | sensor_msgs::msg::Image |
Visualization images with projected points |
Services
| Name | Type | Description |
|---|---|---|
~/input/validate_calibration_srv |
std_srvs::srv::Trigger |
Manual calibration validation request |
Parameters
Node Parameters
{{ json_to_markdown(“sensing/autoware_calibration_status_classifier/schema/calibration_status_classifier.schema.json”) }}
Network Parameters
{{ json_to_markdown(“sensing/autoware_calibration_status_classifier/schema/ml_package_calibration_status_classifier.schema.json”) }}
Assumptions / Known Limits
- Input images must be in BGR8 format (8-bit per channel)
- Input point clouds should contain intensity information (XYZIRC format)
Usage Example
ros2 launch autoware_calibration_status_classifier calibration_status_classifier.launch.xml
Future Extensions / Unimplemented Parts
- Manual runtime mode with detailed response (custom srv)
- Replace filter for objects on the scene counter to objects within the camera FOV counter (raytracing)
- Multithreading for multiple camera-LiDAR pairs
- More filters (e.g. yaw rate)
- cuda_blackboard support
- Replace custom kernels with NPP functions where applicable
References
Changelog for package autoware_calibration_status_classifier
0.53.0 (2026-09-29)
- Merge remote-tracking branch 'origin/main' into prepare-0.53.0-changelog
- fix(design): align the sensing node designs with the packages they describe (#13337) CalibrationStatusClassifier declares a preview_image publisher on a hardcoded per-camera topic that the node no longer creates, and names it as the outcome of the classify process. The point cloud concatenation component is built as concatenate_pointclouds_node.
- refactor(sensing): move node design files into each package (#13105)
- Contributors: Ryohsuke Mitsudome, Taekjin LEE
0.52.0 (2026-06-30)
0.51.0 (2026-05-01)
-
Merge remote-tracking branch 'origin/main' into tmp/bot/bump_version_base
-
feat: default artifact paths to ~/autoware_data/ml_models (#12523) feat(launches,configs): default artifact paths to ~/autoware_data/ml_models Roll every per-package [data_path]{.title-ref} / [model_path]{.title-ref} launch-arg default from [$(env HOME)/autoware_data[/...]]{.title-ref} to [$(env HOME)/autoware_data/ml_models[/...]]{.title-ref} so standalone universe launches resolve artifacts under the new [~/autoware_data/ml_models/]{.title-ref} layout (autowarefoundation/autoware#7068). When invoked through autoware_launch the parent overrides cascade and already pin the new root (autowarefoundation/autoware_launch#1835); this commit closes the gap for users who launch a perception / localization / sensing / planning component directly with [ros2 launch <pkg>]{.title-ref}. 22 launch files updated (one-line default change each):
- e2e/autoware_tensorrt_vad/launch/vad_carla_tiny.launch.xml
- localization/yabloc/yabloc_pose_initializer/launch/yabloc_pose_initializer.launch.xml
- perception/autoware_bevfusion/launch/bevfusion.launch.xml
- perception/autoware_camera_streampetr/launch/streampetr.launch.xml
- perception/autoware_image_projection_based_fusion/launch/pointpainting_fusion.launch.xml
- perception/autoware_lidar_apollo_instance_segmentation/launch/lidar_apollo_instance_segmentation.launch.xml
- perception/autoware_lidar_centerpoint/launch/lidar_centerpoint.launch.xml
- perception/autoware_lidar_frnet/launch/lidar_frnet.launch.xml
- perception/autoware_lidar_transfusion/launch/lidar_transfusion.launch.xml
- perception/autoware_ptv3/launch/ptv3.launch.xml
- perception/autoware_shape_estimation/launch/shape_estimation.launch.xml
- perception/autoware_simpl_prediction/launch/simpl.launch.xml
- perception/autoware_tensorrt_bevdet/launch/tensorrt_bevdet.launch.xml
- perception/autoware_tensorrt_bevformer/launch/bevformer.launch.xml
- perception/autoware_tensorrt_yolox/launch/{yolox_traffic_light_detector,yolox_tiny,yolox_s_plus_opt}.launch.xml
- perception/autoware_traffic_light_classifier/launch/{car,pedestrian}_traffic_light_classifier.launch.xml
- perception/autoware_traffic_light_fine_detector/launch/traffic_light_fine_detector.launch.xml
- planning/autoware_diffusion_planner/launch/diffusion_planner.launch.xml
- sensing/autoware_calibration_status_classifier/launch/calibration_status_classifier.launch.xml Drive-by README and test fixes:
- e2e/autoware_tensorrt_vad/{README.md,docs/design.md}: also migrate the [$HOME/autoware_map/Town01]{.title-ref} examples to [$HOME/autoware_data/maps/Town01]{.title-ref}.
- localization/yabloc/{README.md,yabloc_pose_initializer/README.md}: also migrate [$HOME/autoware_map/sample-map-rosbag]{.title-ref} to [$HOME/autoware_data/maps/demos/sample-map-rosbag]{.title-ref}.
- control/autoware_smart_mpc_trajectory_follower/README.md: migrate the [map_path:=$HOME/autoware_map/sample-map-planning]{.title-ref} example to [$HOME/autoware_data/maps/demos/sample-map-planning]{.title-ref}.
- simulator/autoware_carla_interface/README.md: migrate every [$HOME/autoware_map/Town01/...]{.title-ref} reference to [$HOME/autoware_data/maps/Town01/...]{.title-ref}.
- perception/{autoware_bevfusion,autoware_image_projection_based_fusion,autoware_lidar_centerpoint,autoware_tensorrt_bevformer}/README.md: copy-paste examples updated to [~/autoware_data/ml_models/<pkg>]{.title-ref}.
- perception/autoware_camera_streampetr/config/ml_package_camera_streampetr.param.yaml: header comment updated.
- planning/autoware_diffusion_planner/README.md: prerequisites snippet updated.
- sensing/autoware_calibration_status_classifier/test/{test_model_inference,test_calibration_status_classifier}.cpp: hardcoded fallback ONNX path updated. Users on the legacy layout can pin the old root with [data_path:=$HOME/autoware_data]{.title-ref} (or the per-package equivalent) on the command line. Refs: https://github.com/autowarefoundation/autoware/issues/7068
-
feat(autoware_calibration_status_classifier): add angular velocity filter and refine filters design
File truncated at 100 lines see the full file
Package Dependencies
System Dependencies
| Name |
|---|
| libopencv-dev |
Dependant Packages
Launch files
- launch/calibration_status_classifier.launch.xml
-
- input_linear_velocity [default: /sensing/vehicle_velocity_converter/twist_with_covariance]
- input_angular_velocity [default: /sensing/vehicle_velocity_converter/twist_with_covariance]
- input_objects [default: /perception/object_recognition/objects]
- validate_calibration_srv [default: validate_calibration]
- data_path [default: $(env HOME)/autoware_data/ml_models]
- model_name [default: calibration_status_classifier]
- model_path [default: $(var data_path)/calibration_status_classifier]
- model_param_path [default: $(find-pkg-share autoware_calibration_status_classifier)/config/$(var model_name).param.yaml]
- ml_package_param_path [default: $(var model_path)/ml_package_$(var model_name).param.yaml]
- build_only [default: false]
- use_sim_time [default: true]
- decompressor_param_file [default: $(find-pkg-share autoware_image_transport_decompressor)/config/image_transport_decompressor.param.yaml]
Messages
Services
Plugins
Recent questions tagged autoware_calibration_status_classifier at Robotics Stack Exchange
Package Summary
| Version | 0.53.0 |
| License | Apache License 2.0 |
| Build type | AMENT_CMAKE |
| Use | RECOMMENDED |
Repository Summary
| Description | |
| Checkout URI | https://github.com/autowarefoundation/autoware_universe.git |
| VCS Type | git |
| VCS Version | main |
| Last Updated | 2026-10-23 |
| Dev Status | UNKNOWN |
| Released | UNRELEASED |
| Contributing |
Help Wanted (-)
Good First Issues (-) Pull Requests to Review (-) |
Package Description
Maintainers
- Amadeusz Szymko
- Manato Hirabayashi
- Patiphon Narksri
Authors
- Amadeusz Szymko
autoware_calibration_status_classifier
Purpose
The autoware_calibration_status_classifier package provides real-time LiDAR-camera calibration validation using deep learning inference. It detects miscalibration between LiDAR and camera sensors by analyzing projected point clouds overlaid on camera images through a neural network-based approach.
Inner-workings / Algorithms
The calibration status detection system operates through the following pipeline:
1. Data Preprocessing (CUDA-accelerated)
- Image Undistortion: Corrects camera distortion
- Point Cloud Projection: Projects 3D LiDAR points onto undistorted 2D image plane - adds depth and intensity information
- Morphological Dilation: Enhances point visibility for neural network input
2. Neural Network Inference (TensorRT)
- Input Format: 5-channel normalized data (RGB + depth + intensity)
- Architecture: Deep neural network trained on calibrated/miscalibrated data
- Output: Binary classification with confidence scores for calibration status
3. Runtime Modes
- MANUAL: On-demand validation via service calls
- PERIODIC: Regular validation at configurable intervals
- ACTIVE: Continuous monitoring with synchronized sensor data
Inputs / Outputs
Input
| Name | Type | Description |
|---|---|---|
~/input/linear_velocity |
prerequisite.linear_velocity_check.source parameter |
Vehicle twist for linear velocity check (multiple message types supported) |
~/input/angular_velocity |
prerequisite.angular_velocity_check.source parameter |
Vehicle twist for angular velocity check (multiple message types supported) |
~/input/objects |
prerequisite.objects_check.source parameter |
Detected objects for objects check (multiple message types supported) |
input.cloud_topics |
sensor_msgs::msg::PointCloud2 |
LiDAR point cloud data |
input.image_topics |
sensor_msgs::msg::Image |
Camera image data (BGR8 format) |
| Camera info topics | sensor_msgs::msg::CameraInfo |
Camera intrinsic parameters and distortion coefficients |
Output
| Name | Type | Description |
|---|---|---|
/diagnostics |
diagnostic_msgs::msg::DiagnosticArray |
ROS diagnostics with calibration status |
~/validate_calibration_srv |
std_srvs::srv::Trigger |
Manual validation service (MANUAL mode) |
| Preview image topics | sensor_msgs::msg::Image |
Visualization images with projected points |
Services
| Name | Type | Description |
|---|---|---|
~/input/validate_calibration_srv |
std_srvs::srv::Trigger |
Manual calibration validation request |
Parameters
Node Parameters
{{ json_to_markdown(“sensing/autoware_calibration_status_classifier/schema/calibration_status_classifier.schema.json”) }}
Network Parameters
{{ json_to_markdown(“sensing/autoware_calibration_status_classifier/schema/ml_package_calibration_status_classifier.schema.json”) }}
Assumptions / Known Limits
- Input images must be in BGR8 format (8-bit per channel)
- Input point clouds should contain intensity information (XYZIRC format)
Usage Example
ros2 launch autoware_calibration_status_classifier calibration_status_classifier.launch.xml
Future Extensions / Unimplemented Parts
- Manual runtime mode with detailed response (custom srv)
- Replace filter for objects on the scene counter to objects within the camera FOV counter (raytracing)
- Multithreading for multiple camera-LiDAR pairs
- More filters (e.g. yaw rate)
- cuda_blackboard support
- Replace custom kernels with NPP functions where applicable
References
Changelog for package autoware_calibration_status_classifier
0.53.0 (2026-09-29)
- Merge remote-tracking branch 'origin/main' into prepare-0.53.0-changelog
- fix(design): align the sensing node designs with the packages they describe (#13337) CalibrationStatusClassifier declares a preview_image publisher on a hardcoded per-camera topic that the node no longer creates, and names it as the outcome of the classify process. The point cloud concatenation component is built as concatenate_pointclouds_node.
- refactor(sensing): move node design files into each package (#13105)
- Contributors: Ryohsuke Mitsudome, Taekjin LEE
0.52.0 (2026-06-30)
0.51.0 (2026-05-01)
-
Merge remote-tracking branch 'origin/main' into tmp/bot/bump_version_base
-
feat: default artifact paths to ~/autoware_data/ml_models (#12523) feat(launches,configs): default artifact paths to ~/autoware_data/ml_models Roll every per-package [data_path]{.title-ref} / [model_path]{.title-ref} launch-arg default from [$(env HOME)/autoware_data[/...]]{.title-ref} to [$(env HOME)/autoware_data/ml_models[/...]]{.title-ref} so standalone universe launches resolve artifacts under the new [~/autoware_data/ml_models/]{.title-ref} layout (autowarefoundation/autoware#7068). When invoked through autoware_launch the parent overrides cascade and already pin the new root (autowarefoundation/autoware_launch#1835); this commit closes the gap for users who launch a perception / localization / sensing / planning component directly with [ros2 launch <pkg>]{.title-ref}. 22 launch files updated (one-line default change each):
- e2e/autoware_tensorrt_vad/launch/vad_carla_tiny.launch.xml
- localization/yabloc/yabloc_pose_initializer/launch/yabloc_pose_initializer.launch.xml
- perception/autoware_bevfusion/launch/bevfusion.launch.xml
- perception/autoware_camera_streampetr/launch/streampetr.launch.xml
- perception/autoware_image_projection_based_fusion/launch/pointpainting_fusion.launch.xml
- perception/autoware_lidar_apollo_instance_segmentation/launch/lidar_apollo_instance_segmentation.launch.xml
- perception/autoware_lidar_centerpoint/launch/lidar_centerpoint.launch.xml
- perception/autoware_lidar_frnet/launch/lidar_frnet.launch.xml
- perception/autoware_lidar_transfusion/launch/lidar_transfusion.launch.xml
- perception/autoware_ptv3/launch/ptv3.launch.xml
- perception/autoware_shape_estimation/launch/shape_estimation.launch.xml
- perception/autoware_simpl_prediction/launch/simpl.launch.xml
- perception/autoware_tensorrt_bevdet/launch/tensorrt_bevdet.launch.xml
- perception/autoware_tensorrt_bevformer/launch/bevformer.launch.xml
- perception/autoware_tensorrt_yolox/launch/{yolox_traffic_light_detector,yolox_tiny,yolox_s_plus_opt}.launch.xml
- perception/autoware_traffic_light_classifier/launch/{car,pedestrian}_traffic_light_classifier.launch.xml
- perception/autoware_traffic_light_fine_detector/launch/traffic_light_fine_detector.launch.xml
- planning/autoware_diffusion_planner/launch/diffusion_planner.launch.xml
- sensing/autoware_calibration_status_classifier/launch/calibration_status_classifier.launch.xml Drive-by README and test fixes:
- e2e/autoware_tensorrt_vad/{README.md,docs/design.md}: also migrate the [$HOME/autoware_map/Town01]{.title-ref} examples to [$HOME/autoware_data/maps/Town01]{.title-ref}.
- localization/yabloc/{README.md,yabloc_pose_initializer/README.md}: also migrate [$HOME/autoware_map/sample-map-rosbag]{.title-ref} to [$HOME/autoware_data/maps/demos/sample-map-rosbag]{.title-ref}.
- control/autoware_smart_mpc_trajectory_follower/README.md: migrate the [map_path:=$HOME/autoware_map/sample-map-planning]{.title-ref} example to [$HOME/autoware_data/maps/demos/sample-map-planning]{.title-ref}.
- simulator/autoware_carla_interface/README.md: migrate every [$HOME/autoware_map/Town01/...]{.title-ref} reference to [$HOME/autoware_data/maps/Town01/...]{.title-ref}.
- perception/{autoware_bevfusion,autoware_image_projection_based_fusion,autoware_lidar_centerpoint,autoware_tensorrt_bevformer}/README.md: copy-paste examples updated to [~/autoware_data/ml_models/<pkg>]{.title-ref}.
- perception/autoware_camera_streampetr/config/ml_package_camera_streampetr.param.yaml: header comment updated.
- planning/autoware_diffusion_planner/README.md: prerequisites snippet updated.
- sensing/autoware_calibration_status_classifier/test/{test_model_inference,test_calibration_status_classifier}.cpp: hardcoded fallback ONNX path updated. Users on the legacy layout can pin the old root with [data_path:=$HOME/autoware_data]{.title-ref} (or the per-package equivalent) on the command line. Refs: https://github.com/autowarefoundation/autoware/issues/7068
-
feat(autoware_calibration_status_classifier): add angular velocity filter and refine filters design
File truncated at 100 lines see the full file
Package Dependencies
System Dependencies
| Name |
|---|
| libopencv-dev |
Dependant Packages
Launch files
- launch/calibration_status_classifier.launch.xml
-
- input_linear_velocity [default: /sensing/vehicle_velocity_converter/twist_with_covariance]
- input_angular_velocity [default: /sensing/vehicle_velocity_converter/twist_with_covariance]
- input_objects [default: /perception/object_recognition/objects]
- validate_calibration_srv [default: validate_calibration]
- data_path [default: $(env HOME)/autoware_data/ml_models]
- model_name [default: calibration_status_classifier]
- model_path [default: $(var data_path)/calibration_status_classifier]
- model_param_path [default: $(find-pkg-share autoware_calibration_status_classifier)/config/$(var model_name).param.yaml]
- ml_package_param_path [default: $(var model_path)/ml_package_$(var model_name).param.yaml]
- build_only [default: false]
- use_sim_time [default: true]
- decompressor_param_file [default: $(find-pkg-share autoware_image_transport_decompressor)/config/image_transport_decompressor.param.yaml]
Messages
Services
Plugins
Recent questions tagged autoware_calibration_status_classifier at Robotics Stack Exchange
Package Summary
| Version | 0.53.0 |
| License | Apache License 2.0 |
| Build type | AMENT_CMAKE |
| Use | RECOMMENDED |
Repository Summary
| Description | |
| Checkout URI | https://github.com/autowarefoundation/autoware_universe.git |
| VCS Type | git |
| VCS Version | main |
| Last Updated | 2026-10-23 |
| Dev Status | UNKNOWN |
| Released | UNRELEASED |
| Contributing |
Help Wanted (-)
Good First Issues (-) Pull Requests to Review (-) |
Package Description
Maintainers
- Amadeusz Szymko
- Manato Hirabayashi
- Patiphon Narksri
Authors
- Amadeusz Szymko
autoware_calibration_status_classifier
Purpose
The autoware_calibration_status_classifier package provides real-time LiDAR-camera calibration validation using deep learning inference. It detects miscalibration between LiDAR and camera sensors by analyzing projected point clouds overlaid on camera images through a neural network-based approach.
Inner-workings / Algorithms
The calibration status detection system operates through the following pipeline:
1. Data Preprocessing (CUDA-accelerated)
- Image Undistortion: Corrects camera distortion
- Point Cloud Projection: Projects 3D LiDAR points onto undistorted 2D image plane - adds depth and intensity information
- Morphological Dilation: Enhances point visibility for neural network input
2. Neural Network Inference (TensorRT)
- Input Format: 5-channel normalized data (RGB + depth + intensity)
- Architecture: Deep neural network trained on calibrated/miscalibrated data
- Output: Binary classification with confidence scores for calibration status
3. Runtime Modes
- MANUAL: On-demand validation via service calls
- PERIODIC: Regular validation at configurable intervals
- ACTIVE: Continuous monitoring with synchronized sensor data
Inputs / Outputs
Input
| Name | Type | Description |
|---|---|---|
~/input/linear_velocity |
prerequisite.linear_velocity_check.source parameter |
Vehicle twist for linear velocity check (multiple message types supported) |
~/input/angular_velocity |
prerequisite.angular_velocity_check.source parameter |
Vehicle twist for angular velocity check (multiple message types supported) |
~/input/objects |
prerequisite.objects_check.source parameter |
Detected objects for objects check (multiple message types supported) |
input.cloud_topics |
sensor_msgs::msg::PointCloud2 |
LiDAR point cloud data |
input.image_topics |
sensor_msgs::msg::Image |
Camera image data (BGR8 format) |
| Camera info topics | sensor_msgs::msg::CameraInfo |
Camera intrinsic parameters and distortion coefficients |
Output
| Name | Type | Description |
|---|---|---|
/diagnostics |
diagnostic_msgs::msg::DiagnosticArray |
ROS diagnostics with calibration status |
~/validate_calibration_srv |
std_srvs::srv::Trigger |
Manual validation service (MANUAL mode) |
| Preview image topics | sensor_msgs::msg::Image |
Visualization images with projected points |
Services
| Name | Type | Description |
|---|---|---|
~/input/validate_calibration_srv |
std_srvs::srv::Trigger |
Manual calibration validation request |
Parameters
Node Parameters
{{ json_to_markdown(“sensing/autoware_calibration_status_classifier/schema/calibration_status_classifier.schema.json”) }}
Network Parameters
{{ json_to_markdown(“sensing/autoware_calibration_status_classifier/schema/ml_package_calibration_status_classifier.schema.json”) }}
Assumptions / Known Limits
- Input images must be in BGR8 format (8-bit per channel)
- Input point clouds should contain intensity information (XYZIRC format)
Usage Example
ros2 launch autoware_calibration_status_classifier calibration_status_classifier.launch.xml
Future Extensions / Unimplemented Parts
- Manual runtime mode with detailed response (custom srv)
- Replace filter for objects on the scene counter to objects within the camera FOV counter (raytracing)
- Multithreading for multiple camera-LiDAR pairs
- More filters (e.g. yaw rate)
- cuda_blackboard support
- Replace custom kernels with NPP functions where applicable
References
Changelog for package autoware_calibration_status_classifier
0.53.0 (2026-09-29)
- Merge remote-tracking branch 'origin/main' into prepare-0.53.0-changelog
- fix(design): align the sensing node designs with the packages they describe (#13337) CalibrationStatusClassifier declares a preview_image publisher on a hardcoded per-camera topic that the node no longer creates, and names it as the outcome of the classify process. The point cloud concatenation component is built as concatenate_pointclouds_node.
- refactor(sensing): move node design files into each package (#13105)
- Contributors: Ryohsuke Mitsudome, Taekjin LEE
0.52.0 (2026-06-30)
0.51.0 (2026-05-01)
-
Merge remote-tracking branch 'origin/main' into tmp/bot/bump_version_base
-
feat: default artifact paths to ~/autoware_data/ml_models (#12523) feat(launches,configs): default artifact paths to ~/autoware_data/ml_models Roll every per-package [data_path]{.title-ref} / [model_path]{.title-ref} launch-arg default from [$(env HOME)/autoware_data[/...]]{.title-ref} to [$(env HOME)/autoware_data/ml_models[/...]]{.title-ref} so standalone universe launches resolve artifacts under the new [~/autoware_data/ml_models/]{.title-ref} layout (autowarefoundation/autoware#7068). When invoked through autoware_launch the parent overrides cascade and already pin the new root (autowarefoundation/autoware_launch#1835); this commit closes the gap for users who launch a perception / localization / sensing / planning component directly with [ros2 launch <pkg>]{.title-ref}. 22 launch files updated (one-line default change each):
- e2e/autoware_tensorrt_vad/launch/vad_carla_tiny.launch.xml
- localization/yabloc/yabloc_pose_initializer/launch/yabloc_pose_initializer.launch.xml
- perception/autoware_bevfusion/launch/bevfusion.launch.xml
- perception/autoware_camera_streampetr/launch/streampetr.launch.xml
- perception/autoware_image_projection_based_fusion/launch/pointpainting_fusion.launch.xml
- perception/autoware_lidar_apollo_instance_segmentation/launch/lidar_apollo_instance_segmentation.launch.xml
- perception/autoware_lidar_centerpoint/launch/lidar_centerpoint.launch.xml
- perception/autoware_lidar_frnet/launch/lidar_frnet.launch.xml
- perception/autoware_lidar_transfusion/launch/lidar_transfusion.launch.xml
- perception/autoware_ptv3/launch/ptv3.launch.xml
- perception/autoware_shape_estimation/launch/shape_estimation.launch.xml
- perception/autoware_simpl_prediction/launch/simpl.launch.xml
- perception/autoware_tensorrt_bevdet/launch/tensorrt_bevdet.launch.xml
- perception/autoware_tensorrt_bevformer/launch/bevformer.launch.xml
- perception/autoware_tensorrt_yolox/launch/{yolox_traffic_light_detector,yolox_tiny,yolox_s_plus_opt}.launch.xml
- perception/autoware_traffic_light_classifier/launch/{car,pedestrian}_traffic_light_classifier.launch.xml
- perception/autoware_traffic_light_fine_detector/launch/traffic_light_fine_detector.launch.xml
- planning/autoware_diffusion_planner/launch/diffusion_planner.launch.xml
- sensing/autoware_calibration_status_classifier/launch/calibration_status_classifier.launch.xml Drive-by README and test fixes:
- e2e/autoware_tensorrt_vad/{README.md,docs/design.md}: also migrate the [$HOME/autoware_map/Town01]{.title-ref} examples to [$HOME/autoware_data/maps/Town01]{.title-ref}.
- localization/yabloc/{README.md,yabloc_pose_initializer/README.md}: also migrate [$HOME/autoware_map/sample-map-rosbag]{.title-ref} to [$HOME/autoware_data/maps/demos/sample-map-rosbag]{.title-ref}.
- control/autoware_smart_mpc_trajectory_follower/README.md: migrate the [map_path:=$HOME/autoware_map/sample-map-planning]{.title-ref} example to [$HOME/autoware_data/maps/demos/sample-map-planning]{.title-ref}.
- simulator/autoware_carla_interface/README.md: migrate every [$HOME/autoware_map/Town01/...]{.title-ref} reference to [$HOME/autoware_data/maps/Town01/...]{.title-ref}.
- perception/{autoware_bevfusion,autoware_image_projection_based_fusion,autoware_lidar_centerpoint,autoware_tensorrt_bevformer}/README.md: copy-paste examples updated to [~/autoware_data/ml_models/<pkg>]{.title-ref}.
- perception/autoware_camera_streampetr/config/ml_package_camera_streampetr.param.yaml: header comment updated.
- planning/autoware_diffusion_planner/README.md: prerequisites snippet updated.
- sensing/autoware_calibration_status_classifier/test/{test_model_inference,test_calibration_status_classifier}.cpp: hardcoded fallback ONNX path updated. Users on the legacy layout can pin the old root with [data_path:=$HOME/autoware_data]{.title-ref} (or the per-package equivalent) on the command line. Refs: https://github.com/autowarefoundation/autoware/issues/7068
-
feat(autoware_calibration_status_classifier): add angular velocity filter and refine filters design
File truncated at 100 lines see the full file
Package Dependencies
System Dependencies
| Name |
|---|
| libopencv-dev |
Dependant Packages
Launch files
- launch/calibration_status_classifier.launch.xml
-
- input_linear_velocity [default: /sensing/vehicle_velocity_converter/twist_with_covariance]
- input_angular_velocity [default: /sensing/vehicle_velocity_converter/twist_with_covariance]
- input_objects [default: /perception/object_recognition/objects]
- validate_calibration_srv [default: validate_calibration]
- data_path [default: $(env HOME)/autoware_data/ml_models]
- model_name [default: calibration_status_classifier]
- model_path [default: $(var data_path)/calibration_status_classifier]
- model_param_path [default: $(find-pkg-share autoware_calibration_status_classifier)/config/$(var model_name).param.yaml]
- ml_package_param_path [default: $(var model_path)/ml_package_$(var model_name).param.yaml]
- build_only [default: false]
- use_sim_time [default: true]
- decompressor_param_file [default: $(find-pkg-share autoware_image_transport_decompressor)/config/image_transport_decompressor.param.yaml]
Messages
Services
Plugins
Recent questions tagged autoware_calibration_status_classifier at Robotics Stack Exchange
Package Summary
| Version | 0.53.0 |
| License | Apache License 2.0 |
| Build type | AMENT_CMAKE |
| Use | RECOMMENDED |
Repository Summary
| Description | |
| Checkout URI | https://github.com/autowarefoundation/autoware_universe.git |
| VCS Type | git |
| VCS Version | main |
| Last Updated | 2026-10-23 |
| Dev Status | UNKNOWN |
| Released | UNRELEASED |
| Contributing |
Help Wanted (-)
Good First Issues (-) Pull Requests to Review (-) |
Package Description
Maintainers
- Amadeusz Szymko
- Manato Hirabayashi
- Patiphon Narksri
Authors
- Amadeusz Szymko
autoware_calibration_status_classifier
Purpose
The autoware_calibration_status_classifier package provides real-time LiDAR-camera calibration validation using deep learning inference. It detects miscalibration between LiDAR and camera sensors by analyzing projected point clouds overlaid on camera images through a neural network-based approach.
Inner-workings / Algorithms
The calibration status detection system operates through the following pipeline:
1. Data Preprocessing (CUDA-accelerated)
- Image Undistortion: Corrects camera distortion
- Point Cloud Projection: Projects 3D LiDAR points onto undistorted 2D image plane - adds depth and intensity information
- Morphological Dilation: Enhances point visibility for neural network input
2. Neural Network Inference (TensorRT)
- Input Format: 5-channel normalized data (RGB + depth + intensity)
- Architecture: Deep neural network trained on calibrated/miscalibrated data
- Output: Binary classification with confidence scores for calibration status
3. Runtime Modes
- MANUAL: On-demand validation via service calls
- PERIODIC: Regular validation at configurable intervals
- ACTIVE: Continuous monitoring with synchronized sensor data
Inputs / Outputs
Input
| Name | Type | Description |
|---|---|---|
~/input/linear_velocity |
prerequisite.linear_velocity_check.source parameter |
Vehicle twist for linear velocity check (multiple message types supported) |
~/input/angular_velocity |
prerequisite.angular_velocity_check.source parameter |
Vehicle twist for angular velocity check (multiple message types supported) |
~/input/objects |
prerequisite.objects_check.source parameter |
Detected objects for objects check (multiple message types supported) |
input.cloud_topics |
sensor_msgs::msg::PointCloud2 |
LiDAR point cloud data |
input.image_topics |
sensor_msgs::msg::Image |
Camera image data (BGR8 format) |
| Camera info topics | sensor_msgs::msg::CameraInfo |
Camera intrinsic parameters and distortion coefficients |
Output
| Name | Type | Description |
|---|---|---|
/diagnostics |
diagnostic_msgs::msg::DiagnosticArray |
ROS diagnostics with calibration status |
~/validate_calibration_srv |
std_srvs::srv::Trigger |
Manual validation service (MANUAL mode) |
| Preview image topics | sensor_msgs::msg::Image |
Visualization images with projected points |
Services
| Name | Type | Description |
|---|---|---|
~/input/validate_calibration_srv |
std_srvs::srv::Trigger |
Manual calibration validation request |
Parameters
Node Parameters
{{ json_to_markdown(“sensing/autoware_calibration_status_classifier/schema/calibration_status_classifier.schema.json”) }}
Network Parameters
{{ json_to_markdown(“sensing/autoware_calibration_status_classifier/schema/ml_package_calibration_status_classifier.schema.json”) }}
Assumptions / Known Limits
- Input images must be in BGR8 format (8-bit per channel)
- Input point clouds should contain intensity information (XYZIRC format)
Usage Example
ros2 launch autoware_calibration_status_classifier calibration_status_classifier.launch.xml
Future Extensions / Unimplemented Parts
- Manual runtime mode with detailed response (custom srv)
- Replace filter for objects on the scene counter to objects within the camera FOV counter (raytracing)
- Multithreading for multiple camera-LiDAR pairs
- More filters (e.g. yaw rate)
- cuda_blackboard support
- Replace custom kernels with NPP functions where applicable
References
Changelog for package autoware_calibration_status_classifier
0.53.0 (2026-09-29)
- Merge remote-tracking branch 'origin/main' into prepare-0.53.0-changelog
- fix(design): align the sensing node designs with the packages they describe (#13337) CalibrationStatusClassifier declares a preview_image publisher on a hardcoded per-camera topic that the node no longer creates, and names it as the outcome of the classify process. The point cloud concatenation component is built as concatenate_pointclouds_node.
- refactor(sensing): move node design files into each package (#13105)
- Contributors: Ryohsuke Mitsudome, Taekjin LEE
0.52.0 (2026-06-30)
0.51.0 (2026-05-01)
-
Merge remote-tracking branch 'origin/main' into tmp/bot/bump_version_base
-
feat: default artifact paths to ~/autoware_data/ml_models (#12523) feat(launches,configs): default artifact paths to ~/autoware_data/ml_models Roll every per-package [data_path]{.title-ref} / [model_path]{.title-ref} launch-arg default from [$(env HOME)/autoware_data[/...]]{.title-ref} to [$(env HOME)/autoware_data/ml_models[/...]]{.title-ref} so standalone universe launches resolve artifacts under the new [~/autoware_data/ml_models/]{.title-ref} layout (autowarefoundation/autoware#7068). When invoked through autoware_launch the parent overrides cascade and already pin the new root (autowarefoundation/autoware_launch#1835); this commit closes the gap for users who launch a perception / localization / sensing / planning component directly with [ros2 launch <pkg>]{.title-ref}. 22 launch files updated (one-line default change each):
- e2e/autoware_tensorrt_vad/launch/vad_carla_tiny.launch.xml
- localization/yabloc/yabloc_pose_initializer/launch/yabloc_pose_initializer.launch.xml
- perception/autoware_bevfusion/launch/bevfusion.launch.xml
- perception/autoware_camera_streampetr/launch/streampetr.launch.xml
- perception/autoware_image_projection_based_fusion/launch/pointpainting_fusion.launch.xml
- perception/autoware_lidar_apollo_instance_segmentation/launch/lidar_apollo_instance_segmentation.launch.xml
- perception/autoware_lidar_centerpoint/launch/lidar_centerpoint.launch.xml
- perception/autoware_lidar_frnet/launch/lidar_frnet.launch.xml
- perception/autoware_lidar_transfusion/launch/lidar_transfusion.launch.xml
- perception/autoware_ptv3/launch/ptv3.launch.xml
- perception/autoware_shape_estimation/launch/shape_estimation.launch.xml
- perception/autoware_simpl_prediction/launch/simpl.launch.xml
- perception/autoware_tensorrt_bevdet/launch/tensorrt_bevdet.launch.xml
- perception/autoware_tensorrt_bevformer/launch/bevformer.launch.xml
- perception/autoware_tensorrt_yolox/launch/{yolox_traffic_light_detector,yolox_tiny,yolox_s_plus_opt}.launch.xml
- perception/autoware_traffic_light_classifier/launch/{car,pedestrian}_traffic_light_classifier.launch.xml
- perception/autoware_traffic_light_fine_detector/launch/traffic_light_fine_detector.launch.xml
- planning/autoware_diffusion_planner/launch/diffusion_planner.launch.xml
- sensing/autoware_calibration_status_classifier/launch/calibration_status_classifier.launch.xml Drive-by README and test fixes:
- e2e/autoware_tensorrt_vad/{README.md,docs/design.md}: also migrate the [$HOME/autoware_map/Town01]{.title-ref} examples to [$HOME/autoware_data/maps/Town01]{.title-ref}.
- localization/yabloc/{README.md,yabloc_pose_initializer/README.md}: also migrate [$HOME/autoware_map/sample-map-rosbag]{.title-ref} to [$HOME/autoware_data/maps/demos/sample-map-rosbag]{.title-ref}.
- control/autoware_smart_mpc_trajectory_follower/README.md: migrate the [map_path:=$HOME/autoware_map/sample-map-planning]{.title-ref} example to [$HOME/autoware_data/maps/demos/sample-map-planning]{.title-ref}.
- simulator/autoware_carla_interface/README.md: migrate every [$HOME/autoware_map/Town01/...]{.title-ref} reference to [$HOME/autoware_data/maps/Town01/...]{.title-ref}.
- perception/{autoware_bevfusion,autoware_image_projection_based_fusion,autoware_lidar_centerpoint,autoware_tensorrt_bevformer}/README.md: copy-paste examples updated to [~/autoware_data/ml_models/<pkg>]{.title-ref}.
- perception/autoware_camera_streampetr/config/ml_package_camera_streampetr.param.yaml: header comment updated.
- planning/autoware_diffusion_planner/README.md: prerequisites snippet updated.
- sensing/autoware_calibration_status_classifier/test/{test_model_inference,test_calibration_status_classifier}.cpp: hardcoded fallback ONNX path updated. Users on the legacy layout can pin the old root with [data_path:=$HOME/autoware_data]{.title-ref} (or the per-package equivalent) on the command line. Refs: https://github.com/autowarefoundation/autoware/issues/7068
-
feat(autoware_calibration_status_classifier): add angular velocity filter and refine filters design
File truncated at 100 lines see the full file
Package Dependencies
System Dependencies
| Name |
|---|
| libopencv-dev |
Dependant Packages
Launch files
- launch/calibration_status_classifier.launch.xml
-
- input_linear_velocity [default: /sensing/vehicle_velocity_converter/twist_with_covariance]
- input_angular_velocity [default: /sensing/vehicle_velocity_converter/twist_with_covariance]
- input_objects [default: /perception/object_recognition/objects]
- validate_calibration_srv [default: validate_calibration]
- data_path [default: $(env HOME)/autoware_data/ml_models]
- model_name [default: calibration_status_classifier]
- model_path [default: $(var data_path)/calibration_status_classifier]
- model_param_path [default: $(find-pkg-share autoware_calibration_status_classifier)/config/$(var model_name).param.yaml]
- ml_package_param_path [default: $(var model_path)/ml_package_$(var model_name).param.yaml]
- build_only [default: false]
- use_sim_time [default: true]
- decompressor_param_file [default: $(find-pkg-share autoware_image_transport_decompressor)/config/image_transport_decompressor.param.yaml]
Messages
Services
Plugins
Recent questions tagged autoware_calibration_status_classifier at Robotics Stack Exchange
Package Summary
| Version | 0.53.0 |
| License | Apache License 2.0 |
| Build type | AMENT_CMAKE |
| Use | RECOMMENDED |
Repository Summary
| Description | |
| Checkout URI | https://github.com/autowarefoundation/autoware_universe.git |
| VCS Type | git |
| VCS Version | main |
| Last Updated | 2026-10-23 |
| Dev Status | UNKNOWN |
| Released | UNRELEASED |
| Contributing |
Help Wanted (-)
Good First Issues (-) Pull Requests to Review (-) |
Package Description
Maintainers
- Amadeusz Szymko
- Manato Hirabayashi
- Patiphon Narksri
Authors
- Amadeusz Szymko
autoware_calibration_status_classifier
Purpose
The autoware_calibration_status_classifier package provides real-time LiDAR-camera calibration validation using deep learning inference. It detects miscalibration between LiDAR and camera sensors by analyzing projected point clouds overlaid on camera images through a neural network-based approach.
Inner-workings / Algorithms
The calibration status detection system operates through the following pipeline:
1. Data Preprocessing (CUDA-accelerated)
- Image Undistortion: Corrects camera distortion
- Point Cloud Projection: Projects 3D LiDAR points onto undistorted 2D image plane - adds depth and intensity information
- Morphological Dilation: Enhances point visibility for neural network input
2. Neural Network Inference (TensorRT)
- Input Format: 5-channel normalized data (RGB + depth + intensity)
- Architecture: Deep neural network trained on calibrated/miscalibrated data
- Output: Binary classification with confidence scores for calibration status
3. Runtime Modes
- MANUAL: On-demand validation via service calls
- PERIODIC: Regular validation at configurable intervals
- ACTIVE: Continuous monitoring with synchronized sensor data
Inputs / Outputs
Input
| Name | Type | Description |
|---|---|---|
~/input/linear_velocity |
prerequisite.linear_velocity_check.source parameter |
Vehicle twist for linear velocity check (multiple message types supported) |
~/input/angular_velocity |
prerequisite.angular_velocity_check.source parameter |
Vehicle twist for angular velocity check (multiple message types supported) |
~/input/objects |
prerequisite.objects_check.source parameter |
Detected objects for objects check (multiple message types supported) |
input.cloud_topics |
sensor_msgs::msg::PointCloud2 |
LiDAR point cloud data |
input.image_topics |
sensor_msgs::msg::Image |
Camera image data (BGR8 format) |
| Camera info topics | sensor_msgs::msg::CameraInfo |
Camera intrinsic parameters and distortion coefficients |
Output
| Name | Type | Description |
|---|---|---|
/diagnostics |
diagnostic_msgs::msg::DiagnosticArray |
ROS diagnostics with calibration status |
~/validate_calibration_srv |
std_srvs::srv::Trigger |
Manual validation service (MANUAL mode) |
| Preview image topics | sensor_msgs::msg::Image |
Visualization images with projected points |
Services
| Name | Type | Description |
|---|---|---|
~/input/validate_calibration_srv |
std_srvs::srv::Trigger |
Manual calibration validation request |
Parameters
Node Parameters
{{ json_to_markdown(“sensing/autoware_calibration_status_classifier/schema/calibration_status_classifier.schema.json”) }}
Network Parameters
{{ json_to_markdown(“sensing/autoware_calibration_status_classifier/schema/ml_package_calibration_status_classifier.schema.json”) }}
Assumptions / Known Limits
- Input images must be in BGR8 format (8-bit per channel)
- Input point clouds should contain intensity information (XYZIRC format)
Usage Example
ros2 launch autoware_calibration_status_classifier calibration_status_classifier.launch.xml
Future Extensions / Unimplemented Parts
- Manual runtime mode with detailed response (custom srv)
- Replace filter for objects on the scene counter to objects within the camera FOV counter (raytracing)
- Multithreading for multiple camera-LiDAR pairs
- More filters (e.g. yaw rate)
- cuda_blackboard support
- Replace custom kernels with NPP functions where applicable
References
Changelog for package autoware_calibration_status_classifier
0.53.0 (2026-09-29)
- Merge remote-tracking branch 'origin/main' into prepare-0.53.0-changelog
- fix(design): align the sensing node designs with the packages they describe (#13337) CalibrationStatusClassifier declares a preview_image publisher on a hardcoded per-camera topic that the node no longer creates, and names it as the outcome of the classify process. The point cloud concatenation component is built as concatenate_pointclouds_node.
- refactor(sensing): move node design files into each package (#13105)
- Contributors: Ryohsuke Mitsudome, Taekjin LEE
0.52.0 (2026-06-30)
0.51.0 (2026-05-01)
-
Merge remote-tracking branch 'origin/main' into tmp/bot/bump_version_base
-
feat: default artifact paths to ~/autoware_data/ml_models (#12523) feat(launches,configs): default artifact paths to ~/autoware_data/ml_models Roll every per-package [data_path]{.title-ref} / [model_path]{.title-ref} launch-arg default from [$(env HOME)/autoware_data[/...]]{.title-ref} to [$(env HOME)/autoware_data/ml_models[/...]]{.title-ref} so standalone universe launches resolve artifacts under the new [~/autoware_data/ml_models/]{.title-ref} layout (autowarefoundation/autoware#7068). When invoked through autoware_launch the parent overrides cascade and already pin the new root (autowarefoundation/autoware_launch#1835); this commit closes the gap for users who launch a perception / localization / sensing / planning component directly with [ros2 launch <pkg>]{.title-ref}. 22 launch files updated (one-line default change each):
- e2e/autoware_tensorrt_vad/launch/vad_carla_tiny.launch.xml
- localization/yabloc/yabloc_pose_initializer/launch/yabloc_pose_initializer.launch.xml
- perception/autoware_bevfusion/launch/bevfusion.launch.xml
- perception/autoware_camera_streampetr/launch/streampetr.launch.xml
- perception/autoware_image_projection_based_fusion/launch/pointpainting_fusion.launch.xml
- perception/autoware_lidar_apollo_instance_segmentation/launch/lidar_apollo_instance_segmentation.launch.xml
- perception/autoware_lidar_centerpoint/launch/lidar_centerpoint.launch.xml
- perception/autoware_lidar_frnet/launch/lidar_frnet.launch.xml
- perception/autoware_lidar_transfusion/launch/lidar_transfusion.launch.xml
- perception/autoware_ptv3/launch/ptv3.launch.xml
- perception/autoware_shape_estimation/launch/shape_estimation.launch.xml
- perception/autoware_simpl_prediction/launch/simpl.launch.xml
- perception/autoware_tensorrt_bevdet/launch/tensorrt_bevdet.launch.xml
- perception/autoware_tensorrt_bevformer/launch/bevformer.launch.xml
- perception/autoware_tensorrt_yolox/launch/{yolox_traffic_light_detector,yolox_tiny,yolox_s_plus_opt}.launch.xml
- perception/autoware_traffic_light_classifier/launch/{car,pedestrian}_traffic_light_classifier.launch.xml
- perception/autoware_traffic_light_fine_detector/launch/traffic_light_fine_detector.launch.xml
- planning/autoware_diffusion_planner/launch/diffusion_planner.launch.xml
- sensing/autoware_calibration_status_classifier/launch/calibration_status_classifier.launch.xml Drive-by README and test fixes:
- e2e/autoware_tensorrt_vad/{README.md,docs/design.md}: also migrate the [$HOME/autoware_map/Town01]{.title-ref} examples to [$HOME/autoware_data/maps/Town01]{.title-ref}.
- localization/yabloc/{README.md,yabloc_pose_initializer/README.md}: also migrate [$HOME/autoware_map/sample-map-rosbag]{.title-ref} to [$HOME/autoware_data/maps/demos/sample-map-rosbag]{.title-ref}.
- control/autoware_smart_mpc_trajectory_follower/README.md: migrate the [map_path:=$HOME/autoware_map/sample-map-planning]{.title-ref} example to [$HOME/autoware_data/maps/demos/sample-map-planning]{.title-ref}.
- simulator/autoware_carla_interface/README.md: migrate every [$HOME/autoware_map/Town01/...]{.title-ref} reference to [$HOME/autoware_data/maps/Town01/...]{.title-ref}.
- perception/{autoware_bevfusion,autoware_image_projection_based_fusion,autoware_lidar_centerpoint,autoware_tensorrt_bevformer}/README.md: copy-paste examples updated to [~/autoware_data/ml_models/<pkg>]{.title-ref}.
- perception/autoware_camera_streampetr/config/ml_package_camera_streampetr.param.yaml: header comment updated.
- planning/autoware_diffusion_planner/README.md: prerequisites snippet updated.
- sensing/autoware_calibration_status_classifier/test/{test_model_inference,test_calibration_status_classifier}.cpp: hardcoded fallback ONNX path updated. Users on the legacy layout can pin the old root with [data_path:=$HOME/autoware_data]{.title-ref} (or the per-package equivalent) on the command line. Refs: https://github.com/autowarefoundation/autoware/issues/7068
-
feat(autoware_calibration_status_classifier): add angular velocity filter and refine filters design
File truncated at 100 lines see the full file
Package Dependencies
System Dependencies
| Name |
|---|
| libopencv-dev |
Dependant Packages
Launch files
- launch/calibration_status_classifier.launch.xml
-
- input_linear_velocity [default: /sensing/vehicle_velocity_converter/twist_with_covariance]
- input_angular_velocity [default: /sensing/vehicle_velocity_converter/twist_with_covariance]
- input_objects [default: /perception/object_recognition/objects]
- validate_calibration_srv [default: validate_calibration]
- data_path [default: $(env HOME)/autoware_data/ml_models]
- model_name [default: calibration_status_classifier]
- model_path [default: $(var data_path)/calibration_status_classifier]
- model_param_path [default: $(find-pkg-share autoware_calibration_status_classifier)/config/$(var model_name).param.yaml]
- ml_package_param_path [default: $(var model_path)/ml_package_$(var model_name).param.yaml]
- build_only [default: false]
- use_sim_time [default: true]
- decompressor_param_file [default: $(find-pkg-share autoware_image_transport_decompressor)/config/image_transport_decompressor.param.yaml]