-
-
Notifications
You must be signed in to change notification settings - Fork 378
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
Implementation on velodyne lidar #64
Comments
If you have your own driver for a lidar, you can definitely implement it in a way where it gives you the image (or rather multiple small "scan" images). If you don't own a driver, it depends on what it provides you. Projecting the data takes really not that long even if you only have a point cloud. Definitely enough for prototyping, and if you actually want to use this in production, you should probably have your own driver. |
We have Velodyne LiDAR sensor but can you please clarify, what exactly you mean by "driver"? |
The driver is the software that interprets the data coming directly from the sensor and creates a useful representation that is used further down the line, i.e., to point clouds. |
Thanks for ur reply. I am getting a run time of approx. 0.02 second for each frame on 32GB RAM system. Is this run time justified or could there be a problem in implementation , in ur opinion? |
The amount of RAM is relatively irrelevant here. The crucial factor is what is your processor. Otherwise, you are getting around 50fps, which seems rather slow. What are you measuring? I will close this issue, but feel free to continue the discussion here. |
I am using Velodyne (VLP-32C) Lidar. Could you please let me know, if this Lidar gives range data (as 32 rows and many columns, used in your method) or I need to create this kind of format using the point cloud. Creating a cylindrical projection from a point cloud increases the run time to great extent..
The text was updated successfully, but these errors were encountered: