-
Notifications
You must be signed in to change notification settings - Fork 3.4k
Description
Checklist
- I've read the contribution guidelines.
- I've searched other issues and no duplicate issues were found.
- I'm convinced that this is not my fault but a bug.
Description
Once the initial pose is set, the vehicle appears correctly positioned and oriented on the map. The /sensing/lidar/concatenated/pointcloud topic (XYZIRC format) publishes data at approximately 10.5 Hz. Shortly afterward, the /localization/util/crop_box_filter_measurement_range, voxel_grid_downsample_filter, and random_downsample_filter components crash. As a result, the ndt_scan_matcher is unable to update the EKF.
Expected behavior
The expected behavior is that /localization/util/crop_box_filter_measurement_range, voxel_grid_downsample_filter, and random_downsample_filter components don't crash and ndt_scan_matcher updates EKF.
Actual behavior
The actual behavior is that /localization/util/crop_box_filter_measurement_range, voxel_grid_downsample_filter, and random_downsample_filter components crash and update counter on EKF keeps counting.
Steps to reproduce
ros2 launch autoware_launch autoware.launch.xml map_path:=ds_autoware_maps/research_drive vehicle_model:=pacifica_vehicle sensor_model:=pacifica_sensor_kit
- Set initial pose in RVIZ
- Watch EKF not update in rqt_robot_monitor
Versions
- OS: 22.04
- ROS2 Humble
- Autoware: main
Possible causes
Something with the pointcloud topic not being accepted. Initial pose is populating and that is the pose when the /localization/util pipeline dies.
Additional context
I am running a single Ouster lidar.