Behavior trees concept for robotics in ROS - Practice Problems & Coding Challenges

Challenge - 5 Problems

❓ component_behavior

intermediate

What is the output behavior of this simple ROS behavior tree snippet?

Consider a behavior tree with a Sequence node having two children: a Condition node that checks if a sensor value is above a threshold, and an Action node that commands the robot to move forward. What happens if the sensor value is below the threshold?

ROS

Sequence
 ├─ Condition: sensor_value > threshold
 └─ Action: move_forward()

A The robot does not move forward because the Condition node fails, stopping the Sequence.

B The robot moves forward only if the sensor value is below the threshold.

C The robot moves backward because the Condition node fails.

D The robot moves forward regardless of the sensor value.

💡 Hint

Remember that in a Sequence node, all children must succeed for the sequence to continue.

In a Sequence node, if any child fails, the entire sequence fails and subsequent actions are not executed. Since the Condition node fails when sensor_value <= threshold, the Action node to move forward is not run.

❓ state_output

intermediate

What is the state of the behavior tree after running this ROS BT snippet?

A Fallback node has two children: an Action node that tries to pick up an object, and a Log node that logs 'Pick failed'. If the Action node fails, what is the status of the Fallback node?

ROS

Fallback
 ├─ Action: pick_object()
 └─ Action: log('Pick failed')

A The Fallback node returns success only if pick_object() succeeds.

B The Fallback node returns failure immediately after pick_object() fails.

C The Fallback node returns running indefinitely.

D The Fallback node returns success after logging the failure.

💡 Hint

Fallback nodes try children until one succeeds.

Fallback nodes return success as soon as one child succeeds. If pick_object() fails, the Log action runs and returns success, so the Fallback node returns success.

📝 Syntax

advanced

Which ROS behavior tree XML snippet is syntactically correct?

Identify the valid XML snippet for a behavior tree with a Sequence node containing two Action nodes named 'Move' and 'Grab'.

A <Sequence><Action name='Move'/><Action name='Grab'/></Sequence>

B <Sequence><Action name='Move'><Action name='Grab'/></Sequence>

C <Sequence><Action name='Move'/><Action name='Grab'></Sequence>

D <Sequence><Action name='Move'></Action><Action name='Grab'></Action>

💡 Hint

Check for proper closing tags and nesting.

Option A correctly closes all tags and nests the Action nodes inside the Sequence node properly. Other options have missing or mismatched closing tags.

🔧 Debug

advanced

Why does this ROS behavior tree never execute the Action node?

Given a Sequence node with a Condition node that always returns failure, followed by an Action node, why does the Action node never run?

ROS

Sequence
 ├─ Condition: always returns failure
 └─ Action: perform_task()

A Because the Condition node returns success, skipping the Action node.

B Because the Action node is incorrectly defined and cannot run.

C Because the Sequence node stops at the first failure and does not run subsequent children.

D Because the Sequence node runs children in parallel and the Action node is delayed.

💡 Hint

Recall how Sequence nodes handle child node failures.

Sequence nodes require all children to succeed in order. If any child fails, the sequence stops immediately and later children are not executed.

🧠 Conceptual

expert

What is the main advantage of using Behavior Trees over traditional state machines in ROS robotics?

Choose the best explanation for why Behavior Trees are preferred in complex robot control scenarios.

A Behavior Trees require less memory and CPU than state machines, making them faster in all cases.

B Behavior Trees allow modular, reusable, and hierarchical control flow with clear success/failure handling, improving scalability and maintainability.

C Behavior Trees eliminate the need for any debugging or testing in robot control software.

D Behavior Trees force all robot actions to run in parallel, increasing responsiveness.

💡 Hint

Think about how behavior trees organize tasks and handle outcomes.

Behavior Trees provide a structured way to organize robot behaviors with modular nodes that can be reused and combined hierarchically. They handle success and failure clearly, making complex behaviors easier to manage than flat state machines.

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