Use Pro-RRT directly under MoveToJointState
and MoveToWaypoint
#63
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.
Refactors the base
MoveToJointState
andMoveToWaypoint
to:MoveToWaypoint
useMoveToJointState
internally.This PR effectively makes Pro-RRT the default in all configs everywhere where
MoveToJointState
orMoveToWaypoint
is called (e.g. move to waypoint shortcuts, etc.)This should save planning time, improve determinism, reduce number of layers to maintain and give more flexibility to the user, since now we directly expose ports for:
It also lets us get rid of the 'RetryUntilSuccessful' decorators in planning Objectives, since the plans are now deterministic.
I manually tested all the configs this PR is touching to make sure they still work.
Here's an example of planning around a keep-out zone with a tool 'keep upright' constraint:
RRT.Constraints.webm
MTC stages doing joint-space planning still not updated to use Pro-RRT by default (https://github.com/PickNikRobotics/moveit_studio/issues/9810).
Requires https://github.com/PickNikRobotics/moveit_studio/pull/9924
Closes https://github.com/PickNikRobotics/moveit_studio/issues/9701