You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: doc/examples/perception_pipeline/perception_pipeline_tutorial.rst
+47-11Lines changed: 47 additions & 11 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -34,7 +34,7 @@ To use the Occupancy Map Updater, it is only necessary to set the appropriate pa
34
34
YAML Configuration file (Point Cloud)
35
35
+++++++++++++++++++++++++++++++++++++
36
36
37
-
We will have to generate a YAML configuration file for configuring the 3D sensors. Please see :panda_codedir:`this example file <config/sensors_3d.yaml>` for processing point clouds.
37
+
We will have to generate a YAML configuration file for configuring the 3D sensors. Please see :moveit_resources_codedir:`this example file <panda_moveit_config/config/sensors_3d.yaml>` for processing point clouds.
38
38
39
39
Save this file in the config folder in the robot's moveit_config package with name "sensors_3d.yaml": ::
40
40
@@ -50,6 +50,20 @@ Save this file in the config folder in the robot's moveit_config package with na
@@ -75,7 +89,7 @@ Save this file in the config folder in the robot's moveit_config package with na
75
89
YAML Configuration file (Depth Map)
76
90
+++++++++++++++++++++++++++++++++++
77
91
78
-
We will have to generate a YAML configuration file for configuring the 3D sensors. An :panda_codedir:`example file for processing depth images <config/sensors_3d.yaml>` can be found in the panda_moveit_config repository as well.
92
+
We will have to generate a YAML configuration file for configuring the 3D sensors. An :moveit_resources_codedir:`example file for processing depth images <panda_moveit_config/config/sensors_3d.yaml>` can be found in the panda_moveit_config repository as well.
79
93
Save this file in the config folder in the robot's moveit_config package with name "sensors_3d.yaml": ::
80
94
81
95
sensors:
@@ -125,21 +139,43 @@ Update the launch file
125
139
126
140
Add the YAML file to the launch script
127
141
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
128
-
You will now need to create a *sensor_manager.launch* file in the "launch" directory of your panda_moveit_config directory (e.g. `on github <https://github.com/ros-planning/panda_moveit_config/blob/rolling-devel/launch/sensor_manager.launch.xml>`_) with this sensor information. You will need to add the following line into that file to configure the set of sensor sources for MoveIt to use: ::
You will now need to create a *sensor_manager.launch* file in the "launch" directory of your ``panda_moveit_config`` directory with this sensor information, which is already done for you for convenience under :moveit_resources_codedir:`moveit_resources/panda_moveit_config <panda_moveit_config/config/sensor_manager.launch.xml>`.
143
+
144
+
You will need ``sensors_3d.yaml`` to be read by your application. :moveit_resources_codedir:`In panda_moveit_config/launch/demo.launch.py <panda_moveit_config/launch/demo.launch.py>` the file is already read like the following (It's convoluted, you should use ``demo.launch.py`` from ``moveit_resources`` repo unless you know what this piece of code does.): ::
145
+
146
+
from moveit_configs_utils import MoveItConfigsBuilder
You will also need to configure the `Octomap <http://octomap.github.io/>`_. :moveit_resources_codedir:`In the pre-made example (panda_moveit_config/launch/demo.launch.py) <panda_moveit_config/launch/demo.launch.py>` the following does the job: ::
MoveIt uses an octree-based framework to represent the world around it. The *Octomap* parameters above are configuration parameters for this representation:
144
180
* *octomap_frame*: specifies the coordinate frame in which this representation will be stored. If you are working with a mobile robot, this frame should be a fixed frame in the world.
145
181
* *octomap_resolution*: specifies the resolution at which this representation is maintained (in meters).
0 commit comments