PropertyMap implementation #9
Closed
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
replacing scalar graspOffset and hard-coded Euler angles with arbitrary graspFrame
rhaschke
force-pushed
the
wip-properties
branch
2 times, most recently
from
2afadbf to
7b0bf2e
Compare
rhaschke
force-pushed
the
wip-properties
branch
from
a14eccf to
0faeb42
Compare
|
I have some more additions to this. Closing for now, will reopen later. |
sjahr
added a commit
to henningkayser/moveit_task_constructor
that referenced
this pull request
Oct 18, 2023
Merge upstream ros2
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.
I implemented the
PropertyMapwe discussed a while ago.Using this
PropertyMapI also generalized the grasp frame specification forGenerateGraspPose- getting rid of hard-coded YPR angles. This allows for our PA10 example to be included easily.