ROS Resources: Documentation | Support | Discussion Forum | Index | Service Status | ros @ Robotics Stack Exchange |
1 | initial version |
don't include obstacles layer in the costmap_common_params_covid or global_costmap_params insert it only in local_costmap_params
I mean this part or alternative depend on how you configure your obstacles layer
observation_sources: scan scan: {sensor_frame: base_scan, data_type: LaserScan, topic: scan, marking: true, clearing: true}
2 | No.2 Revision |
don't include obstacles layer in the costmap_common_params_covid costmap_common_params or global_costmap_params insert it only in local_costmap_params
I mean this part or alternative depend on how you configure your obstacles layer
observation_sources: scan scan: {sensor_frame: base_scan, data_type: LaserScan, topic: scan, marking: true, clearing: true}
3 | No.3 Revision |
don't include obstacles layer in the costmap_common_params or global_costmap_params insert it only in local_costmap_params
I mean this part or alternative depend on how you configure your obstacles layer
observation_sources: scan scan: {sensor_frame: base_scan, data_type: LaserScan, topic: scan, marking: true, clearing: true}
how ever it'll effect global path planner behavior. otherwise you can clear using this service
rosservice call /move_base/clear_costmaps "{}"
4 | No.4 Revision |
don't include obstacles layer in the costmap_common_params or global_costmap_params insert it only in local_costmap_params
I mean this part or alternative depend on how you configure your obstacles layer
observation_sources: scan scan: {sensor_frame: base_scan, data_type: LaserScan, topic: scan, marking: true, clearing: true}
how ever however it'll effect global path planner behavior. otherwise you can clear using this service
rosservice call /move_base/clear_costmaps "{}"