Repository navigation
Add easynav_bigmap_maps_manager: a NavMap fine around the robot and coarse far away - #180
Closed
jmguerreroh wants to merge 2 commits into
Closed
jmguerreroh wants to merge 2 commits into
jmguerreroh wants to merge 2 commits into
Conversation
Contributor
Author
|
Superseded by #183: a different design built on NavMap's own tools. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Split out of #177, as suggested. As discussed there, I think it belongs under
maps_managers/next to the other maps managers, but it needs NavMap changes that are not in NavMap rolling yet (EasyNavigation/NavMap#), so I'd merge it once those are in. Happy to host it elsewhere if you prefer.What
A new maps manager plugin,
easynav_bigmap_maps_manager/BigMapMapsManager(parameter namespacebigmap), for maps too big to plan on at full resolution. It holds one NavMap that is fine around the robot and coarse far away, re-meshes it as the robot moves, and puts the obstacles seen by the sensors on it. Planners and controllers read it from the NavState (map.navmap) like any other NavMap.occupancy,obstacles,inflated_obstacles,obstacle_hits,elevation,lod_size,traversedand vertex colours, published on<node>/bigmap/map.lengths.cell_size.minnear the robot up tocell_size.maxfar away, and stays fine over ramps, narrow passages and the ground the robot has driven over.easynav_navmap_maps_managerapplied on top.multilevel.enabled: a grid engine for outdoor terrain (RTIN over a height grid) and a hierarchy engine for buildings with floors over each other (clustering of the NavMap's own triangles).terrain.initial_navmap) or from a DEM (terrain.dem_file).Two documented example configurations are installed (
config/example_indoor.yaml,config/example_outdoor.yaml).Other files
.github/workflows/rolling.yaml: adds the package to the CI list.README.md: a row for the package.Dependencies
easynav_navmap_maps_manager,navmap_core,navmap_ros,navmap_ros_interfaces.Tests
Unit and integration tests under
test/(LOD meshing, closure, DEM grid, obstacle memory, update watchdog, real maps, among others).