Fix: Nav objectives discard click-time pose stamps#763
Merged
Conversation
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (2)
📝 WalkthroughSummary by CodeRabbit
WalkthroughTwo behavior tree XML objective files were modified to change timestamp handling in navigation actions. The ChangesNavigation XML Timestamp Configuration
Possibly related issues
Suggested reviewers: 🚥 Pre-merge checks | ✅ 4✅ Passed checks (4 passed)
Comment |
|
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.
[written by AI]
needs: moveit_pro/#20320
Problem
Navigate to Clicked Point(and its replanning variant) zero the goal pose's timestamp before sending it to Nav2:ComputePathToPoseActionis invoked withignore_stamp_time="true"andNavigateToPoseActionrelies on the same port'struedefault. A zero stamp means "resolve with the latest transform", so a goal clicked in a moving frame (e.g.base_linkwith the fixed-frame selector from moveit_pro#20259) re-anchors to wherever the robot is at lookup time instead of where it was when the user clicked.moveit_pro#20320 makes the backend stamp
GetPoseFromUserresponses with receipt time — but that stamp is discarded as long as these objectives zero it again.Approach
Set
ignore_stamp_time="false"on both nav actions so the receipt-time stamp survives to Nav2, which resolves the goal's frame as of the click. Safe with or without moveit_pro#20320: before it, the stamp is zero anyway (identical behavior); after it, the stamp is fresh (tens of ms old) so no transform-tolerance risk.The
needs:token stacks this PR's integration tests on moveit_pro#20320's image so the combined behavior is what CI exercises.