Recovery behaviors in ROS - Step-by-Step Execution

Concept Flow - Recovery behaviors

Robot encounters obstacle

↓

Trigger recovery behavior

↓

Select recovery action

↓

Execute recovery action

↓

Check if obstacle cleared

↓

Resume normal

↓

navigation

↓

All recovery failed

↓

Report failure

The robot detects a problem, triggers recovery, tries actions to fix it, and either resumes or reports failure.

Execution Sample

ROS

if obstacle_detected:
    recovery_behavior.execute()
    if recovery_successful:
        resume_navigation()
    else:
        report_failure()

Robot detects obstacle, runs recovery, then resumes or reports failure.

Execution Table

Step	Event	Action	Result	Next Step
1	Obstacle detected	Trigger recovery_behavior.execute()	Recovery started	Check recovery result
2	Recovery action 1 executed	Clear obstacle by backing up	Obstacle partially cleared	Check if cleared
3	Obstacle cleared?	Condition check	No	Try next recovery action
4	Recovery action 2 executed	Rotate in place	Obstacle cleared	Resume navigation
5	Resume navigation	Continue normal path	Navigation resumed	End
6	End	No further action	Robot moving normally	Stop

💡 Recovery succeeded at step 4, robot resumes navigation

Variable Tracker

Variable	Start	After Step 2	After Step 4	Final
obstacle_detected	True	True	True	False
recovery_successful	False	False	True	True
navigation_state	Normal	Recovery	Normal	Normal

Key Moments - 2 Insights

Why does the robot try multiple recovery actions instead of just one?

Because the first recovery action may not clear the obstacle (see execution_table step 3), so it tries the next action until success or failure.

What happens if all recovery actions fail?

The robot reports failure and stops recovery attempts (not shown in this trace but implied after all actions fail).

Visual Quiz - 3 Questions

Look at the execution_table, what is the robot's state after step 2?

A Obstacle cleared

B Obstacle partially cleared

C Recovery failed

D Navigation resumed

💡 Hint

Check the 'Result' column at step 2 in execution_table

At which step does the robot resume normal navigation?

A Step 3

B Step 4

C Step 5

D Step 6

💡 Hint

Look for 'Resume navigation' action in execution_table

If the first recovery action cleared the obstacle, how would the execution_table change?

A Step 3 would show 'Yes' and skip step 4

B Step 2 would be skipped

C Robot would report failure immediately

D Navigation would never resume

💡 Hint

Refer to the 'Obstacle cleared?' condition at step 3 in execution_table

Concept Snapshot

Recovery behaviors in ROS:
- Triggered when robot faces obstacle
- Executes predefined recovery actions (e.g., back up, rotate)
- Checks if obstacle cleared after each action
- Resumes navigation if successful
- Reports failure if all actions fail

Full Transcript

Recovery behaviors help a robot handle obstacles during navigation. When the robot detects an obstacle, it triggers recovery actions like backing up or rotating. After each action, it checks if the obstacle is cleared. If yes, it resumes normal navigation. If not, it tries the next recovery action. If all fail, it reports failure. This process ensures the robot can try multiple ways to fix problems before stopping.

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