Beehave static analysis for robot behavior trees
The small branch that matters¶
Beehave reads a BehaviorTree.CPP tree (v3 or v4) or a py_trees tree and shows only the actions your robot can take, in order, with the conditions that lead to each one.
Behavior tree XML in the small branch that matters out
Three questions, one glance¶
Behavior trees grow fast. Subtrees, fallbacks, reactive sequences and decorators stack up until nobody can say what the robot does when a step fails halfway through a task, whether it flies, drives or grasps. Beehave answers:
- Which actions exist in this tree?
- What has to be true for each one to run?
- What runs next on success, and what runs next on failure?
Before and after¶
A 22-node drone mission becomes 10 actions. Control nodes become arrows, conditions become arrow labels, subtrees are inlined, retries become notes.
---
config:
theme: base
themeVariables:
edgeLabelBackground: "#f5f0e9"
lineColor: "#1b1813"
---
%% Beehave action graph: DroneMission (btcpp-v3)
flowchart TD
start(("START"))
a1["LandNow"]
a2["Arm"]
a3["TakeOff"]
a4["FlyToWaypoint<br/><small>retry ×3</small>"]
a5["CaptureImage"]
a6["FlyHome"]
a7["FindLandingSpot"]
a8["FlyToLandingSpot"]
a9["Land"]
a10["Disarm"]
success(["SUCCESS"])
failure(["FAILURE"])
start -->|"IsBatteryCritical"| a1
start -->|"not IsBatteryCritical"| a2
a1 -->|"success"| success
a1 -.->|"failure"| a2
a2 -->|"success"| a3
a2 -.->|"failure"| failure
a3 -->|"success and IsBatteryOK"| a4
a3 -->|"success and not IsBatteryOK"| a6
a3 -.->|"failure"| failure
a4 -->|"success"| a5
a4 -.->|"failure"| a6
a5 -->|"success"| a6
a5 -.->|"failure"| a6
a6 -->|"success"| a9
a6 -.->|"failure"| a7
a7 -->|"success"| a8
a7 -.->|"failure"| failure
a8 -->|"success"| a9
a8 -.->|"failure"| failure
a9 -->|"success"| a10
a9 -.->|"failure"| failure
a10 -->|"success"| success
a10 -.->|"failure"| failure
classDef start fill:#1b1813,stroke:#1b1813,stroke-width:1.5px,color:#f5f0e9
classDef action fill:#fdfbf9,stroke:#1b1813,stroke-width:1.5px,color:#1b1813
classDef success fill:#107550,stroke:#fdfbf9,stroke-width:2px,color:#fdfbf9
classDef failure fill:#b93917,stroke:#fdfbf9,stroke-width:2px,color:#fdfbf9
class start start
class a1,a2,a3,a4,a5,a6,a7,a8,a9,a10 action
class success success
class failure failure
linkStyle 0,1 stroke:#1b1813,stroke-width:1.75px
linkStyle 2,4,6,7,9,11,13,15,17,19,21 stroke:#107550,stroke-width:1.75px
linkStyle 3,5,8,10,12,14,16,18,20,22 stroke:#b93917,stroke-width:1.75px,stroke-dasharray:7 4
"What if the emergency landing fails?" takes one arrow to answer, and it shows
a gap: LandNow fails over to Arm, so the drone would start the mission
again. The same works for mobile robots and manipulators.
Where to go next¶
-
Install, run your first graph, read the output.
-
A drone mission, a mobile robot navigating with recovery, and a pick-and-place arm, each in BT.CPP v3, v4 and py_trees.
-
BehaviorTree.CPP v3 and v4,
SKIPPEDand scripts, and py_trees. -
The pipeline, the Phase 1 specification, the roadmap and every design decision.
-
BehaviorTree.CPP semantics checked against the source, prior art and the literature.
-
The metrics on public BT.CPP, Groot and Nav2 trees.
Not the Godot addon
This Beehave is a static analysis tool for robot behavior trees (BehaviorTree.CPP, py_trees, ROS 2, Nav2). It is unrelated to the Beehave behavior tree addon for the Godot game engine.