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
Hello, I noticed a bug on the lidar sensor : if simulation frequency is higher than lidar frequency, the published lidar point cloud will only contains data produced on the last simulation tick, and will then be incomplete.
I have written a simple fix for that, which stack the produced lidar data when the simulation ticks and publish the whole packet when the sensors ticks. I would be happy to do a pull request if possible.
Best regards,
Paul
The text was updated successfully, but these errors were encountered:
Paul-Nico
pushed a commit
to Paul-Nico/ros-bridge
that referenced
this issue
Jun 8, 2023
Thank you for this branch! I stumbled over this problem some months ago and you just made my day!
I also ported it to the semantic lidar. Works like a charm :)
Thank you for this branch! I stumbled over this problem some months ago and you just made my day! I also ported it to the semantic lidar. Works like a charm :)
Hello, I noticed a bug on the lidar sensor : if simulation frequency is higher than lidar frequency, the published lidar point cloud will only contains data produced on the last simulation tick, and will then be incomplete.
I have written a simple fix for that, which stack the produced lidar data when the simulation ticks and publish the whole packet when the sensors ticks. I would be happy to do a pull request if possible.
Best regards,
Paul
The text was updated successfully, but these errors were encountered: