Why the navigation stack enables autonomous movement in ROS - Test Your Understanding

Practice - 5 Tasks

1fill in blank

easy

Complete the code to initialize the ROS node for navigation.

ROS

ros::init(argc, argv, [1]);

Drag options to blanks, or click blank then click option'

A"navigation_node"

B"robot_driver"

C"move_base"

D"sensor_listener"

Attempts:

3 left

💡 Hint

Common Mistakes

Using unrelated node names like sensor_listener or robot_driver.

The navigation stack typically uses the node named move_base to handle autonomous movement.

2fill in blank

medium

Complete the code to create a ROS publisher for velocity commands.

ROS

ros::Publisher cmd_vel_pub = nh.advertise<geometry_msgs::Twist>([1], 10);

Drag options to blanks, or click blank then click option'

A"/odom"

B"/cmd_vel"

C"/scan"

D"/map"

Attempts:

3 left

💡 Hint

Common Mistakes

Publishing velocity commands on sensor or odometry topics.

The /cmd_vel topic is used to send velocity commands to the robot for autonomous movement.

3fill in blank

hard

Fix the error in the code that sets the robot's goal position using the navigation stack.

ROS

move_base_msgs::MoveBaseGoal goal;
goal.target_pose.header.frame_id = [1];
goal.target_pose.header.stamp = ros::Time::now();

Drag options to blanks, or click blank then click option'

A"map"

B"odom"

C"base_link"

D"laser"

Attempts:

3 left

💡 Hint

Common Mistakes

Using local frames like base_link which cause incorrect goal positioning.

The goal position should be set in the map frame to ensure the robot navigates correctly in the global environment.

4fill in blank

hard

Fill both blanks to correctly subscribe to the laser scan topic and process data.

ROS

ros::Subscriber laser_sub = nh.subscribe([1], 1000, [2]);

Drag options to blanks, or click blank then click option'

A"/scan"

B"/laser_scan"

ClaserCallback

DprocessLaserData

Attempts:

3 left

💡 Hint

Common Mistakes

Using incorrect topic names or callback function names.

The standard laser scan topic is /scan, and the callback function is often named laserCallback to process incoming data.

5fill in blank

hard

Fill all three blanks to create a simple costmap configuration for obstacle avoidance.

ROS

costmap_ros->setFootprint([1]);
costmap_ros->setInflationRadius([2]);
costmap_ros->setRobotRadius([3]);

Drag options to blanks, or click blank then click option'

Afootprint_polygon

B0.55

C0.3

Drobot_base

Attempts:

3 left

💡 Hint

Common Mistakes

Confusing footprint with robot base or using incorrect numeric values.

The footprint polygon defines the robot shape, inflation radius sets the safety margin around obstacles, and robot radius defines the robot's size for collision checking.

Practice

1. What is the main purpose of the ROS navigation stack in autonomous robots?

easy

A. To create 3D models of the robot

B. To plan paths and move the robot to desired locations automatically

C. To only collect sensor data without movement

D. To manually control the robot using a joystick

Solution

1. Step 1: Understand the navigation stack role

   The navigation stack is designed to enable autonomous movement by planning paths and controlling the robot's motion.

2. Step 2: Compare options with this role

   Only To plan paths and move the robot to desired locations automatically describes automatic path planning and movement, which matches the navigation stack's purpose.

3. Final Answer:

   To plan paths and move the robot to desired locations automatically -> Option B

4. Quick Check:

   Navigation stack = autonomous path planning [OK]

Hint: Navigation stack plans and moves robot automatically [OK]

Common Mistakes:

• Confusing manual control with autonomous movement
• Thinking navigation stack only collects data
• Assuming it creates 3D models

2. Which ROS message type is commonly used to send a goal position to the navigation stack?

easy

A. sensor_msgs/LaserScan

B. std_msgs/String

C. nav_msgs/OccupancyGrid

D. geometry_msgs/PoseStamped

Solution

1. Step 1: Identify message types related to navigation goals

   The navigation stack receives goal positions as poses with timestamps, which is geometry_msgs/PoseStamped.

2. Step 2: Eliminate unrelated message types

   LaserScan is sensor data, OccupancyGrid is a map, and String is generic text, so they don't represent goal positions.

3. Final Answer:

   geometry_msgs/PoseStamped -> Option D

4. Quick Check:

   Goal message = PoseStamped [OK]

Hint: Goal positions use PoseStamped messages [OK]

Common Mistakes:

• Choosing sensor data types instead of goal messages
• Confusing map data with goal commands
• Selecting generic message types

3. Given the following ROS code snippet, what will happen when send_goal() is called?

def send_goal():
    goal = PoseStamped()
    goal.header.frame_id = "map"
    goal.pose.position.x = 2.0
    goal.pose.position.y = 3.0
    goal.pose.orientation.w = 1.0
    nav_client.send_goal(goal)

medium

A. The robot will move autonomously to coordinates (2.0, 3.0) on the map frame

B. The robot will stop immediately without moving

C. The robot will move randomly ignoring the goal

D. The code will cause a syntax error and not run

Solution

1. Step 1: Analyze the goal message setup

   The goal is set with position (2.0, 3.0) in the 'map' coordinate frame and a valid orientation (w=1.0 means no rotation).

2. Step 2: Understand the effect of sending the goal

   Calling nav_client.send_goal(goal) sends this goal to the navigation stack, which will plan and move the robot there autonomously.

3. Final Answer:

   The robot will move autonomously to coordinates (2.0, 3.0) on the map frame -> Option A

4. Quick Check:

   Sending goal = autonomous move to (2.0, 3.0) [OK]

Hint: Sending PoseStamped goal triggers autonomous movement [OK]

Common Mistakes:

• Assuming the robot stops instead of moving
• Thinking the robot moves randomly
• Believing the code has syntax errors

4. A developer tries to send a navigation goal but the robot does not move. The code snippet is:

goal = PoseStamped()
goal.pose.position.x = 1.0
goal.pose.position.y = 1.0
nav_client.send_goal(goal)

What is the likely cause of the problem?

medium

A. The goal message is missing the header frame_id, so the navigation stack ignores it

B. The position values are invalid and cause a runtime error

C. The send_goal method is not defined in nav_client

D. The robot hardware is disconnected

Solution

1. Step 1: Check the goal message completeness

   The goal message lacks the header.frame_id field, which tells the navigation stack the coordinate frame of the goal.

2. Step 2: Understand navigation stack requirements

   Without frame_id, the navigation stack cannot interpret the goal position and will ignore the command, so the robot does not move.

3. Final Answer:

   The goal message is missing the header frame_id, so the navigation stack ignores it -> Option A

4. Quick Check:

   Missing frame_id = ignored goal [OK]

Hint: Always set header.frame_id in goal messages [OK]

Common Mistakes:

• Assuming position values cause errors
• Thinking send_goal method is missing
• Blaming hardware without checking code

5. In a complex environment, the navigation stack uses sensor data and maps to avoid obstacles. Which combination best explains how the navigation stack enables safe autonomous movement?

hard

A. It ignores sensor data and follows a fixed path regardless of obstacles

B. It moves randomly and stops only when hitting an obstacle

C. It uses sensor data to update the map and plans a path avoiding obstacles before moving

D. It requires manual joystick input to avoid obstacles

Solution

1. Step 1: Understand sensor and map integration

   The navigation stack continuously updates its map with sensor data to detect obstacles in real time.

2. Step 2: Analyze path planning and obstacle avoidance

   It plans a safe path that avoids obstacles before moving, enabling autonomous and safe navigation.

3. Final Answer:

   It uses sensor data to update the map and plans a path avoiding obstacles before moving -> Option C

4. Quick Check:

   Sensor + map = safe path planning [OK]

Hint: Sensor data + map = safe autonomous path [OK]

Common Mistakes:

• Thinking robot moves randomly
• Assuming fixed paths ignore obstacles
• Believing manual control is needed for safety