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

Always update initial robot state to prevent dirty robot state error. #448


None yet
3 participants
Copy link

commented Feb 16, 2017

The class ModelBasedPlanningContext uses the initial robot state complete_initial_robot_state_. This robot state might be dirty if transforms are not up to date, which can cause errors while planning. To prevent this the robot state needs to be updated after initialization and reset.


v4hn approved these changes Feb 16, 2017

Copy link

left a comment

@henhenhen thanks creating the pull-request :)

This is the result of a debugging session of @henhenhen and myself to get to work.
Turns out the code might work with a dirty robot state and after #188 running it prints an error.

Should be cherry-picked to j/k.

Copy link

left a comment

makes sense

@davetcoleman davetcoleman merged commit 5625917 into ros-planning:indigo-devel Mar 11, 2017

1 check passed

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

This comment has been minimized.

Copy link

commented Mar 11, 2017


@henningkayser henningkayser deleted the henningkayser:indigo-update_robot_state branch Dec 8, 2017

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.