ROS Resources: Documentation | Support | Discussion Forum | Index | Service Status | ros @ Robotics Stack Exchange |
1 | initial version |
the inflation_radius
and cost_saling_factor
parameters should go under the inflater_layer
in both global and local costmap params files like this:
inflater_layer:
inflation_radius: 3.0
cost_scaling_factor: 1.0
You should have this in each global and local costmap files only if you want different inflation for them.
You should still use the cosmtap_common_params
file since it is there that you usually put the frame, footprint and plugins params. For example in your cosmtap_common_params
you should have something like this:
global_frame: map
robot_base_frame: base_link
footprint: [[-1.5, -1.1], [-1.5, 1.1], [1.5, 1.1], [1.5,-1.1]]
footprint_padding: 0.1
plugins:
- {name: static_map, type: "costmap_2d::StaticLayer"}
- {name: inflater_layer, type: "costmap_2d::InflationLayer"}
inflater_layer:
inflation_radius: 1.5
cost_scaling_factor: 2.0
2 | No.2 Revision |
the inflation_radius
and cost_saling_factor
parameters should go under the inflater_layer
in both global and local costmap params files like this:
inflater_layer:
inflation_radius: 3.0
0.5
cost_scaling_factor: 1.0
You should have this in each global and local costmap param files only if you want different inflation for them.
You should still use the cosmtap_common_params
file since it is there that you usually put the frame, footprint and plugins params. For example in your cosmtap_common_params
you should have something like this:
global_frame: map
robot_base_frame: base_link
footprint: [[-1.5, -1.1], [-1.5, 1.1], [1.5, 1.1], [1.5,-1.1]]
footprint_padding: 0.1
plugins:
- {name: static_map, type: "costmap_2d::StaticLayer"}
- {name: inflater_layer, type: "costmap_2d::InflationLayer"}
inflater_layer:
inflation_radius: 1.5
0.5
cost_scaling_factor: 2.0
1.0
If you want to have the same inflation for both global and local costmap then you put the params in the common_costmap file like it is shown above.
3 | No.3 Revision |
the inflation_radius
and cost_saling_factor
parameters should go under the inflater_layer
in both global and local costmap params files like this:
inflater_layer:
inflation_radius: 0.5
cost_scaling_factor: 1.0
You should have this in each global and local costmap param files only if you want different inflation for them.
You should still use the cosmtap_common_params
file since it is there that you usually put the frame, footprint and plugins params. For example in your cosmtap_common_params
you should have something like this:
global_frame: map
robot_base_frame: base_link
map_topic: /map
footprint: [[-1.5, -1.1], [-1.5, 1.1], [1.5, 1.1], [1.5,-1.1]]
[[0.12, 0.14], [0.12, -0.14], [-0.12, -0.14], [-0.12, 0.14]]
footprint_padding: 0.1
plugins:
- {name: static_map, type: "costmap_2d::StaticLayer"}
- {name: inflater_layer, type: "costmap_2d::InflationLayer"}
inflater_layer:
inflation_radius: 0.5
cost_scaling_factor: 1.0
If you want to have the same inflation for both global and local costmap then you put the params in the common_costmap file like it is shown above.
4 | No.4 Revision |
the inflation_radius
and cost_saling_factor
parameters should go under the inflater_layer
in both global and local costmap params files like this:
inflater_layer:
inflation_radius: 0.5
0.2
cost_scaling_factor: 1.0
You should have this in each global and local costmap param files only if you want different inflation for them.
You should still use the cosmtap_common_params
file since it is there that you usually put the frame, footprint and plugins params. For example in your cosmtap_common_params
you should have something like this:
global_frame: map
robot_base_frame: base_link
map_topic: /map
footprint: [[0.12, 0.14], [0.12, -0.14], [-0.12, -0.14], [-0.12, 0.14]]
footprint_padding: 0.1
0.03
plugins:
- {name: static_map, type: "costmap_2d::StaticLayer"}
- {name: inflater_layer, type: "costmap_2d::InflationLayer"}
inflater_layer:
inflation_radius: 0.5
0.2
cost_scaling_factor: 1.0
If you want to have the same inflation for both global and local costmap then you put the params in the common_costmap file like it is shown above.
5 | No.5 Revision |
the inflation_radius
and cost_saling_factor
parameters should go under the inflater_layer
in both global and local costmap params files like this:
inflater_layer:
inflation_radius: 0.2
cost_scaling_factor: 1.0
You should have this in each global and local costmap param files only if you want different inflation for them.
You should still use the cosmtap_common_params
file since it is there that you usually put the frame, footprint and plugins params. For example in your cosmtap_common_params
you should have something like this:
global_frame: map
robot_base_frame: base_link
map_topic: /map
footprint: [[0.12, 0.14], [0.12, -0.14], [-0.12, -0.14], [-0.12, 0.14]]
footprint_padding: 0.03
plugins:
- {name: static_map, static_layer, type: "costmap_2d::StaticLayer"}
- {name: inflater_layer, type: "costmap_2d::InflationLayer"}
static_layer: map_topic: /map subscribe_to_updates: true
obstacles_layer: observation_sources: laser_scan_sensor laser_scan_sensor: {sensor_frame: laser_frame, data_type: LaserScan, topic: scan, marking: true, clearing: true, obstacle_range: 6.0, raytrace_range: 8.5}
inflater_layer:
inflation_radius: 0.2
cost_scaling_factor: 1.0
If you want to have the same inflation for both global and local costmap then you put the params in the common_costmap file like it is shown above.
6 | No.6 Revision |
the inflation_radius
and cost_saling_factor
parameters should go under the inflater_layer
in both global and local costmap params files like this:
inflater_layer:
inflation_radius: 0.2
cost_scaling_factor: 1.0
You should have this in each global and local costmap param files only if you want different inflation for them.
You should still use the cosmtap_common_params
file since it is there that you usually put the frame, footprint and plugins params. For example in your cosmtap_common_params
you should have something like this:
global_frame: map
robot_base_frame: base_link
footprint: [[0.12, 0.14], [0.12, -0.14], [-0.12, -0.14], [-0.12, 0.14]]
footprint_padding: 0.03
plugins:
- {name: static_layer, type: "costmap_2d::StaticLayer"}
- {name: inflater_layer, type: "costmap_2d::InflationLayer"}
static_layer: map_topic: /map subscribe_to_updates: true
obstacles_layer: observation_sources: laser_scan_sensor laser_scan_sensor: {sensor_frame: laser_frame, data_type: LaserScan, topic: scan, marking: true, clearing: true, obstacle_range: 6.0, raytrace_range: 8.5}
inflater_layer:
inflation_radius: 0.2
cost_scaling_factor: 1.0
If you want to have the same inflation for both global and local costmap then you put the params in the common_costmap file like it is shown above.
7 | No.7 Revision |
the inflation_radius
and cost_saling_factor
parameters should go under the inflater_layer
in both global and local costmap params files like this:
inflater_layer:
inflation_radius: 0.2
cost_scaling_factor: 1.0
You should have this in each global and local costmap param files only if you want different inflation for them.
You should still use the cosmtap_common_params
file since it is there that you usually put the frame, footprint and plugins params. For example in your cosmtap_common_params
you should have something like this:
static_layer:
map_topic: /map
subscribe_to_updates: true
obstacles_layer:
If you want to have the same inflation for both global and local costmap then you put the params in the common_costmap file like it is shown above.
8 | No.8 Revision |
the inflation_radius
and cost_saling_factor
parameters should go under the inflater_layer
in both global and local costmap params files like this:
inflater_layer:
inflation_radius: 0.2
cost_scaling_factor: 1.0
You should have this in each global and local costmap param files only if you want different inflation for them.
You should still use the cosmtap_common_params
file since it is there that you usually put the frame, footprint and plugins params. For example in your cosmtap_common_params
you should have something like this:
global_frame: map
robot_base_frame: If you want to have the same inflation for both global and local costmap then you put the params in the common_costmap file like it is shown above.