ROS Navigation stack architecture - Practice Problems & Coding Challenges

Challenge - 5 Problems

🧠 Conceptual

intermediate

Core components of the ROS Navigation stack

Which of the following is NOT a core component of the ROS Navigation stack?

A move_base

B rviz

C amcl

D costmap_2d

💡 Hint

Think about which component is mainly for visualization rather than navigation.

The ROS Navigation stack core components include move_base for path planning and execution, amcl for localization, and costmap_2d for obstacle representation. rviz is a visualization tool, not a navigation component.

❓ component_behavior

intermediate

Behavior of the costmap_2d in obstacle detection

What happens in the ROS Navigation stack when the costmap_2d detects a new obstacle in the robot's path?

A The global planner recalculates a new path avoiding the obstacle.

B The amcl node updates the robot's position to avoid the obstacle.

C The move_base immediately stops the robot and waits for manual intervention.

D The robot ignores the obstacle and continues on the original path.

💡 Hint

Consider which component is responsible for path planning.

The costmap_2d updates the obstacle information, prompting the move_base to invoke the global planner to find a new path that avoids the obstacle. The robot does not stop immediately unless programmed to do so.

❓ lifecycle

advanced

Lifecycle of move_base during navigation

During a navigation task, what is the correct sequence of move_base states from receiving a goal to reaching it?

A 1,2,3,4

B 1,3,2,4

C 2,1,3,4

D 1,2,4,3

💡 Hint

Think about the order from receiving a goal to planning and execution.

The move_base first receives the goal, then calls the global planner to create a path. After that, the local planner follows the path to move the robot. Finally, the goal is either reached or aborted.

📝 Syntax

advanced

Correct YAML configuration for costmap_2d inflation layer

Which YAML snippet correctly configures the inflation layer in costmap_2d to have an inflation radius of 0.5 meters?

A

inflation_layer:
  inflation_radius = 0.5

B

inflation_layer:
  inflation_radius: 0,5

C

inflation_layer:
  inflation_radius: 0.5

D

inflation_layer:
  inflation_radius: '0.5m'

💡 Hint

YAML uses colon and space for key-value pairs and decimal points for floats.

YAML syntax requires a colon and space to assign values. The value should be a number without units or commas. Option C follows correct YAML syntax.

🔧 Debug

expert

Diagnosing localization failure with amcl

Given the following symptoms: the robot's pose estimate does not update and stays fixed despite movement, which of the following is the MOST likely cause in the amcl configuration?

A The robot's odometry frame is set to 'map' instead of 'odom'.

B The global planner is not generating a path.

C The costmap_2d inflation radius is set too high.

D The laser scan topic is incorrectly set or not publishing data.

💡 Hint

amcl relies heavily on sensor data to update pose.

If the laser scan topic is wrong or not publishing, amcl cannot update the robot's pose estimate, causing it to stay fixed. Other options affect different parts of navigation or are incorrect frame settings.

Practice

1. Which component in the ROS Navigation stack is responsible for localizing the robot on a known map?

easy

A. amcl

B. move_base

C. map_server

D. costmap_2d

Solution

1. Step 1: Understand the role of amcl

   amcl stands for Adaptive Monte Carlo Localization and it helps the robot find its position on a known map.

2. Step 2: Differentiate from other components

   map_server provides the map, move_base plans and executes paths, and costmap_2d manages obstacle data.

3. Final Answer:

   amcl -> Option A

4. Quick Check:

   Localization = amcl [OK]

Hint: Localization uses amcl in ROS Navigation stack [OK]

Common Mistakes:

• Confusing map_server as localization
• Thinking move_base localizes robot
• Mixing costmap_2d with localization

2. Which of the following is the correct way to launch the ROS Navigation stack using move_base?

easy

A. rosrun map_server map_server

B. rosrun move_base move_base

C. roslaunch amcl amcl.launch

D. roslaunch move_base move_base.launch

Solution

1. Step 1: Identify the launch command for move_base

   The Navigation stack uses launch files to start nodes with configurations. The correct launch file for move_base is move_base.launch.

2. Step 2: Differentiate from other commands

   rosrun runs single nodes without launch files. amcl.launch and map_server are for other components.

3. Final Answer:

   roslaunch move_base move_base.launch -> Option D

4. Quick Check:

   Launch move_base with roslaunch [OK]

Hint: Use roslaunch move_base move_base.launch to start navigation [OK]

Common Mistakes:

• Using rosrun instead of roslaunch for move_base
• Launching wrong component like amcl for navigation
• Missing launch file name in command

3. Given the following ROS Navigation stack setup, what will happen if the costmap_2d detects an obstacle in front of the robot?

1. Robot receives sensor data.
2. costmap_2d updates obstacle position.
3. move_base plans path.

medium

A. Robot ignores obstacle and moves forward.

B. Robot stops and replans path to avoid obstacle.

C. Robot shuts down navigation stack.

D. Robot moves backward without replanning.

Solution

1. Step 1: Understand costmap_2d role in obstacle detection

   costmap_2d creates a map of obstacles around the robot using sensor data.

2. Step 2: Analyze move_base behavior on obstacle detection

   move_base uses the costmap to plan safe paths. When an obstacle is detected, it replans to avoid collision.

3. Final Answer:

   Robot stops and replans path to avoid obstacle. -> Option B

4. Quick Check:

   Obstacle detected = path replanned [OK]

Hint: Obstacle detected triggers path replanning in move_base [OK]

Common Mistakes:

• Assuming robot ignores obstacles
• Thinking navigation stack shuts down on obstacles
• Believing robot moves backward automatically

4. You launched the ROS Navigation stack but the robot does not move even though the goal is set. Which of the following is the most likely cause?

medium

A. The robot's battery is fully charged.

B. map_server is publishing the map correctly.

C. amcl is not publishing the robot's pose.

D. move_base is receiving goals and planning paths.

Solution

1. Step 1: Check localization status

   If amcl is not publishing the robot's pose, move_base cannot know where the robot is to plan a path.

2. Step 2: Evaluate other components

   map_server publishing map and move_base receiving goals are good signs. Battery charged is unrelated to navigation stack software.

3. Final Answer:

   amcl is not publishing the robot's pose. -> Option C

4. Quick Check:

   Localization failure = no movement [OK]

Hint: No movement? Check if amcl publishes pose [OK]

Common Mistakes:

• Ignoring localization as cause
• Assuming battery status affects navigation stack
• Thinking map_server alone controls movement

5. You want your robot to navigate in a dynamic environment where obstacles can appear suddenly. Which combination of ROS Navigation stack components should you configure to ensure safe and smooth navigation?

hard

A. Use map_server for static map, amcl for localization, move_base with local_costmap for obstacle avoidance.

B. Use only map_server and move_base without costmaps.

C. Use amcl and disable move_base to avoid replanning.

D. Use costmap_2d only without localization or map.

Solution

1. Step 1: Identify components for dynamic obstacle handling

   local_costmap updates obstacles in real-time for move_base to avoid them.

2. Step 2: Combine with localization and static map

   amcl localizes robot on the static map from map_server. Together they enable safe navigation.

3. Step 3: Evaluate other options

   Options without costmaps or localization will fail in dynamic environments.

4. Final Answer:

   Use map_server, amcl, move_base with local_costmap -> Option A

5. Quick Check:

   Static map + localization + local costmap = safe navigation [OK]

Hint: Combine static map, localization, and local costmap for dynamic obstacles [OK]

Common Mistakes:

• Ignoring local costmap for dynamic obstacles
• Disabling move_base disables path planning
• Using costmap without localization or map