Robot frame conventions (base_link, odom, map) in ROS - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to publish the robot's base frame name.

ROS

frame_id = "[1]"  # Robot's base frame

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

Abase_link

Bodom

Cmap

Dworld

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'odom' or 'map' instead of 'base_link' for the robot base frame.

The base_link frame represents the robot's base in ROS conventions.

2fill in blank

medium

Complete the code to specify the odometry frame in a transform broadcaster.

ROS

odom_frame = "[1]"  # Frame for odometry reference

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

Alaser

Bbase_link

Cmap

Dodom

Attempts:

3 left

💡 Hint

Common Mistakes

Confusing 'odom' with 'map' or 'base_link' frames.

The odom frame tracks the robot's position relative to its starting point using odometry.

3fill in blank

hard

Fix the error in the frame assignment to use the global fixed frame.

ROS

global_frame = "[1]"  # Fixed global frame for localization

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

Abase_link

Bmap

Ccamera

Dodom

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'odom' or 'base_link' instead of 'map' for the global frame.

The map frame is the fixed global frame used for localization and navigation.

4fill in blank

hard

Fill both blanks to correctly define a transform from odom to base_link.

ROS

tf_broadcaster.sendTransform(
  translation, rotation, time, "[2]", "[1]"
)

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

Abase_link

Bodom

Cmap

Dlaser

Attempts:

3 left

💡 Hint

Common Mistakes

Swapping parent and child frames in the transform.

The transform is from odom (parent) to base_link (child) frame.

5fill in blank

hard

Fill all three blanks to create a dictionary mapping frames to their descriptions.

ROS

frame_descriptions = {
  "[1]": "Robot base frame",
  "[2]": "Odometry reference frame",
  "[3]": "Global fixed map frame"
}

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

Abase_link

Bodom

Cmap

Dcamera

Attempts:

3 left

💡 Hint

Common Mistakes

Mixing up frame names or including unrelated frames like 'camera'.

This dictionary correctly maps each standard ROS frame to its role.

Practice

1. Which ROS frame represents the robot's own center point and moves with it?

easy

A. map

B. base_link

C. odom

D. world

Solution

1. Step 1: Understand the role of base_link

   base_link is the frame fixed to the robot itself, representing its center.

2. Step 2: Compare with other frames

   odom tracks movement but can drift, map is a fixed global frame, and world is not a standard ROS frame here.

3. Final Answer:

   base_link -> Option B

4. Quick Check:

   Robot center frame = base_link [OK]

Hint: Remember: base_link moves with the robot itself [OK]

Common Mistakes:

• Confusing odom as robot center
• Thinking map moves with robot
• Assuming world is standard ROS frame

2. Which of the following is the correct way to refer to the odometry frame in ROS?

easy

A. odom

B. odom_frame

C. map

D. base_link

Solution

1. Step 1: Identify the standard odometry frame name

   The standard ROS frame for odometry is odom.

2. Step 2: Check other options

   base_link is robot center, map is global frame, and odom_frame is not a standard name.

3. Final Answer:

   odom -> Option A

4. Quick Check:

   Odometry frame = odom [OK]

Hint: Odom frame is just 'odom', no extra suffix [OK]

Common Mistakes:

• Adding '_frame' suffix incorrectly
• Mixing base_link with odom
• Using map instead of odom

3. Given a robot moving in a room, which frame will show drift over time due to sensor noise?

medium

A. world

B. map

C. base_link

D. odom

Solution

1. Step 1: Understand frame drift

   The odom frame tracks movement from start but can accumulate errors causing drift.

2. Step 2: Compare with other frames

   map is fixed and does not drift, base_link moves with robot, world is not standard here.

3. Final Answer:

   odom -> Option D

4. Quick Check:

   Drifting frame = odom [OK]

Hint: Odom drifts; map stays fixed [OK]

Common Mistakes:

• Thinking map drifts
• Confusing base_link with odom
• Assuming world is used here

4. You notice your robot's position drifts over time when using the odom frame. What is the best way to fix this issue?

medium

A. Use the map frame for global localization

B. Switch to using the base_link frame for navigation

C. Reset the odom frame periodically

D. Ignore the drift as it is normal

Solution

1. Step 1: Understand the cause of drift

   The odom frame drifts due to sensor noise and integration errors over time.

2. Step 2: Choose a frame that corrects drift

   The map frame is fixed globally and used for localization to correct odom drift.

3. Final Answer:

   Use the map frame for global localization -> Option A

4. Quick Check:

   Fix drift with map frame [OK]

Hint: Use map frame to correct odom drift [OK]

Common Mistakes:

• Using base_link which moves with robot
• Resetting odom often is impractical
• Ignoring drift causes navigation errors

5. You want to build a navigation system that uses sensor data to update the robot's position on a fixed map. Which sequence of frames should you use to correctly represent the robot's position relative to the world?

hard

A. odom -> base_link -> map

B. base_link -> odom -> map

C. map -> odom -> base_link

D. base_link -> map -> odom

Solution

1. Step 1: Understand frame hierarchy

   The robot's position is relative to base_link, which is relative to odom, and odom is relative to map.

2. Step 2: Determine correct parent-child order

   The correct chain is map (global fixed frame) -> odom (local odometry) -> base_link (robot center).

3. Final Answer:

   map -> odom -> base_link -> Option C

4. Quick Check:

   Global to robot: map -> odom -> base_link [OK]

Hint: Frame chain goes from map down to base_link [OK]

Common Mistakes:

• Reversing frame order
• Putting base_link as parent of odom
• Ignoring map as global frame