-
Notifications
You must be signed in to change notification settings - Fork 951
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
Add velodyne HDL (32,64) support #10
Comments
Hi, Where can I get the LOAM that supports HDL 32 and 64? Did anyone work on it? |
You can add the feature by editing scanRegistration.cpp by :
You also have to increase the size of some array : (max number of points during a sweep)
Don't forget to add the velodyne_pointcloud in the CMakeLists and in the package.xml ;) |
The code above fails to compile when copied as-is. Does this work on your system and is that all the code required? E.g. "velodyne_pointcloud" isn't defined. On my system it fails with the following error:
|
Please read the error ;) you forgot to add velodyne_pointcloud in the CMakeList and in your package.xml. |
Ah, I'm sorry. I didn't realize velodyne_pointcloud was a separate package. I did also need to include the header files to make LOAM compile properly, so these lines also need to be added at the top of scanRegistration.cpp:
Now everything compiles and I can run LOAM over a bagfile! So thank you very much for your help @ClementLeBihan , I really appreciate it! I do have to ask though, when LOAM runs, the topic |
I’m really happy you succeed ;) |
@msy22 Can you share the code that worked for you? |
With the proposed changes, do we also have to increase N_SCANS to 32 or 64 respectively? |
Yes of course, to 32 or 64 ;) |
Thanks, I got it to working as well! Any thoughts on saving the high resolution map as PCD? My thoughts are to save the /after_mapped_to_init to a file and then play the bag file and create an accumulated map by projecting each point cloud with the estimated odometry. Is there any other easier way ? |
You can save all the registered cloud in laserMapping.cpp in the camera_init frame ;)
|
@saimanoj18 You can also use the command @ClementLeBihan That looks useful. What file should we put that code in and where? The topic of this issue is drifting away from its original subject (HDL-32 support) but it looks like saving the map is a common issue people are having (me included), so would it be better to document all this in a separate issue or in the readme.md file? |
@ClementLeBihan I have modified codes as add HDL64 support #11 |
@lowmee hi , Is your problem solved? I seem to have encountered the same problem with VLP-16. |
Hi, I tried to test it with KITTI dataset, but failed. I debugged the node and found that KITTI dataset just provide 4 values (x y z intensity) without rings. Do you have any idea that how to put points into different rings as what does with VLP-16 Lidar? Looking forward to your reply! |
@ClementLeBihan Hi , I Imodified the code as you provided . However, when i use 'rosbag play xxx.bag',which is a velodyne-64 bag, it failed as follows : process[rviz-7]: started with pid [14273] Do you have any idea about it ? Looking forward to your reply. |
@Xpeipei |
@LiShuaixin HI, do you succeed testing with KITTI? I‘m trying to test LOAM with KITTI recently. To get the code usable with KITTI , I sort the points into 64 scans just like the code did but the intervals of the scans are changed according to the Velodyn64E manual. However, I havn't get a good result, the error is much more than 0.68% as it showed on the ranking list. Do you have any idea about it ? |
@zjuluolun |
@seanM29 |
@zjuluolun Can you share what changes did you make ? |
@saimanoj18 I dont know which step you have reached now, but in general, you should first sort 64 lines precisely from the lidar data to guarantee the correct feature extraction. When you evaluate your result, you should align the lidar frame to the camera frame according to the calibration file. |
Hi does anyone have it working with the hdl64 and is willing to share their code? |
@CtfChan I am trying to reproduce the same results of the KITTI Vision Benchmark, but I am not getting it. You can checkout my modified version of loam_velodyne to run with the KITTI dataset here: https://github.com/claydergc/loam_velodyne_kitti |
@zjuluolun I‘m trying to test LOAM with KITTI recently.But did not get a good result.Can you share what change did you make? Or uploading your code in your github. |
did you fix it?I met the same problem... |
We need to test and merge the following forks:
HDL32 https://github.com/smori/loam_velodyne/commit/774d5117ffc7662cd30ef831be9ce82b6985d5df
HDL64 https://github.com/YANG-H/loam_velodyne/commit/ba1d606d2ec62d48be484c28f71d8f29a08b9ab5
[vlp16, hdl32, hdl64] should be added as a param to .launch file
The text was updated successfully, but these errors were encountered: