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

AMCL, problem with clustering in west direction #27

Open
corot opened this issue Apr 5, 2013 · 3 comments
Open

AMCL, problem with clustering in west direction #27

corot opened this issue Apr 5, 2013 · 3 comments

Comments

@corot
Copy link
Contributor

corot commented Apr 5, 2013

While evaluating kidnap recovery through global_localization service, I have realized that almost never the best hypothesis points west-ward. After googling a bit, I found this in a player-stage project mailing list:

http://player-stage-gazebo.10965.n7.nabble.com/AMCL-problem-with-clustering-in-west-direction-td2731.html

Looks like an old, never solved problem.

@forouher
Copy link

forouher commented Apr 5, 2013

Interesting. Did you notice real-world consequences from this? E.g. wrong/bad localization in some scenario?

@corot
Copy link
Contributor Author

corot commented Apr 11, 2013

Not really; only when trying global localization. I suppose this is because on global localization is normally the only moment when there are particles pointing to any heading "competing" to be the best hypothesis

@VorpalBlade
Copy link

I ran into this separately while looking into how AMCL works. It should be reasonably easy to fix in the function pf_kdtree_cluster_node in pf_kdtree.cpp, which neighbor "buckets" from the KLD kd-tree algorithm are found by looking at the 3^3 buckets around the current one. There would simply have to be some wrap-around logic for nkey[2] (based on self->size[2] to determine when -pi/+pi are reached).

That should fix the problem.

nlimpert pushed a commit to nlimpert/navigation that referenced this issue Feb 25, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants