Recovery behaviors in ROS - Cheat Sheet & Quick Revision

Recall & Review

beginner

What is a recovery behavior in ROS navigation?

A recovery behavior is a predefined action that a robot takes when it gets stuck or cannot find a valid path. It helps the robot to try to get back on track and continue moving safely.

beginner

Name two common recovery behaviors used in ROS navigation.

Two common recovery behaviors are clearing the costmap (removing old obstacle data) and rotating in place to find a new path.

intermediate

How does the 'clear_costmap_recovery' behavior help a robot?

It clears the robot's local costmap of obstacles that might be outdated or incorrect, allowing the planner to find a new path without old obstacles blocking it.

intermediate

What is the purpose of the 'rotate_recovery' behavior in ROS?

The 'rotate_recovery' behavior makes the robot turn in place to scan the surroundings. This can help the robot find a new path or clear temporary obstacles from its sensors.

beginner

Why is it important to configure recovery behaviors in a robot's navigation stack?

Configuring recovery behaviors ensures the robot can handle unexpected situations autonomously, improving reliability and safety during navigation.

What does a recovery behavior do when a robot is stuck?

A Sends an error message only

B Stops the robot permanently

C Attempts actions to get the robot unstuck

D Turns off the robot's sensors

Recovery behaviors try to help the robot get unstuck by performing specific actions.

Which recovery behavior clears outdated obstacle data from the map?

A clear_costmap_recovery

B rotate_recovery

C move_base

D path_planner

clear_costmap_recovery removes old obstacle data to help the planner find a new path.

What is the main goal of the rotate_recovery behavior?

A Move the robot forward quickly

B Clear the global map

C Stop the robot immediately

D Turn the robot in place to scan surroundings

rotate_recovery turns the robot to scan and find new paths or clear sensor obstacles.

When should recovery behaviors be triggered?

A When the robot cannot find a valid path or is stuck

B Only during startup

C Every time the robot moves

D When the battery is low

Recovery behaviors activate when the robot is stuck or path planning fails.

Why is it important to have multiple recovery behaviors?

A To confuse the robot

B To provide different ways to recover from various problems

C To slow down the robot

D To use more memory

Multiple recovery behaviors give the robot options to handle different stuck situations.

Explain what recovery behaviors are in ROS navigation and why they are useful.

Think about what a robot does when it cannot move forward.

Describe how the 'clear_costmap_recovery' and 'rotate_recovery' behaviors work and when they might be used.

Consider how the robot updates its map and looks around.

Practice

1. What is the main purpose of recovery behaviors in ROS navigation?

easy

A. To help the robot fix problems when it gets stuck

B. To speed up the robot's movement

C. To map the environment faster

D. To reduce battery usage

Solution

1. Step 1: Understand recovery behaviors role

   Recovery behaviors are designed to help the robot when it encounters problems like being stuck or blocked.

2. Step 2: Compare options with purpose

   Only To help the robot fix problems when it gets stuck matches this purpose. Other options describe unrelated functions.

3. Final Answer:

   To help the robot fix problems when it gets stuck -> Option A

4. Quick Check:

   Recovery behaviors fix stuck robot = C [OK]

Hint: Recovery behaviors fix stuck robots, not speed or mapping [OK]

Common Mistakes:

• Confusing recovery behaviors with mapping functions
• Thinking recovery behaviors save battery
• Assuming recovery speeds up navigation

2. Which YAML configuration snippet correctly enables a recovery behavior in ROS navigation?

easy

A. recovery_behaviors:
- clear_costmap_recovery
- rotate_recovery

B. recovery_behaviors = [clear_costmap, rotate_recovery]

C. recovery_behaviors:
clear_costmap: true
rotate_recovery: true

D. recovery_behaviors:
- name: clear_costmap
type: "clear_costmap_recovery/ClearCostmapRecovery"

Solution

1. Step 1: Identify correct YAML syntax for recovery behaviors

   ROS navigation expects a list of recovery behaviors with name and type keys in YAML format.

2. Step 2: Check each option's format

   recovery_behaviors: - name: clear_costmap type: "clear_costmap_recovery/ClearCostmapRecovery" uses correct YAML list with name and type. Options B, C, and D use invalid syntax or missing keys.

3. Final Answer:

   YAML list with name and type keys -> Option D

4. Quick Check:

   YAML recovery behaviors need name and type keys = A [OK]

Hint: YAML lists need dash and key:value pairs for recovery behaviors [OK]

Common Mistakes:

• Using equal signs instead of colon in YAML
• Missing name or type keys in recovery behavior
• Using Python list syntax instead of YAML

3. Given this ROS recovery behavior configuration snippet, what will happen when the robot is stuck?

recovery_behaviors:
  - name: rotate_recovery
    type: "rotate_recovery/RotateRecovery"

medium

A. The robot will clear its costmap to remove obstacles

B. The robot will rotate in place to find a new path

C. The robot will stop and wait indefinitely

D. The robot will move backward quickly

Solution

1. Step 1: Understand rotate_recovery behavior

   The rotate_recovery behavior makes the robot spin in place to scan surroundings and find a new path.

2. Step 2: Match behavior to options

   The robot will rotate in place to find a new path correctly describes rotation. The robot will clear its costmap to remove obstacles describes clearing costmap, which is different. Options C and D do not match rotate_recovery.

3. Final Answer:

   The robot will rotate in place to find a new path -> Option B

4. Quick Check:

   rotate_recovery spins robot = B [OK]

Hint: RotateRecovery spins robot to find path, not clear or stop [OK]

Common Mistakes:

• Confusing rotate_recovery with clear_costmap_recovery
• Thinking robot stops instead of rotating
• Assuming robot moves backward

4. You configured a recovery behavior in ROS but it never triggers when the robot is stuck. What is the most likely cause?

medium

A. The recovery behavior is not listed in the YAML file

B. The robot's battery is low

C. The robot is moving too fast

D. The map is too large

Solution

1. Step 1: Check recovery behavior configuration

   If the recovery behavior is not listed or enabled in the YAML file, it will not run.

2. Step 2: Evaluate other options

   Battery level, speed, or map size do not prevent recovery behaviors from triggering directly.

3. Final Answer:

   The recovery behavior is not listed in the YAML file -> Option A

4. Quick Check:

   Missing YAML config stops recovery trigger = A [OK]

Hint: Recovery behaviors must be listed in YAML to trigger [OK]

Common Mistakes:

• Blaming battery or speed for recovery not triggering
• Ignoring YAML configuration
• Assuming map size affects recovery behavior

5. You want the robot to first clear its costmap and then rotate if still stuck. How should you configure the recovery behaviors in YAML?

hard

A. recovery_behaviors:
- name: rotate_recovery
type: "rotate_recovery/RotateRecovery"
- name: clear_costmap
type: "clear_costmap_recovery/ClearCostmapRecovery"

B. recovery_behaviors:
- clear_costmap_recovery
- rotate_recovery

C. recovery_behaviors:
- name: clear_costmap
type: "clear_costmap_recovery/ClearCostmapRecovery"
- name: rotate_recovery
type: "rotate_recovery/RotateRecovery"

D. recovery_behaviors:
clear_costmap: true
rotate_recovery: true

Solution

1. Step 1: Understand order matters in recovery behaviors

   ROS runs recovery behaviors in the order listed in YAML. To clear costmap first, it must be listed first.

2. Step 2: Check YAML syntax and order

   recovery_behaviors: - name: clear_costmap type: "clear_costmap_recovery/ClearCostmapRecovery" - name: rotate_recovery type: "rotate_recovery/RotateRecovery" lists clear_costmap first, then rotate_recovery, with correct YAML syntax. recovery_behaviors: - name: rotate_recovery type: "rotate_recovery/RotateRecovery" - name: clear_costmap type: "clear_costmap_recovery/ClearCostmapRecovery" reverses order. Options B and C have invalid syntax.

3. Final Answer:

   List clear_costmap first, then rotate_recovery with correct YAML -> Option C

4. Quick Check:

   Order in YAML controls recovery sequence = D [OK]

Hint: List recovery behaviors in YAML in desired run order [OK]

Common Mistakes:

• Reversing order of recovery behaviors
• Using invalid YAML syntax
• Assuming order does not matter