Recovery behaviors in ROS - Performance & Optimization

Performance: Recovery behaviors

MEDIUM IMPACT

Recovery behaviors impact how quickly a robotic system can resume normal operation after a failure, affecting interaction responsiveness and system stability.

Handling sensor failure and resuming normal operation

ROS

def recovery_behavior():
    if not sensor_ok():
        schedule_retry(delay=1)  # non-blocking retry
    else:
        resume_operations()

Non-blocking retries allow other tasks to run, reducing input lag.

📈 Performance Gainmaintains responsive control loop, reduces input delay

Handling sensor failure and resuming normal operation

ROS

def recovery_behavior():
    while not sensor_ok():
        time.sleep(1)  # blocking wait
    resume_operations()

Blocking the main control loop causes input lag and delays other system tasks.

📉 Performance Costblocks main loop for seconds, increasing input latency

Performance Comparison

Pattern	Blocking Behavior	Control Loop Delay	System Responsiveness	Verdict
Blocking wait in recovery	Yes	High	Low	[X] Bad
Non-blocking scheduled retry	No	Minimal	High	[OK] Good

Rendering Pipeline

Recovery behaviors run within the robot's control loop affecting sensor data processing and command execution stages.

→Sensor Data Processing

→Control Loop Execution

→Command Dispatch

⚠️ BottleneckBlocking waits during recovery delay sensor updates and command execution.

Core Web Vital Affected

INP

Recovery behaviors impact how quickly a robotic system can resume normal operation after a failure, affecting interaction responsiveness and system stability.

Optimization Tips

1Avoid blocking calls in recovery behaviors to keep control loops responsive.

2Use asynchronous timers or scheduled retries for recovery attempts.

3Monitor recovery delays with tracing tools to identify bottlenecks.

Performance Quiz - 3 Questions

What is the main performance issue with blocking waits in recovery behaviors?

A They delay the control loop and reduce system responsiveness.

B They increase memory usage significantly.

C They cause excessive network traffic.

D They improve sensor accuracy.

DevTools: ros2_tracing

How to check: Record a trace during recovery behavior execution and analyze task durations and blocking calls.

What to look for: Look for long blocking calls or delays in control loop callbacks indicating poor recovery performance.

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