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

data accuary problem #19

Open
sakurazhu opened this issue Aug 11, 2017 · 1 comment
Open

data accuary problem #19

sakurazhu opened this issue Aug 11, 2017 · 1 comment

Comments

@sakurazhu
Copy link

sakurazhu commented Aug 11, 2017

hi ,after reading your paper and code , there is little thing about how to change .pcap to .pcd . when i did my work ,i use rosbag (https://github.com/ros-drivers/velodyne ) to change the data format,because the data i got from velodyne 16 is .pcap format. 
But when i changed the format ,i found that the accuracy of the data has decrease for example the data in .pcap is 2.0909876583 but in .pcd is 2.0909 . i have tried to change the type of the points from float to double ,but the result seemed worse .I wonder if you met the same problems ,could you please give me some suggestions .thank you very much for your kindness.
@martin-velas
Copy link
Contributor

Hi! I have not noticed this. Actually, I can not imagine the problems, which can be caused by this "lost" of precision. The difference between 2.0909876583 (meters) and 2.0909m is actually smaller than 0.1mm. This seems to be quite insignificant comparing for example to the magnitude of common noise (~2cm) of this sensor caused by mechanical properties.
So I think you do not need to deal with these differences in precision. Unfortunately this is the only advice I'm able to give you.

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

No branches or pull requests

2 participants