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

drifted error of the ndt_omp #10

Open
weisongwen opened this issue Aug 1, 2019 · 5 comments
Open

drifted error of the ndt_omp #10

weisongwen opened this issue Aug 1, 2019 · 5 comments

Comments

@weisongwen
Copy link

Hi @koide3 , thanks for sharing your work to the community. I have test the accuracy og the ndt-omp and the conventional ndt in pcl. the ndt_omp seems to drift in z axis dramatically compared with the conventioanl NDT in pcl. have you find this ?

is this caused by the searching method in the ndt_omp?

Best,
Welson,

@koide3
Copy link
Owner

koide3 commented Aug 5, 2019

Hi @weisongwen ,
I didn't notice such error. Is that error transnational? or it's rotational? Do you see the error when you use pclomp::KDTREE method? With this method, the result should become the same as the pcl implementation.

@weisongwen
Copy link
Author

Hi @koide3, yes. the drift is mainly the translation error in z axis using the Direct7 search.

@koide3
Copy link
Owner

koide3 commented Aug 9, 2019

Hmm, unfortunately, I've not met this problem yet and have no idea... Let me confirm that you didn't see this problem with pclomp::KDTree, right?

@weisongwen
Copy link
Author

Hi @koide3 . exactly, the probelm also see in pclomp::KDTree. The drift in accumulated at a larger speed compared with the very conventional NDT in PCL, for example the one in Autoware. Can this be cuased due to the keyframe selection in hdl_gra_slam. In the conventional NDT in Autoware, all the frames of point clouds are applied to calculate the consecutive transformation,

Best,
Welson,

@koide3
Copy link
Owner

koide3 commented Aug 14, 2019

Possibly it is a problem of the accumulation algorithm rather than the scan matching algorithm as you said. But, I have no idea why it happens...

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