Skip to content
Open
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
30 changes: 29 additions & 1 deletion spot_navigation/config/spot.yaml
Original file line number Diff line number Diff line change
Expand Up @@ -261,14 +261,42 @@ spot_nav/local_costmap:
obstacle_layer:
plugin: "nav2_costmap_2d::ObstacleLayer"
enabled: True
observation_sources: velodyne
observation_sources: velodyne frontleft frontright left right
velodyne:
topic: /velodyne_points
min_obstacle_height: 0.20
max_obstacle_height: 1.2
clearing: True
marking: True
data_type: "PointCloud2"
frontleft:
topic: /spot_pointclouds/frontleft_points
min_obstacle_height: 0.20
max_obstacle_height: 2.0
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Any particular reason to use 2.0 as the max height here instead of the 1.2 used for the lidar?

Copy link
Copy Markdown
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I tested navigation with the point clouds active. However, at the time I made the change, the commit I was in had 2.0 as the max height used for the lidar. I'll make the change and test navigation again

clearing: True
marking: True
data_type: "PointCloud2"
frontright:
topic: /spot_pointclouds/frontright_points
min_obstacle_height: 0.20
max_obstacle_height: 2.0
clearing: True
marking: True
data_type: "PointCloud2"
left:
topic: /spot_pointclouds/left_points
min_obstacle_height: 0.20
max_obstacle_height: 2.0
clearing: True
marking: True
data_type: "PointCloud2"
right:
topic: /spot_pointclouds/right_points
min_obstacle_height: 0.20
max_obstacle_height: 2.0
clearing: True
marking: True
data_type: "PointCloud2"
voxel_layer:
plugin: "nav2_costmap_2d::VoxelLayer"
enabled: True
Expand Down