Added message fields for setting the maximum cartesian end effector for cartesian paths #113
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
speed of the computed path.
6 tasks
v4hn
reviewed
May 19, 2021
…is not using the planning pipeline.
|
Hi @v4hn, do you mind checking this again and potentially merging this? Thanks |
v4hn
approved these changes
Jun 26, 2021
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
See ros_planning/moveit#2674 for more details.
These additional fields are needed to pass these values from the move_group_interface to a planning adapter, that recomputes the time parameterization of the trajectory to match the given Cartesian speed for the function
computeCartesianPath