Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

moveit_grasps tutorial #302

Merged
merged 12 commits into from
Apr 22, 2019
Merged

Conversation

henningkayser
Copy link
Member

@henningkayser henningkayser commented Mar 28, 2019

This will be the new tutorial for moveit_grasps.
Currently, there is only the kinetic branch so I will update all links and references once melodic (or master) branch are created.
Should I also target this PR against melodic and kinetic?
@davetcoleman I addressed you previous changes.

Also, I'm currently testing moveit_grasps and will add some instructions to the tutorial if needed.

@rhaschke
Copy link
Contributor

How does this relate to #215?

@henningkayser
Copy link
Member Author

How does this relate to #215?

Good question! @davetcoleman do you think the previous PR should be continued rather than making a new one?

Copy link
Contributor

@rhaschke rhaschke left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Good initial text.


...

Within that file you will find all of the gripper specific parameters necessary for customizing MoveIt Grasps with any suction or finger gripper.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

From looking at the parameter file, the meaning of all those parameters doesn't yet become clear.
I guess the code is limited to parallel-jaw grippers, right? Why, for example, is it required to define the finger width?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I added further parameter description to the example config moveit/moveit_grasps#36. I agree that some of the parameters seem a bit confusing at first but I think the comments should clarify all of them.

@mlautman
Copy link
Contributor

@henningkayser I have made some additional changes that I have pushed to the picknikrobotics moveit-tutorials fork. Please consider cherry picking them on top of your branch.

https://github.com/PickNikRobotics/moveit_tutorials/commits/melodic-mike-moveit-grasps

My changes are in the two most recent commits

@henningkayser
Copy link
Member Author

@mlautman Looks good! You could have pushed them here directly as well. Shouldn't we copy the remaining images into this repo?

@henningkayser henningkayser changed the title WIP: moveit_grasps tutorial moveit_grasps tutorial Apr 12, 2019
@henningkayser
Copy link
Member Author

How does this relate to #215?

@rhaschke actually this was a duplicate since I wasn't aware that there was already an existing PR for moveit_grasps. Also the other PR was abandoned and incomplete so I would vote for merging this one and closing the other.


In order to run the full grasp pipeline the three components need to be applied in sequence.

An example for generating, filtering and planning grasp motions can be found inside the file `src/grasp_pipeline_demo.cpp <https://github.com/ros-planning/moveit_grasps/blob/kinetic-devel/src/demo/grasp_pipeline_demo.cpp>`_. The grasp pipeline demo can be run by launching `launch/grasp_pipeline_demo.launch <https://github.com/ros-planning/moveit_grasps/blob/kinetic-devel/launch/grasp_pipeline_demo.launch>`_.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

nit: these should point to the melodic-devel or a master branch

@mlautman mlautman merged commit 21ac925 into moveit:master Apr 22, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants