fix: ensure attached objects update during motion execution#3327
Merged
sjahr merged 10 commits intomoveit:mainfrom Apr 3, 2025
Merged
Conversation
- Check that attached objects in the monitored robot match those in the planned trajectory. - If an object disappears from the monitored robot, remove it from the trajectory waypoint robot_state. - If an object is attached to the monitored robot but missing in the trajectory, add it to enable meaningful collision checking.
sea-bass
reviewed
Feb 6, 2025
sea-bass
reviewed
Feb 6, 2025
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## main #3327 +/- ##
==========================================
+ Coverage 45.87% 46.22% +0.36%
==========================================
Files 717 717
Lines 62592 62648 +56
Branches 7570 7581 +11
==========================================
+ Hits 28708 28953 +245
+ Misses 33718 33528 -190
- Partials 166 167 +1 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
style: `sample_attached_object` -> `sample_attached_objects`
…queried based on their consistency in the planned trajectory. --- Before entering the monitoring phase, it checks whether the attached objects remain consistent throughout the trajectory. If they do, they are stored and later used by the isRemainingPathValid method without needing to be queried again. If the attached objects change during the planned trajectory, the map is left empty, signaling isRemainingPathValid to query them at each waypoint.
sea-bass
reviewed
Feb 12, 2025
Contributor
sea-bass
left a comment
There was a problem hiding this comment.
Mostly looks good to me, with some minor comments!
Also tagged a few other maintainers for a second look.
Contributor
Author
|
Hey all, just checking in on this PR. It’s been open for a bit—let me know if I need to update anything to move it forward. |
sjahr
approved these changes
Apr 3, 2025
mergify bot
pushed a commit
that referenced
this pull request
Apr 3, 2025
(cherry picked from commit 89acadd) # Conflicts: # moveit_core/robot_state/include/moveit/robot_state/robot_state.hpp # moveit_ros/planning/plan_execution/include/moveit/plan_execution/plan_execution.hpp # moveit_ros/planning/plan_execution/src/plan_execution.cpp
mergify bot
pushed a commit
that referenced
this pull request
Apr 3, 2025
(cherry picked from commit 89acadd)
sea-bass
pushed a commit
that referenced
this pull request
Apr 4, 2025
sussybot5258
pushed a commit
to GreyCatAI/moveit2
that referenced
this pull request
Apr 19, 2025
This was referenced May 12, 2025
Markus-Simonsen
pushed a commit
to Markus-Simonsen/moveit2
that referenced
this pull request
Aug 12, 2025
helen9975
pushed a commit
to personalrobotics/moveit2
that referenced
this pull request
Feb 17, 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.
Description
Implications
This could impact a few different situations: