fix nav_to_pose planning every iteration#6029
Merged
SteveMacenski merged 1 commit intoros-navigation:mainfrom Mar 16, 2026
Merged
fix nav_to_pose planning every iteration#6029SteveMacenski merged 1 commit intoros-navigation:mainfrom
SteveMacenski merged 1 commit intoros-navigation:mainfrom
Conversation
PR ros-navigation#5876 added `IsGoalNearby` condition to the sequence. However, when to goal is far, this action is Always Failure => always trigger the Fallback and planning Changed logic to replan if: - path is invalid - always - goal updated - always - IsGoalNearby AND timer expired Signed-off-by: Adi Vardi <adi.vardi@enway.ai>
859505c to
b622578
Compare
Member
SteveMacenski
left a comment
There was a problem hiding this comment.
@mini-1235 can you review, since this was your recent project?
mini-1235
approved these changes
Mar 16, 2026
Collaborator
mini-1235
left a comment
There was a problem hiding this comment.
Thanks for catching this! I think I misunderstood the original intent of this Behavior Tree in the previous PR
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.
Basic Info
Description of contribution in a few bullet points
PR #5876 added
IsGoalNearbycondition to the sequence. However, when to goal is far, this action is Always Failure => always trigger the Fallback and planningChanged logic to replan if:
Description of documentation updates required from your changes
none
Description of how this change was tested
Test in simulation.
Without this fix, the BT replans every tick of the RateController while the goal is far away.
With the fix, it should not only replan iff the conditions above are verified
Future work that may be required in bullet points
I am not using any of the other demo BTs, so I didn't check if any modifications to them are needed
For Maintainers:
backport-*.