Skip to content

Commit da7175e

Browse files
committed
Minor fixes
Signed-off-by: Alberto Tudela <ajtudela@gmail.com>
1 parent 61be30b commit da7175e

2 files changed

Lines changed: 7 additions & 6 deletions

File tree

migration/Jazzy.rst

Lines changed: 2 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -432,5 +432,6 @@ During the ``goalCompleted`` callback, it fetches the ``waypoint_statuses`` inst
432432

433433
Groot 2 Support
434434
***************
435+
In `PR #5065 <https://github.com/ros-navigation/navigation2/pull/5065>`_ , BT navigators: ``navigate_to_pose`` and ``navigate_through_poses`` now support live monitoring and visualization of the behavior tree using Groot 2. JSON conversions are also available to see the content of the Blackboard, allowing the introspection of the BT nodes. Switching bt-xmls on the fly through a new goal request is also included.
435436

436-
BT navigators: ``navigate_to_pose`` and ``navigate_through_poses`` now support live monitoring and visualization of the behavior tree using Groot 2. JSON conversions are also available to see the content of the Blackboard, allowing the introspection of the BT nodes. Switching bt-xmls on the fly through a new goal request is also included. Because live monitoring of Behavior Tree with more than 20 nodes and visualizing the content of the blackboard is a PRO (paid) feature of Groot 2. This feature is disabled by default.
437+
Because live monitoring of Behavior Tree with more than 20 nodes and visualizing the content of the blackboard is a PRO (paid) feature of Groot 2. This feature is disabled by default.

plugin_tutorials/docs/writing_new_bt_plugin.rst

Lines changed: 5 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -241,9 +241,9 @@ Select this BT XML file in your specific navigation request in ``NavigateToPose`
241241
Using custom types for Input/Output ports
242242
=========================================
243243

244-
In addition to standard types, custom types such as those from `nav2_msgs` or `geometry_msgs` can also be used for input/output ports.
244+
In addition to standard types, custom types such as those from ``nav2_msgs`` or ``geometry_msgs`` can also be used for input/output ports.
245245

246-
For example, you can define custom types for ports in the `providedPorts` function as follows:
246+
For example, you can define custom types for ports in the ``providedPorts`` function as follows:
247247

248248
.. code-block:: cpp
249249
@@ -256,7 +256,7 @@ For example, you can define custom types for ports in the `providedPorts` functi
256256
257257
To use custom types for input/output ports in the behavior tree XML, it is necessary to convert them from a string. This is because ports in the XML are represented as strings and must be transformed into the corresponding data type in the code.
258258

259-
For example, if you have a custom type `geometry_msgs::msg::Point`, you can perform the conversion as follows:
259+
For example, if you have a custom type ``geometry_msgs::msg::Point``, you can perform the conversion as follows:
260260

261261
.. code-block:: cpp
262262
@@ -279,7 +279,7 @@ For example, if you have a custom type `geometry_msgs::msg::Point`, you can perf
279279
}
280280
} // namespace BT
281281
282-
For more information on custom type conversion, you can refer to the `bt_utils.hpp <https://github.com/ros-navigation/navigation2/blob/main/nav2_behavior_tree/include/nav2_behavior_tree/bt_utils.hpp>`_ or the BT.CPP documentation : `Parsing a string <https://www.behaviortree.dev/docs/tutorial-basics/tutorial_03_generic_ports#parsing-a-string>`_
282+
For more information on custom type conversion, you can refer to the `bt_utils.hpp <https://github.com/ros-navigation/navigation2/blob/main/nav2_behavior_tree/include/nav2_behavior_tree/bt_utils.hpp>`_ or the BT.CPP documentation: `Parsing a string <https://www.behaviortree.dev/docs/tutorial-basics/tutorial_03_generic_ports#parsing-a-string>`_.
283283

284284
Visualize the content of the blackboard in Groot 2 (PRO)
285285
========================================================
@@ -312,7 +312,7 @@ After defining the conversion, you need to register the custom type in the `prov
312312
});
313313
}
314314
315-
For more information on custom type conversion, you can refer to the `json_utils.hpp <https://github.com/ros-navigation/navigation2/blob/main/nav2_behavior_tree/include/nav2_behavior_tree/json_utils.hpp>`_ or the BT.CPP documentation : `Visualize custom types in the Blackboard <https://www.behaviortree.dev/docs/tutorial-basics/tutorial_11_groot2/#visualize-custom-types-in-the-blackboard>`_
315+
For more information on custom type conversion, you can refer to the `json_utils.hpp <https://github.com/ros-navigation/navigation2/blob/main/nav2_behavior_tree/include/nav2_behavior_tree/json_utils.hpp>`_ or the BT.CPP documentation: `Visualize custom types in the Blackboard <https://www.behaviortree.dev/docs/tutorial-basics/tutorial_11_groot2/#visualize-custom-types-in-the-blackboard>`_
316316

317317
.. note::
318318

0 commit comments

Comments
 (0)