How fzi-forschungszentrum-informatik/ros2_ros_bt_py works
Project Type and Purpose
• This is a ROS2-based Behavior Tree library designed to serve as an alternative to other BT tools (like BehaviorTree.cpp, SMACH, FlexBE).
• Its purpose is to provide a plug‐and‐play framework for mission control and task orchestration in robotics, leveraging ROS actions, services, and a configurable node system. It even includes a ReactJS-based web GUI to build and edit behavior trees without coding.
File Structure
• The top-level file tree indicates a multi-package project:
– The "ros_bt_py" directory contains the core library.
– "ros_bt_py_interfaces" defines ROS messages, services, and actions that support the communication needs of the core library.
– "ros_bt_py_web_gui" provides the standalone graphical web interface.
• Inside the core library (ros_bt_py/ros_bt_py) you see modules like node.py, node_config.py, various helper modules, and a directory of nodes (both generic and ROS-specific in the "nodes" and "ros_nodes" folders) that together form the building blocks of the behavior tree framework.
• Additional directories like "launch", "doc", "tests", and configuration files (package.xml, setup.py/pyproject.toml) help build, document, and verify the system.
• Continuous integration configurations (GitHub workflows, GitLab CI) and a manifest (LICENSE, CONTRIBUTING) indicate the project is built with modern software best practices.
Specific Elements
• ROS Communications Layer (with nodes for actions, services, messages, and parameters, pointing out ros_bt_py_interfaces).
• Web Interface (showing the web server, web socket/rosbridge connection, and the front-end application).
• The flow from the Web GUI launch (at ros_bt_py_web_gui) to initiating a Behavior Tree execution (ros_bt_py).
• Service and topic interactions defined by ros_bt_py_interfaces which are used by the core library.
• Configuration inputs from launch files and YAML configuration (from the launch and config directories) that modify behavior at runtime.
• Annotations on architectural patterns such as modularity, plug-in extensibility, and clear separation between behavior logic and I/O.
Final Steps
• Which component handles the behavior tree logic.
• How the system interfaces with ROS.
• How the user interacts with the system via the web GUI.