Behavior trees concept for robotics in ROS - Step-by-Step Execution

Concept Flow - Behavior trees concept for robotics

Start Behavior Tree

↓

Select Root Node

↓

Evaluate Node Type

↓

Sequence

↓

Run Children

↓

Child Success?

↓

Next Child

↓

Return Result

↓

End

The behavior tree starts at the root, evaluates node types (Sequence or Fallback), runs children nodes in order, and returns success or failure based on children outcomes.

Execution Sample

ROS

sequence_node = Sequence(children=[task1, task2])
result = sequence_node.tick()
print(result)

This code runs a sequence node that ticks its children tasks in order and prints the overall success or failure.

Execution Table

Step	Node Evaluated	Child Index	Child Result	Sequence Action	Overall Result
1	Sequence Root	0	Success	Proceed to next child	Running
2	Sequence Root	1	Failure	Stop sequence, return failure	Failure
3	Sequence Root	-	-	-	Stop: Child 1 failed, sequence fails

💡 Sequence node stops when a child fails; overall result is failure.

Variable Tracker

Variable	Start	After Step 1	After Step 2	Final
child_index	0	1	-	1
child_result	-	Success	Failure	Failure
sequence_status	Running	Running	Failure	Failure

Key Moments - 2 Insights

Why does the sequence node stop after the second child fails?

Because in the execution_table at Step 2, the child result is Failure, so the sequence node stops and returns Failure immediately.

What happens if the first child fails in a sequence node?

The sequence node stops immediately and returns Failure, no further children are ticked, as shown by the early stop in the execution_table.

Visual Quiz - 3 Questions

Look at the execution_table, what is the child_index after Step 1?

A 1

B 0

C 2

D -

💡 Hint

Check the 'child_index' column in variable_tracker after Step 1.

At which step does the sequence node return failure?

A Step 1

B Step 3

C Step 2

D Never

💡 Hint

Look at the 'Overall Result' column in execution_table for when failure is returned.

If the first child returned failure, how would the execution_table change?

A Sequence continues to Step 2

B Sequence stops at Step 1 with failure

C Sequence returns success

D Sequence ignores child results

💡 Hint

Sequence nodes stop immediately on first failure, see key_moments explanation.

Concept Snapshot

Behavior Trees control robot actions by evaluating nodes in a tree.
Sequence nodes run children in order and fail on first failure.
Fallback nodes try children until one succeeds.
Each node returns Success, Failure, or Running.
This structure helps robots decide what to do step-by-step.

Full Transcript

Behavior trees in robotics start at a root node and evaluate child nodes based on their type. Sequence nodes run each child in order and stop if any child fails, returning failure. Fallback nodes try children until one succeeds. This step-by-step evaluation helps robots make decisions clearly and predictably. The example shows a sequence node ticking two children: the first succeeds, the second fails, so the sequence returns failure and stops. Variables like child index and sequence status update as the tree runs. Understanding when nodes stop or continue is key to using behavior trees effectively.

Practice

1. What is the main purpose of a behavior tree in robotics?

easy

A. To create 3D models of the robot environment

B. To store large amounts of sensor data

C. To replace the robot's hardware components

D. To organize robot tasks step-by-step for clear control flow

Solution

1. Step 1: Understand behavior tree role

   Behavior trees help organize robot actions in a clear, step-by-step way.

2. Step 2: Compare options

   Only To organize robot tasks step-by-step for clear control flow describes organizing tasks; others describe unrelated functions.

3. Final Answer:

   To organize robot tasks step-by-step for clear control flow -> Option D

4. Quick Check:

   Behavior trees = organize tasks [OK]

Hint: Behavior trees control robot actions stepwise [OK]

Common Mistakes:

• Confusing behavior trees with data storage
• Thinking behavior trees modify hardware
• Mixing behavior trees with 3D modeling

2. Which of the following is the correct way to define a Sequence node in a ROS behavior tree XML?

easy

A. ...

B. ...

C. ...

D. ...

Solution

1. Step 1: Identify node types in behavior tree XML

   Sequence nodes are defined with the tag <Sequence> in ROS behavior trees.

2. Step 2: Match option tags

   Only <Sequence name="root"> ... </Sequence> uses <Sequence> correctly; others use different node types.

3. Final Answer:

   <Sequence name="root"> ... </Sequence> -> Option A

4. Quick Check:

   Sequence node tag = <Sequence> [OK]

Hint: Sequence nodes use <Sequence> tags in XML [OK]

Common Mistakes:

• Using Fallback tag for Sequence node
• Confusing Action or Decorator tags with Sequence
• Missing proper XML syntax

3. Given this behavior tree snippet in ROS:

<Sequence name="root">
  <Action name="CheckBattery" />
  <Fallback name="TryCharging">
    <Action name="FindCharger" />
    <Action name="ChargeBattery" />
  </Fallback>
</Sequence>

What happens if CheckBattery fails?

medium

A. The robot skips charging and continues other tasks

B. The Fallback node TryCharging runs to try charging

C. The tree stops and returns failure immediately

D. The tree restarts from the beginning

Solution

1. Step 1: Understand Sequence node behavior

   Sequence nodes stop and return failure if any child fails.

2. Step 2: Analyze failure of CheckBattery

   Since CheckBattery is first child and it fails, Sequence stops immediately without running Fallback.

3. Final Answer:

   The tree stops and returns failure immediately -> Option C

4. Quick Check:

   Sequence fails on first child failure [OK]

Hint: Sequence stops on first failure child [OK]

Common Mistakes:

• Thinking Fallback runs after Sequence child fails
• Assuming robot continues tasks after failure
• Believing tree restarts automatically

4. You wrote this behavior tree XML but the robot never tries to charge the battery:

<Sequence name="root">
  <Fallback name="TryCharging">
    <Action name="FindCharger" />
    <Action name="ChargeBattery" />
  </Fallback>
  <Action name="CheckBattery" />
</Sequence>

What is the likely error?

medium

A. Fallback nodes cannot be inside Sequence nodes

B. CheckBattery is after TryCharging, so charging never triggers on low battery

C. Action nodes must have child nodes

D. Sequence nodes always run children in reverse order

Solution

1. Step 1: Review node order in Sequence

   Sequence runs children in order; TryCharging runs before CheckBattery.

2. Step 2: Understand logic error

   Charging tries before checking battery status, so it never triggers when needed.

3. Final Answer:

   CheckBattery is after TryCharging, so charging never triggers on low battery -> Option B

4. Quick Check:

   Order matters: check battery first [OK]

Hint: Check battery before charging in Sequence [OK]

Common Mistakes:

• Thinking Fallback can't be inside Sequence
• Believing Action nodes need children
• Assuming Sequence runs children backwards

5. You want a robot to try multiple ways to open a door: first try UseKey, then PushDoor, and finally CallForHelp. Which behavior tree structure best models this?

hard

A.

B.

C.

D.

Solution

1. Step 1: Understand Fallback node behavior

   Fallback tries children in order until one succeeds, perfect for trying multiple options.

2. Step 2: Compare node types

   Sequence requires all children to succeed; Decorator modifies one child; Parallel runs all simultaneously.

3. Final Answer:

   Fallback node with UseKey, PushDoor, CallForHelp actions -> Option A

4. Quick Check:

   Try options in order = Fallback [OK]

Hint: Use Fallback to try alternatives in order [OK]

Common Mistakes:

• Using Sequence which requires all actions to succeed
• Confusing Decorator with control flow node
• Using Parallel which runs all actions at once