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

Added logic to handle "ring" field for velodyne lidars #452

Merged
merged 13 commits into from
Oct 2, 2023

Conversation

VineetTambe
Copy link

In the context to this issue - I have added logic to calculate the "ring" value based on the N_SCANS field and have tested the code out on Velodyne 16.
In addition, I have tried to keep the changes such that it does not affect results for ouster or other lidars but still can be extended easily to other lidars by setting ringFlag = 2

Please let me know if you have any feedback and need me to update the PR.

@grischi
Copy link
Collaborator

grischi commented Sep 27, 2023

Hi @VineetTambe , thank you very much for submitting this PR! Just a tiny little thing: Would you mind fixing the whitespace errors?

@VineetTambe
Copy link
Author

Hi @VineetTambe , thank you very much for submitting this PR! Just a tiny little thing: Would you mind fixing the whitespace errors?

Hey @grischi, I have resolved the whitespacing issue. Please let me know if there are any other changes.

@grischi grischi merged commit 9d039fd into TixiaoShan:ros2 Oct 2, 2023
@wxyLuna2024
Copy link

wxyLuna2024 commented Jul 23, 2024

Thank you soo much for your work!! It saved me. I am trying to feed KITTI360 into LIOSAM and the ROS2 bag converter I used is under KITTI format which doesn't have ring info

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

Successfully merging this pull request may close these issues.

3 participants