Skip to content

Commit 67f42af

Browse files
committed
Clarify on not cancelling executor in MTC tutorial (#1105)
1 parent b0ba2a9 commit 67f42af

1 file changed

Lines changed: 4 additions & 1 deletion

File tree

doc/tutorials/pick_and_place_with_moveit_task_constructor/pick_and_place_with_moveit_task_constructor.rst

Lines changed: 4 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -487,7 +487,10 @@ We return the task and finish with the ``createTask()`` function.
487487
return task;
488488
}
489489

490-
Finally, we have ``main``: the following lines create a node using the class defined above, and calls the class methods to set up and execute a basic MTC task. In this example, we do not cancel the executor once the task has finished executing to keep the node alive to inspect the solutions in RViz.
490+
Finally, we have ``main``: the following lines create a node using the class defined above, and calls the class methods to set up and execute a basic MTC task.
491+
In this example, we do not cancel the executor once the task has finished executing to keep the program running to inspect the solutions in RViz.
492+
Note that it's the internal executor and node inside ``task_.introspection()`` that responds to RViz's introspect request when you click on the solutions in Task Tree, in RViz.
493+
The sole purpose of not cancelling the executor is simply, not letting the program to quit until you CTRL-C on it.
491494

492495
.. code-block:: c++
493496

0 commit comments

Comments
 (0)