Add tutorial on how to add a new move group capability - #295
Conversation
| ------------------------------- | ||
| `This Page <http://wiki.ros.org/pluginlib>`_ gives a detailed explanation of how to add plugins in ROS in general. The two necessary elements are base and plugin classes. The plugin class inherits from the base class and overrides its virtual functions. The main library used for this purpose is pluginlib. | ||
|
|
||
| In this section, we will show how to add a new MoveGroup capability. For demonstration purposes, we will create a capability which provide a service to query the collision objects in MoveGroup's planning scene. The final source files designed in this tutorial are available :codedir:`here <move_group_capabilities/src>`. |
There was a problem hiding this comment.
Hopefully, this's a good example, let me know if you have a better one
nbbrooks
left a comment
There was a problem hiding this comment.
Looking good, the gif is nice! My review is just lots of small stuff.
Also, could you have each sentence start on its own line in the .rst files? Makes for much better version control/review of the files. (when it is rendered, the sentences will stay in the same paragraph and it will add a space between the two sentences.)
| Creating a new MoveGroup capability | ||
| =================================== | ||
|
|
||
| In :doc:`Move Group C++ Interface </doc/examples/move_group_interface/move_group_interface_tutorial>` we saw how MoveGroup node make it easy to use MoveIt through ROS interfaces, this node have a list of `default capabilities <https://github.com/ros-planning/moveit2/blob/main/moveit_ros/move_group/default_capabilities_plugin_description.xml>`_ that provide common used action/services to interact with its internal components, sometimes we need to extend it for our own specific applications which could be done easily by creating MoveGroup capability. |
There was a problem hiding this comment.
| In :doc:`Move Group C++ Interface </doc/examples/move_group_interface/move_group_interface_tutorial>` we saw how MoveGroup node make it easy to use MoveIt through ROS interfaces, this node have a list of `default capabilities <https://github.com/ros-planning/moveit2/blob/main/moveit_ros/move_group/default_capabilities_plugin_description.xml>`_ that provide common used action/services to interact with its internal components, sometimes we need to extend it for our own specific applications which could be done easily by creating MoveGroup capability. | |
| In :doc:`Move Group C++ Interface </doc/examples/move_group_interface/move_group_interface_tutorial>` we saw how the MoveGroup node makes it easy to use MoveIt through ROS interfaces. | |
| This node has a list of `default capabilities <https://github.com/ros-planning/moveit2/blob/main/moveit_ros/move_group/default_capabilities_plugin_description.xml>`_ that provide commonly used action/services to interact with its internal components. | |
| Sometimes we need to extend it for our own specific applications which could be done easily by creating a MoveGroup capability. |
nit
|
|
||
| Creating a MoveGroup Capability | ||
| ------------------------------- | ||
| `This Page <http://wiki.ros.org/pluginlib>`_ gives a detailed explanation of how to add plugins in ROS in general. The two necessary elements are base and plugin classes. The plugin class inherits from the base class and overrides its virtual functions. The main library used for this purpose is pluginlib. |
There was a problem hiding this comment.
| `This Page <http://wiki.ros.org/pluginlib>`_ gives a detailed explanation of how to add plugins in ROS in general. The two necessary elements are base and plugin classes. The plugin class inherits from the base class and overrides its virtual functions. The main library used for this purpose is pluginlib. | |
| `This page <https://wiki.ros.org/pluginlib>`_ gives a detailed explanation of how to add plugins in ROS in general. The two necessary elements are base and plugin classes. The plugin class inherits from the base class and overrides its virtual functions. The main library used for this purpose is pluginlib. |
| ------------------------------- | ||
| `This Page <http://wiki.ros.org/pluginlib>`_ gives a detailed explanation of how to add plugins in ROS in general. The two necessary elements are base and plugin classes. The plugin class inherits from the base class and overrides its virtual functions. The main library used for this purpose is pluginlib. | ||
|
|
||
| In this section, we will show how to add a new MoveGroup capability. For demonstration purposes, we will create a capability which provide a service to query the collision objects in MoveGroup's planning scene. The final source files designed in this tutorial are available :codedir:`here <move_group_capabilities/src>`. |
There was a problem hiding this comment.
| In this section, we will show how to add a new MoveGroup capability. For demonstration purposes, we will create a capability which provide a service to query the collision objects in MoveGroup's planning scene. The final source files designed in this tutorial are available :codedir:`here <move_group_capabilities/src>`. | |
| In this section, we will show how to add a new MoveGroup capability. For demonstration purposes, we will create a capability which provides a service to query the collision objects in MoveGroup's planning scene. The final source files designed in this tutorial are available :codedir:`here <move_group_capabilities/src>`. |
| ------------------------------- | ||
| `This Page <http://wiki.ros.org/pluginlib>`_ gives a detailed explanation of how to add plugins in ROS in general. The two necessary elements are base and plugin classes. The plugin class inherits from the base class and overrides its virtual functions. The main library used for this purpose is pluginlib. | ||
|
|
||
| In this section, we will show how to add a new MoveGroup capability. For demonstration purposes, we will create a capability which provide a service to query the collision objects in MoveGroup's planning scene. The final source files designed in this tutorial are available :codedir:`here <move_group_capabilities/src>`. |
There was a problem hiding this comment.
| In this section, we will show how to add a new MoveGroup capability. For demonstration purposes, we will create a capability which provide a service to query the collision objects in MoveGroup's planning scene. The final source files designed in this tutorial are available :codedir:`here <move_group_capabilities/src>`. | |
| In this section, we will show how to add a new MoveGroup capability. For demonstration purposes, we will create a capability which provide a service to query the collision objects in MoveGroup's planning scene. The final source files designed in this tutorial are available :codedir:`here <examples/move_group_capabilities/src>`. |
I think we need to prefix this, codedir does an external link though so hard to be sure
|
|
||
| In this section, we will show how to add a new MoveGroup capability. For demonstration purposes, we will create a capability which provide a service to query the collision objects in MoveGroup's planning scene. The final source files designed in this tutorial are available :codedir:`here <move_group_capabilities/src>`. | ||
|
|
||
| First we start by creating a class GetCollisionObjects by inheriting from move_group::MoveGroupCapability, to do so we create a file named ``get_collision_objects_service_capability.cpp`` in src folder. the minimal requirement is to pass the plugin name to the base class constructor ``MoveGroupCapability``, override the ``initialize`` function, and register the class as a plugin by using ``PLUGINLIB_EXPORT_CLASS``. |
There was a problem hiding this comment.
| First we start by creating a class GetCollisionObjects by inheriting from move_group::MoveGroupCapability, to do so we create a file named ``get_collision_objects_service_capability.cpp`` in src folder. the minimal requirement is to pass the plugin name to the base class constructor ``MoveGroupCapability``, override the ``initialize`` function, and register the class as a plugin by using ``PLUGINLIB_EXPORT_CLASS``. | |
| First we start by creating a class GetCollisionObjects by inheriting from move_group::MoveGroupCapability, to do so we create a file named ``get_collision_objects_service_capability.cpp`` in src folder. | |
| The minimal requirement is to pass the plugin name to the base class constructor ``MoveGroupCapability``, override the ``initialize`` function, and register the class as a plugin by using ``PLUGINLIB_EXPORT_CLASS``. |
|
|
||
| The ``plugin_description.xml`` need to be added to the ament index to be found at runtime, in ``CMakeLists.txt`` add | ||
|
|
||
| **NOTE** Make sure to add it to the top-level ``CMakeLists.txt`` file otherwise it will not be detected bu ROS |
There was a problem hiding this comment.
I think this line and the one above it are meant to be consolidated?
|
|
||
| ros2 run moveit_ros_move_group list_move_group_capabilities | ||
|
|
||
| you should see ``move_group/GetCollisionObjectsCapability`` as a capability |
There was a problem hiding this comment.
I think it would be nice to have the expected output here. The downside is it could get out of sync if the default move group plugins change in the future.
|
|
||
| .. code-block:: bash | ||
|
|
||
| ros2 run moveit_ros_move_group list_move_group_capabilities |
There was a problem hiding this comment.
Should we instruct them to copy the examples/move_group_capabilities folder into their workspace first?
|
|
||
| Capability usage | ||
| ^^^^^^^^^^^^^^^^ | ||
| To use the capability we need first to tell move_group to use it as follow |
There was a problem hiding this comment.
| To use the capability we need first to tell move_group to use it as follow | |
| To use the capability we need first to tell move_group to use it: |
| ^^^^^^^^^^^^^^^^ | ||
| To use the capability we need first to tell move_group to use it as follow | ||
|
|
||
| .. code-block:: python |
There was a problem hiding this comment.
Is our recommendation here to add this to moveit2_tutorials move_group.launch.py? If so let's be explicit.
|
Do you think you could re-work this to be either a tutorial or a how-to guide? My hope was that new content would not be added to the examples section. |
Yes, how-to guide makes more sense for this, I'll update it later this week |
|
This pull request is in conflict. Could you fix it @JafarAbdi? |
5 similar comments
|
This pull request is in conflict. Could you fix it @JafarAbdi? |
|
This pull request is in conflict. Could you fix it @JafarAbdi? |
|
This pull request is in conflict. Could you fix it @JafarAbdi? |
|
This pull request is in conflict. Could you fix it @JafarAbdi? |
|
This pull request is in conflict. Could you fix it @JafarAbdi? |
Description
I think the intro needs some tweaking but other than that I think this's ready for a review
Checklist