-
Notifications
You must be signed in to change notification settings - Fork 308
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
Differences between KDTREE and DIRECT7 #24
Comments
Did you see the same issue with DIRECT1 as well? |
Yes, DIRECT1 performed similar with DIRECT7. |
Hmm, can you try a small |
We have just found whrere the problem is. It turns out it has noting to do with search method. |
May I ask what the actual problem is? |
Hi,
Sorry to bother you. Thanks to your great package, I have ran a version of robot localization successfully with NDT in ndt_omp. During my tests, I found something different in performance between KDTREE and DIRECT7, but I found it difficult to explain.
I ran a diff-driven robot with a 2d laser in a static environment on the same path with same 2d map. I ran my robot with DIRECT7, the laser scan did not match the map well while I ran with KDTREE, the laser scan match better.
Here are two pictures of matching with KDTREE and DIRECT7.
KDTREE match below.
DIRECT7 match below.
I really can not think about a reason to explain this phenomenon. I would be so grateful if you could offer some help on it.
Best regards.
The text was updated successfully, but these errors were encountered: