You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Mar 28, 2025. It is now read-only.
I've searched other issues and no duplicate issues were found.
I'm convinced that this is not my fault but a bug.
Description
The lidar preprocessing pipeline is broken if use_concat_filter is set to false. In the preprocessor launch file, it is suggested that if the concatenate filter is not used then a passthrough filter is launch. However it is not the case:
This would leave the lidar pipeline broken, has /sensing/lidar/top/outlier_filtered/pointcloud messages are not forwarded to /sensing/lidar/concatenated/pointcloud (which is hardcoded everywhere in other autoware modules).
Either a passthrough should be added, or the option should rather be removed?
Expected behavior
Since use_concat_filter is an option, we should be able to use it.
Checklist
Description
The lidar preprocessing pipeline is broken if
use_concat_filteris set tofalse. In the preprocessor launch file, it is suggested that if the concatenate filter is not used then a passthrough filter is launch. However it is not the case:sample_sensor_kit_launch/sample_sensor_kit_launch/launch/pointcloud_preprocessor.launch.py
Lines 68 to 73 in 417f7ce
This would leave the lidar pipeline broken, has
/sensing/lidar/top/outlier_filtered/pointcloudmessages are not forwarded to/sensing/lidar/concatenated/pointcloud(which is hardcoded everywhere in other autoware modules).Either a passthrough should be added, or the option should rather be removed?
Expected behavior
Since
use_concat_filteris an option, we should be able to use it.Actual behavior
use_concat_filter:=falsedoes not work.Steps to reproduce
N/A
Versions
No response
Possible causes
No response
Additional context
No response