Behavior trees concept for robotics in ROS - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to define a simple behavior tree node in ROS.

ROS

auto node = BT::NodeBuilder().name("[1]Node").build();

Drag options to blanks, or click blank then click option'

ATurn

BStop

CWait

DMove

Attempts:

3 left

💡 Hint

Common Mistakes

Using a generic or unrelated name for the node.

The node name should describe the action, here 'Move' fits a common robot behavior.

2fill in blank

medium

Complete the code to add a Sequence node to the behavior tree.

ROS

auto sequence = tree.root()->addChild(BT::[1]Node::create("Sequence"));

Drag options to blanks, or click blank then click option'

ASequence

BDecorator

CFallback

DAction

Attempts:

3 left

💡 Hint

Common Mistakes

Confusing Sequence with Fallback node types.

A Sequence node runs its children in order until one fails, so 'Sequence' is the correct node type.

3fill in blank

hard

Fix the error in the code to correctly tick the behavior tree root node.

ROS

BT::NodeStatus status = tree.root()->[1]();

Drag options to blanks, or click blank then click option'

Arun

Bexecute

Ctick

Dstart

Attempts:

3 left

💡 Hint

Common Mistakes

Using non-existent methods like 'execute' or 'run'.

The correct method to update the behavior tree is 'tick()'.

4fill in blank

hard

Fill both blanks to create a Fallback node and add a child action node.

ROS

auto fallback = tree.root()->addChild(BT::[1]Node::create("Fallback"));
fallback->addChild(BT::[2]Node::create("CheckBattery"));

Drag options to blanks, or click blank then click option'

AFallback

BSequence

CAction

DDecorator

Attempts:

3 left

💡 Hint

Common Mistakes

Mixing up node types or using wrong node classes.

A Fallback node tries children until one succeeds, and 'CheckBattery' is an action node.

5fill in blank

hard

Fill all three blanks to define a condition node, a decorator node, and add them to the tree.

ROS

auto condition = BT::[1]Node::create("IsObstacleDetected");
auto decorator = BT::[2]Node::create("Inverter");
decorator->addChild(condition);
tree.root()->addChild([3]);

Drag options to blanks, or click blank then click option'

ACondition

BDecorator

Cdecorator

Dcondition

Attempts:

3 left

💡 Hint

Common Mistakes

Adding the condition node directly instead of the decorator.

The condition node checks a state, the decorator modifies behavior, and the decorator is added to the tree.

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