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

Ebandplanner fails when the global plan crosses an obstacle only present in the local one #5

Open
corot opened this issue Jun 14, 2013 · 4 comments
Assignees
Milestone

Comments

@corot
Copy link

corot commented Jun 14, 2013

This is a restriction of the approach, as it essentially combines global and local planning.
A possible solution would be to only use 1 costmap instead of 2.

@piyushk piyushk self-assigned this Mar 26, 2015
@piyushk piyushk added this to the 0.3.0 milestone Mar 26, 2015
@piyushk
Copy link
Member

piyushk commented Mar 26, 2015

I still haven't found a correct solution for this bug, but will attempt the following fix.

If the local plan receives a plan that it cannot convert to a band on first go, try clearing the costmaps first once. Clearing the costmaps typically resynchronizes the local and global costmap around the robot. I believe this should be as simple as calling costmap_ros_->resetLayers() and trying to convert the global plan to an elastic band in the local window again.

piyushk added a commit that referenced this issue Mar 26, 2015
@piyushk
Copy link
Member

piyushk commented Mar 30, 2015

The above solution seems to be working, but will likely require a lot more testing.

@jcmayoral
Copy link

hi. I am new about the topic and I am reading the documentation of ebandplanner but I cannot find the limitations or the considerations of the algorithms. I know that it combines the global and local planner but is there other limitation?

@ompugao
Copy link

ompugao commented Aug 2, 2016

i encountered this problem. how do you always debug these kind of problems?
how can i attach gdb and inspect what's going on exactly when 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

4 participants