ROS Resources: Documentation | Support | Discussion Forum | Index | Service Status | ros @ Robotics Stack Exchange |
1 | initial version |
Unsure if dynamically changing filters is how you are supposed to go about it. Feels more like you are supposed to deal with dynamic objects via costmap changes, and doing keepout zones for areas you know ahead of time that you should avoid. You can make a custom costmap layer based on sensor data, other maps or anything else you deem useful. Tutorial here.
However, if you necessarily must do it your way, add a hook in the costmap filter interface for dynamically changing the parameters you need changed, add the equivalent response in existing costmaps (so as to not break them), implement your functionality, and you're done.