Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

LaserScan Display is transforming messages in an unexpected way #1315

Open
john-maidbot opened this issue Dec 24, 2024 · 0 comments
Open

LaserScan Display is transforming messages in an unexpected way #1315

john-maidbot opened this issue Dec 24, 2024 · 0 comments

Comments

@john-maidbot
Copy link

john-maidbot commented Dec 24, 2024

Hello,

Currently, the rviz2 LaserScan plugin converts laser scans to pointclouds for visualization using the laser_geometry package: https://github.com/ros-perception/laser_geometry/blob/71ba748322a38821eca58e79aeec475379026b68/src/laser_geometry.cpp#L416C23-L416C54

If I publish a laserscan, I would expect that it would be visualized as a pointcloud in the frame listed in the message header. (i.e. convert the range measurements to points in the sensor frame, and rigidly transform all those points into the frame I am currently visualizing).

However, since rviz2 is using transformLaserScanToPointCloud, something else is happening.
(https://github.com/ros2/rviz/blame/be68734b712dbc0f1f556d520bb993eb954fdaff/rviz_default_plugins/src/rviz_default_plugins/displays/laser_scan/laser_scan_display.cpp#L102)

transformLaserScanToPointCloud does the following (oversimplifying for brevity):

I think that this behavior distorts the users understanding of the information held in the laser scan. Additionally, the user might have a different algorithm for handling the per point transformation of points in the laser scan, which would conflict with the transformation rviz is doing under the hood (though in that case you could just set the scan time to 0).

Would you be opposed to providing users an option to enable/disable this behavior?

Thank you for your time.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant