WIP Expose an interface for passing in a function to translate joint values to grasp width #97
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.
These changes should address this comment from @mlautman
https://github.com/ros-planning/moveit_grasps/blob/f1d4fdaa7ba2e5e50e1f3841a5d699644fe790ef/src/two_finger_grasp_data.cpp#L125-L128
Making possible for the user to pass a function during the grasp data construction in the demo grasp pipeline setup
https://github.com/ros-planning/moveit_grasps/blob/f1d4fdaa7ba2e5e50e1f3841a5d699644fe790ef/src/demo/grasp_pipeline_demo.cpp#L142-L147
The original interpolation behavior is kept as a default if no function is specified.
I'm using this with a gripper of which I'm controlling the opening width through a single motorized joint providing the angle in radiants