Marker display for custom visualization in ROS - Cheat Sheet & Quick Revision

Recall & Review

beginner

What is the purpose of a Marker in ROS visualization?

A Marker in ROS is used to display custom shapes, lines, or text in visualization tools like RViz to help understand robot data or environment.

beginner

Which ROS message type is commonly used to publish markers for visualization?

The visualization_msgs/Marker message type is used to define and publish markers for visualization in ROS.

intermediate

How do you specify the shape of a Marker in ROS?

You set the type field of the Marker message to predefined constants like SPHERE, CUBE, ARROW, or LINE_STRIP.

intermediate

What is the role of the header.frame_id in a Marker message?

It defines the coordinate frame in which the marker's position and orientation are interpreted, ensuring correct placement in the visualization.

intermediate

Why is it important to set the lifetime field in a Marker message?

The lifetime controls how long the marker stays visible. Setting it prevents markers from cluttering the visualization if they are no longer relevant.

Which ROS topic type is used to publish custom visualization markers?

A visualization_msgs/Marker

B geometry_msgs/Pose

C sensor_msgs/Image

D std_msgs/String

Markers are published using the visualization_msgs/Marker message type.

How do you change the color of a Marker in ROS?

A Change the <code>type</code> field

B Set the <code>color</code> field with RGBA values

C Modify the <code>header.frame_id</code>

D Publish on a different topic

The color field controls the marker's color using red, green, blue, and alpha transparency values.

What does setting the action field to DELETE do in a Marker message?

A Makes the marker blink

B Changes the marker's shape

C Updates the marker's position

D Removes the marker from the visualization

The DELETE action removes the marker from the visualization display.

Which field controls the position of a Marker in ROS?

A lifetime

B color

C pose.position

D type

The pose.position field sets the marker's location in 3D space.

If you want a Marker to appear as a line connecting points, which type should you use?

A LINE_STRIP

B SPHERE

C TEXT_VIEW_FACING

D CUBE

LINE_STRIP draws a connected line through a list of points.

Explain how to create and display a custom Marker in ROS visualization.

Think about the message fields and how RViz uses them.

Describe the importance of the header.frame_id and lifetime fields in Marker messages.

Consider how markers appear and disappear in RViz.

Practice

1. What is the main purpose of using markers in ROS visualization tools like RViz?

easy

A. To control the robot's movement directly

B. To send commands to the robot's motors

C. To draw shapes in 3D space to help visualize robot data

D. To store robot configuration files

Solution

1. Step 1: Understand marker usage in ROS

   Markers are used to create visual shapes like arrows, cubes, or spheres in RViz to represent data.

2. Step 2: Differentiate markers from control commands

   Markers do not control robot movement or store files; they only help visualize data.

3. Final Answer:

   To draw shapes in 3D space to help visualize robot data -> Option C

4. Quick Check:

   Markers visualize data = B [OK]

Hint: Markers show shapes for visualization, not control [OK]

Common Mistakes:

• Thinking markers control robot movement
• Confusing markers with configuration files
• Assuming markers send commands to motors

2. Which of the following is the correct way to set the type of a marker to a sphere in ROS using the visualization_msgs/Marker message?

easy

A. marker.type = visualization_msgs::Marker::SPHERE;

B. marker.type = visualization_msgs::Marker::CUBE;

C. marker.type = visualization_msgs::Marker::LINE_STRIP;

D. marker.type = visualization_msgs::Marker::TEXT_VIEW_FACING;

Solution

1. Step 1: Identify marker type constants

   ROS defines marker types like CUBE, SPHERE, LINE_STRIP, TEXT_VIEW_FACING as constants in visualization_msgs::Marker.

2. Step 2: Match sphere type

   The constant for a sphere is visualization_msgs::Marker::SPHERE.

3. Final Answer:

   marker.type = visualization_msgs::Marker::SPHERE; -> Option A

4. Quick Check:

   SPHERE type constant = A [OK]

Hint: Use Marker::SPHERE constant to set sphere type [OK]

Common Mistakes:

• Using CUBE instead of SPHERE
• Confusing LINE_STRIP with sphere
• Using text marker type for shapes

3. Given the following ROS Python code snippet, what will be the color of the marker displayed in RViz?

marker.color.r = 0.0
marker.color.g = 1.0
marker.color.b = 0.0
marker.color.a = 0.5

medium

A. Opaque red

B. Fully transparent (invisible)

C. Opaque blue

D. Semi-transparent green

Solution

1. Step 1: Analyze RGB color values

   Red = 0.0, Green = 1.0, Blue = 0.0 means pure green color.

2. Step 2: Check alpha (opacity) value

   Alpha = 0.5 means 50% transparency, so semi-transparent.

3. Final Answer:

   Semi-transparent green -> Option D

4. Quick Check:

   Green=1 and alpha=0.5 = D [OK]

Hint: Alpha <1 means transparency; RGB sets color [OK]

Common Mistakes:

• Ignoring alpha and assuming opaque
• Mixing up RGB values for color
• Thinking alpha=0.5 means fully transparent

4. You wrote this ROS C++ code to publish a marker, but the marker does not appear in RViz. What is the likely error?

visualization_msgs::Marker marker;
marker.header.frame_id = "map";
marker.type = visualization_msgs::Marker::SPHERE;
marker.action = visualization_msgs::Marker::ADD;
marker.pose.position.x = 1.0;
marker.pose.position.y = 2.0;
marker.pose.position.z = 0.0;
marker.scale.x = 0.5;
marker.scale.y = 0.5;
marker.scale.z = 0.5;
marker.color.r = 1.0;
marker.color.g = 0.0;
marker.color.b = 0.0;
marker.color.a = 1.0;
marker_pub.publish(marker);

medium

A. Incorrect marker type used

B. Missing setting of marker.header.stamp to current time

C. Scale values are too small to see

D. Color alpha is zero making it invisible

Solution

1. Step 1: Check marker header completeness

   ROS markers require header.stamp to be set to current time for RViz to display them properly.

2. Step 2: Verify other parameters

   Marker type, scale, and color are valid and visible; alpha is 1.0 (opaque).

3. Final Answer:

   Missing setting of marker.header.stamp to current time -> Option B

4. Quick Check:

   Header stamp missing = A [OK]

Hint: Always set header.stamp to ros::Time::now() [OK]

Common Mistakes:

• Forgetting to set header.stamp
• Using zero alpha making marker invisible
• Assuming scale too small to see

5. You want to display multiple markers at different positions using a single ROS publisher. Which approach correctly updates and publishes markers to show all of them in RViz?

hard

A. Publish each marker separately with unique IDs and the same topic

B. Publish only the last marker repeatedly, ignoring others

C. Publish markers with the same ID to overwrite previous ones

D. Publish markers without setting frame_id to avoid errors

Solution

1. Step 1: Understand marker IDs and topics

   Each marker must have a unique ID to be displayed simultaneously on the same topic.

2. Step 2: Avoid overwriting markers

   Publishing markers with the same ID overwrites previous ones, so unique IDs are needed.

3. Final Answer:

   Publish each marker separately with unique IDs and the same topic -> Option A

4. Quick Check:

   Unique IDs per marker = C [OK]

Hint: Use unique IDs for each marker on one topic [OK]

Common Mistakes:

• Using same ID for multiple markers
• Publishing only one marker and expecting all to show
• Not setting frame_id causing display errors