Support keep out zone and speed filters - #46
Merged
Conversation
…te params with post_ and update binary_filter_switch to use the param function rather than subprocess
* replace wall timer with ros2 approximate time synchronizer and warn when lidars go stale * tighten the bound for floor finding so it doesnt latch to floor away from the robot base
Contributor
hello-robot-shehab
approved these changes
Aug 20, 2026
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.


This PR
to test
and visually check that the robot doesnt go to the keepout zones even if its shorter to pass through it. and you should see a change in speed when it enters the speed costmaps.
for the binary filter
Start the filter node:
ros2 launch stretch_nav2 binary_filter_launch.pyLaunch navigation with the filter configuration:
ros2 launch stretch_nav2 navigation_mppi_binary_filter.launch.py