Enforce joint position limits on internal joint state before making trajectory #13
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
This switchs the order that
composeJointTrajMessage
andenforcePositionLimits
is called so thatenforcePositionLimits
works on a JointState and uses internal_joint_state_ which holds position and velocity information regardless of what should be published. Previously: it was operating on the JointTrajectory and had to take publishing booleans into considerationTested locally, including being able to back away from joint position limit. Shameless plug for new Servo tutorial which includes using a keyboard as input (how I tested the joint limits)