navigation icon indicating copy to clipboard operation
navigation copied to clipboard

TrajectoryPlanner do not consider obstacles while generating escape velocities.

Open AravindaDP opened this issue 8 years ago • 6 comments

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.

AravindaDP avatar Aug 24 '16 09:08 AravindaDP

This is also discussed at http://answers.ros.org/question/217043/escape-velocity-robot-behavior-move_base/

AravindaDP avatar Sep 26 '16 15:09 AravindaDP

@DLu , @mikeferguson Thought you might be able to shed some light on this?

AravindaDP avatar Oct 31 '16 08:10 AravindaDP

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.

mikeferguson avatar Aug 01 '17 02:08 mikeferguson

Has been solved?

Cavalletta98 avatar Feb 13 '23 16:02 Cavalletta98

AFAIK, nobody has worked on this (it certainly hasn't been proposed as a PR to this repo even if they have)

mikeferguson avatar Feb 13 '23 17:02 mikeferguson

Can you please provide me an alternative planner that could not suffer of this problem?

Cavalletta98 avatar Feb 13 '23 17:02 Cavalletta98