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
TrajectoryPlanner do not consider obstacles while generating escape velocities. #516
Comments
This is also discussed at http://answers.ros.org/question/217043/escape-velocity-robot-behavior-move_base/ |
@DLu , @mikeferguson |
I think the notion was: most robots had a single forward-facing laser and didn't have sensors behind them, and so they probably have an inaccurate understanding of the world back there so checking the costmap was already fairly useless. That's probably no longer the case in many cases, and so adding (optional) costmap checking sounds like a great enhancement. Pull requests welcomed. |
Has been solved? |
AFAIK, nobody has worked on this (it certainly hasn't been proposed as a PR to this repo even if they have) |
Can you please provide me an alternative planner that could not suffer of this problem? |
* various improvements across docs website * build issues fix
It appears that when TrajectoryPlanner generates escape trajectories, It do not consider the costmap obstacles.
https://github.com/ros-planning/navigation/blob/indigo-devel/base_local_planner/src/trajectory_planner.cpp#L910
Is this by design? I think this behavior need to be at least made configurable so that users could choose to whether or not to consider costmap obstacles when escaping.
The text was updated successfully, but these errors were encountered: