-
Notifications
You must be signed in to change notification settings - Fork 158
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Make mtc execute solution capability apply scene diffs #467
Make mtc execute solution capability apply scene diffs #467
Conversation
/* RCLCPP_DEBUG_STREAM(LOGGER, "apply effect of " << description); */ | ||
scene_diff.robot_state.joint_state = sensor_msgs::msg::JointState(); | ||
scene_diff.robot_state.multi_dof_joint_state = sensor_msgs::msg::MultiDOFJointState(); | ||
if (!context_->planning_scene_monitor_->newPlanningSceneMessage(scene_diff)) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
…ng trajectory Don't override joint state in planning scene monitor when executing task's solution - Fix: moveit#353 Refactor creating an executable trajectory in a helper lambda Make mtc execute solution capability apply scene diffs before executing trajectory Fix compiler issues Clang-tidy fixes Copy planning scene to modify it
5e83f72
to
c580584
Compare
Codecov ReportPatch and project coverage have no change.
Additional details and impacted files@@ Coverage Diff @@
## ros2 #467 +/- ##
=======================================
Coverage 41.80% 41.80%
=======================================
Files 78 78
Lines 7846 7846
=======================================
Hits 3279 3279
Misses 4567 4567 ☔ View full report in Codecov by Sentry. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The changes are rather large and I don't see immediately what was actually changed.
Please add some more details to the main comment of this PR describing the actual problem and your solution for it.
Given my feedback here, I would have expected a much simpler solution, namely removing the corresponding RobotState members. |
Closed in favor of #498 |
This PR contains a fix for #353 by @JafarAbdi that we've been using on a fork for quite some time but never got contributed upstream. With his consent, I opened this PR to bring it upstream