Obstacle Avoidance vs Detection in Navigation Stack

asked 2014-11-14 16:48:27 -0500

ROSCMBOT
651 ●45 ●53 ●59

updated 2014-11-14 16:49:53 -0500

Hello,

I was wondering if any sort of obstacle detection is happening in the navigation stack. As I understand, when an obstacle is appearing within laser range, it's updated in the local/global costmap, and the robot is doing obstacle avoidance by keep generating a global path (A* or Dijkstra) and moving along the new path, but does the robot know whether a new obstacle appeared on its path or not (or Does the robot detect the Obstacle?)

Thanks

answered 2014-11-14 20:09:04 -0500

fergs

13902 ●59 ●157 ●196 http://www.robotandchisel.com

The robot doesn't really "know" or "reason" much about obstacles. It simply knows that "something" is at a particular location in the costmap and therefore it cannot go through it, but the default costmaps only reason about the occupancy of a particular grid, it doesn't do anything at the object level.

That said, there has been some work on higher level stuff. David Lu originally started on the layered costmap approach so that he could integrate a layer that understands and tracks where people are, allowing more reasoning about the obstacles. So, it is possible to do this kind of object tracking, but it's not part of the default navigation components.

edit flag offensive delete link

Comments

Thanks a lot. If we don't really care about the exact location of the obstacles, but merely the fact that some new obstacles appeared on the cost map, can we find this out by keep comparing the old and new (global?) costmaps?

ROSCMBOT ( 2014-11-14 21:14:53 -0500 )edit

add a comment

Obstacle Avoidance vs Detection in Navigation Stack

1 Answer

Comments

Question Tools

Stats

Related questions

Obstacle Avoidance vs Detection in Navigation Stack edit

1 Answer

Comments

Question Tools

Stats

Related questions

Obstacle Avoidance vs Detection in Navigation Stack