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

Problems on integration of localization to ros navigation stack (move-base) #41

Open
jojo89776 opened this issue Jun 28, 2021 · 2 comments

Comments

@jojo89776
Copy link

First of all, I really appreciate the release of this wonderful mapping and localization package.
Currently, I'm working on an exchange amcl-based localization tool with this iris-lama-ros package.
However, when I was using this package with move base (ros navigation stack), I got the error message "Extrapolation Error: Lookup would require extrapolation into the future". (When using amcl-based localization, there was no error).
Do you have any idea to solve, or did you have any experience with such problems?
(I tried comment tf-broadcaster on localization node, but nothing changed).
It will be greatly helpful if you (or someone) can give any comments!

@eupedrosa
Copy link
Member

Hi @jojo89776, thanks for you kind words about LaMa.

I usually do not have an "Extrapolation Error" when using the localization node. Commenting the tf-broadcaster will not solve the problem, in fact, it makes it worse. Are you using melodic or noetic?

There is a parameter called ~transform_tolerance, try increase it to a higher value than 0.1 (eg 0.2 or 0.3).

@jojo89776
Copy link
Author

Thank you for the comment.
Actually, when I used localization only, there was no error and the algorithm worked perfectly.
This error occurs when I was using the lama-ros localization with move-base (Extrapolation error on local planner).
I will change transform tolerance and figure out the problems.

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