navigation2
navigation2 copied to clipboard
ros-navigation
[Input requested] Topological operation costmap layers
Hi,
I figured I'd ask and see if there was interest in something like this. In order to help remove salt and pepper noise from images, typically you might use dilation and erosion. The same concept could apply to navigation2 costmap layers, where an erroneous voxel layer or obstacle layer measurement (or static layer with SLAM session and things moving around) would make in the middle of free space incorrectly.
The idea would be to then offer some convolution or topological costmap layer to remove this noise. Is this something folks think is useful and would use?
To get rid of noise, erode then dilate https://opencv-python-tutroals.readthedocs.io/en/latest/py_tutorials/py_imgproc/py_morphological_ops/py_morphological_ops.html
This is an actual use case in a real life application I developed, especially for adjusting traversability calculations for different robots with different needs. Is this in the same light as the grip_map package's filters? Because eventually that is what we moved to.
I don't see this particular filter in the filter's package, but its in the same theme. Topological operations are typically used to remove salt and pepper noise from images so it could be good here to remove random single extraneous measurements.
It's also our intent to move to grid_maps, we'd certainly be happy to have you help with that :-)
We should be able to use the MathExpressionFilter to that extent, I think. Maybe a similar concept for costmap2D would be useful (or not, if nav2 is porting to grid_map 🤷). I remember there was such a porting task (I'll try to help if I can😬), but I couldn't find the corresponding issue to link here.
Its been ported to ROS2 but we haven't started the design effort in replacing costmap with it yet. That's under the environmental modelling ticket.
Hi @SteveMacenski , I would like to focus my efforts these weeks on helping to port nav2 to grid_map. I am starting now to do some tests with the grid_map library.
It might be good to start gathering thoughts into a design doc (but a little off topic for this particular ticket :-) )
where to follow up the ticket/discussion related to replacing costmap_2d with grid_map ?, I am interested in this with a potential to take a part in the effort of porting.
