Skip to content
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

World::moveObject(): only apply changes if there is any non-zero motion #1108

merged 2 commits into from Oct 25, 2018


None yet
3 participants
Copy link

commented Oct 21, 2018

This is a follow up to #957, which introduced World::moveObject().
When transform is the identity matrix, i.e. there is no movement, the object shouldn't be touched.
This follows the rule, only to create a copy of the parent planning scene, when there are actual modifications.

  • Cherry pick to Kinetic

@davetcoleman davetcoleman requested a review from mlautman Oct 23, 2018

Copy link

left a comment

Why return false? Shouldn't it return true because the object is at the desired location?


This comment has been minimized.

Copy link
Collaborator Author

commented Oct 25, 2018

@mlautman Well, my thinking was "no motion -> return false". However, another (probably more appropriate) thinking is "object not found -> return false". Changed.

@rhaschke rhaschke merged commit 1daa1d1 into ros-planning:melodic-devel Oct 25, 2018

1 check passed

continuous-integration/travis-ci/pr The Travis CI build passed

rhaschke added a commit that referenced this pull request Oct 25, 2018

@rhaschke rhaschke deleted the ubi-agni:fix-moveObject branch Oct 27, 2018

ggupta9777 added a commit to ggupta9777/moveit that referenced this pull request Mar 17, 2019

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.