Behavior trees concept for robotics in ROS - Cheat Sheet & Quick Revision

Recall & Review

beginner

What is a behavior tree in robotics?

A behavior tree is a way to organize robot actions and decisions in a tree structure. It helps robots decide what to do next by checking conditions and running tasks step-by-step.

beginner

Name the three main types of nodes in a behavior tree.

The three main types are:
1. Control nodes (like Sequence and Selector) that decide the flow.
2. Condition nodes that check if something is true.
3. Action nodes that perform tasks.

intermediate

How does a Sequence node work in a behavior tree?

A Sequence node runs its child nodes one by one. If any child fails, the sequence stops and returns failure. If all succeed, it returns success.

intermediate

What is the role of a Selector node in a behavior tree?

A Selector node tries its child nodes one by one until one succeeds. If a child succeeds, the selector returns success. If all fail, it returns failure.

advanced

Why are behavior trees preferred over simple state machines in robotics?

Behavior trees are easier to read and modify. They allow reusing parts of behavior and handle complex tasks more flexibly than state machines.

What does an Action node do in a behavior tree?

A Checks a condition

B Stops the tree execution

C Performs a task

D Controls flow between nodes

Action nodes perform specific tasks or commands for the robot.

Which node type runs children until one succeeds?

A Selector

B Decorator

C Sequence

D Condition

Selector nodes try children until one succeeds, then return success.

If a Sequence node's child fails, what happens?

A Sequence returns failure immediately

B Sequence continues to next child

C Sequence returns success

D Sequence restarts from first child

Sequence nodes stop and return failure as soon as a child fails.

Behavior trees help robots by:

A Replacing hardware components

B Storing data permanently

C Increasing battery life

D Making decisions step-by-step

Behavior trees organize robot decisions and actions in steps.

Which is NOT a benefit of behavior trees over state machines?

A Better for complex tasks

B Automatically fixes hardware errors

C Easier to read and modify

D Allows reusing behavior parts

Behavior trees do not fix hardware errors; they organize software behavior.

Explain how a behavior tree controls robot actions using its node types.

Think about how the tree decides what to do next step-by-step.

Describe the difference between Sequence and Selector nodes in behavior trees.

Focus on when each node stops running its children.

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