Ask Your Question

Advantage of adding costmap_2d::ObstacleLayer plugin to global costmap

asked 2020-12-25 02:54:41 -0600

I was going through this Husky Navigation tutorial. This tutorial allows us how to navigate the Husky bot without using a map.

It has 3 yaml files for configuring the costmaps - costmap_global_laser.yaml (for global costmap) , costmap_local.yaml (for local costmap) and costmap_common.yaml (for both global and local costmap).

This is how costmap_local.yaml looks-

global_frame: odom
rolling_window: true

  - {name: obstacles_laser,           type: "costmap_2d::ObstacleLayer"}
  - {name: inflation,                        type: "costmap_2d::InflationLayer"}

This is how costmap_global_laser.yaml looks-

global_frame: odom
rolling_window: true
track_unknown_space: true

  - {name: obstacles_laser,           type: "costmap_2d::ObstacleLayer"}
  - {name: inflation,                       type: "costmap_2d::InflationLayer"}

Why have we added an costmap_2d:ObstacleLayer to the costmap_global_laser.yaml when it is already included in the costmap_local.yaml? Are there any advantages in terms of path planning?

edit retag flag offensive close merge delete

1 Answer

Sort by ยป oldest newest most voted

answered 2021-01-12 04:05:20 -0600

drtritm gravatar image

The "costmap_2d:ObstacleLayer" in global costmap will "add" obstacle into global costmap, which resultes that global planner will plan a path to avoid that obstacle

edit flag offensive delete link more


Makes sense. Thanks!

skpro19 gravatar image skpro19  ( 2021-01-12 05:00:12 -0600 )edit

Your Answer

Please start posting anonymously - your entry will be published after you log in or create a new account.

Add Answer

Question Tools

1 follower


Asked: 2020-12-25 02:54:41 -0600

Seen: 20 times

Last updated: Jan 12