-
Notifications
You must be signed in to change notification settings - Fork 23
Description
Hello! The README.md lists "integration into elevation_mapping_cupy" as a feature, but there seems to be no further information about what this means.
I can see that wild_visual_navigation_ros/launch/elevation_mapping_cupy.launch references wild_visual_navigation_ros/config/elevation_mapping_cupy/wvn_sensor_parameter.yaml, where the visual_traversability channels are passed into elevation_mapping_cupy. Is that basically it?
Is the integration unidirectional, i.e. from wild_visual_navigation to elevation_mapping_cupy only, or does something also happen in the opposite direction?
What effects or benefits do the added visual_traversability channels bring to elevation_mapping_cupy? Do they improve its traversability predictions, elevation map, plane segmentation etc., or something else? Or is it more of a way to sort of unify and consolidate the visual traversability predictions by combining them with elevation_mapping_cupy's more geometry-based ones? What is the thinking and motivation behind this integration, and am I missing any other aspects of how the two packages are supposed to work together?
It could be helpful to add some more details about this to the README.md. Thanks!