Populate velocities and accelerations for multidof joint trajectories (backport #3635) #3638
+96
−1
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
If I were to use
SetRobotTrajectoryMsg, to set a trajectory message, it appears that only positions are handled for multidof joints, and velocity/acceleration information is discarded.This change handles the contents of multidof joint trajectories similarly to done here and populates the velocities and accelerations in the robot states. I've also taken the liberty of adding a test to ensure that the multidof joint trajectory positions and accelerations appear as expected.
This currently doesn't support
angular/xorangular/y, for which I've added a comment noting this.As a note, I tested this on Jazzy. I currently don't have a rolling build going, but I don't think things look that different in this part of the code base anyway.
This is an automatic backport of pull request #3635 done by Mergify.