ROS Navigation stack architecture - Mini Project: Build & Apply

ROS Navigation Stack Architecture

📖 Scenario: You are building a simple robot navigation system using ROS (Robot Operating System). The robot needs to move safely from one point to another in a room while avoiding obstacles.

🎯 Goal: Build the basic ROS Navigation stack setup by creating the necessary data structures, configuration parameters, and core logic to enable the robot to plan and follow a path.

📋 What You'll Learn

Create a dictionary called robot_pose with keys 'x', 'y', and 'theta' representing the robot's current position and orientation.

Create a variable called goal_pose as a dictionary with keys 'x', 'y', and 'theta' representing the target position and orientation.

Create a variable called obstacle_threshold set to 0.5 representing the minimum safe distance from obstacles.

Write a function called is_path_clear that takes a list of obstacle distances and returns true if all distances are greater than obstacle_threshold, otherwise false.

Add a final step to simulate sending the goal to the navigation stack by creating a dictionary called navigation_goal combining goal_pose and a 'frame_id' set to 'map'.

💡 Why This Matters

🌍 Real World

Robots use navigation stacks to move safely in environments like warehouses or homes, avoiding obstacles and reaching targets.

💼 Career

Understanding ROS navigation stack basics is essential for robotics engineers working on autonomous robots and automation.

1

Create the robot's current position

Create a dictionary called robot_pose with these exact keys and values: 'x': 1.0, 'y': 2.0, 'theta': 0.0.

ROS

# Your code here

Hint

Use a Python dictionary with keys 'x', 'y', and 'theta' and assign the exact float values.

2

Set the navigation goal and obstacle threshold

Create a dictionary called goal_pose with 'x': 5.0, 'y': 3.0, 'theta': 1.57. Then create a variable called obstacle_threshold and set it to 0.5.

ROS

robot_pose = {'x': 1.0, 'y': 2.0, 'theta': 0.0}
# Your code here

Hint

Define goal_pose as a dictionary with the exact keys and values. Then define obstacle_threshold as a float variable.

3

Write a function to check if the path is clear

Write a function called is_path_clear that takes a parameter distances (a list of floats). The function returns true if all distances are greater than obstacle_threshold, otherwise returns false. Use a for loop and an if statement.

ROS

robot_pose = {'x': 1.0, 'y': 2.0, 'theta': 0.0}
goal_pose = {'x': 5.0, 'y': 3.0, 'theta': 1.57}
obstacle_threshold = 0.5

def is_path_clear(distances):
    # Your code here

Hint

Loop through each distance and check if it is less than or equal to obstacle_threshold. Return false immediately if so, else return true after the loop.

4

Create the navigation goal dictionary

Create a dictionary called navigation_goal that contains all key-value pairs from goal_pose and adds a key 'frame_id' with value 'map'.

ROS

robot_pose = {'x': 1.0, 'y': 2.0, 'theta': 0.0}
goal_pose = {'x': 5.0, 'y': 3.0, 'theta': 1.57}
obstacle_threshold = 0.5

def is_path_clear(distances):
    for distance in distances:
        if distance <= obstacle_threshold:
            return false
    return true

# Create navigation_goal dictionary here

Hint

Use dictionary unpacking to combine goal_pose with the new key 'frame_id'.

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