You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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.
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?
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.
The text was updated successfully, but these errors were encountered: