Closed ZhengXinyue closed 2 years ago
Hi @ZhengXinyue Thanks for your points. I think there's a bug in the ROS implementation. Let me double-check the issue.
@ZhengXinyue Heyy, i am facing the same issue with the Ouster OS-1, just wanted to know whether you solved it ? :)
@ZhengXinyue Heyy, i am facing the same issue with the Ouster OS-1, just wanted to know whether you solved it ? :)
No, the author doesn't reply since then. @rohithsaro
@ZhengXinyue Any updates ? I tried to use VLP-16 publishing message into the ROS extension, but it can not detect any object and I believe it's because of that intensity divider value ! I didn't get any response from @AhmedARadwan as well :(.
Hi, thanks for your excellent work and I have successfully made it work with kitti dataset.
But in the ros version, the pointcloud data process is a little different:
The intensity is divided by 100.
Is this because the pointcloud in kitti dataset has been divided by 100 when collected and stored? So it also needs this division in the ros version?
I also notice that the range of pointcloud in kitti dataset is [0, 0.99] as is showed in rviz, so does it really needs to be divided by 100? And when training with pointcloud, the code does not do any data augmentation...
Finally, my lidar is not Velodyne-64, it is Ouster OS-1, I find that the intensity range in a scene is from 0 to about 3300, far away from [0, 0,99], what should I do to keep the data distribution consistent? Divide it by the max intensity and then divide it by 100 to make it distributed in [0, 0.99]? I don't know...