Visualizing sensor data (laser, camera, IMU) in ROS - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to initialize a ROS node for sensor visualization.

ROS

import rospy

def main():
    rospy.[1]('sensor_visualizer')

if __name__ == '__main__':
    main()

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

Arun_node

Bstart_node

Ccreate_node

Dinit_node

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'start_node' instead of 'init_node' causes an AttributeError.

Trying to create a node with 'create_node' is not a valid rospy function.

In ROS, rospy.init_node() initializes a node with a given name.

2fill in blank

medium

Complete the code to subscribe to a laser scan topic named '/scan'.

ROS

from sensor_msgs.msg import LaserScan

rospy.Subscriber('/scan', [1], laser_callback)

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

ALaserScan

BImage

CImu

DPointCloud2

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'Image' instead of 'LaserScan' causes message type mismatch.

Using 'Imu' for laser data is incorrect.

The LaserScan message type is used for laser sensor data in ROS.

3fill in blank

hard

Fix the error in the callback function to correctly process IMU data.

ROS

from sensor_msgs.msg import Imu

def imu_callback(msg):
    orientation = msg.[1].orientation
    rospy.loginfo(f"Orientation: {orientation}")

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

Aorientation

Bpose

Cheader

Dangular_velocity

Attempts:

3 left

💡 Hint

Common Mistakes

Trying to access 'pose.orientation' causes an AttributeError.

Using 'angular_velocity' instead of 'orientation' logs wrong data.

The Imu message has an orientation field directly accessible.

4fill in blank

hard

Fill both blanks to publish a processed camera image on topic '/camera_processed'.

ROS

from sensor_msgs.msg import Image

publisher = rospy.Publisher('/camera_processed', [1], queue_size=[2])

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

AImage

BLaserScan

C10

D5

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'LaserScan' message type for image data causes errors.

Setting queue_size to a string instead of an integer causes runtime errors.

Publishing images requires the Image message type and a queue size integer.

5fill in blank

hard

Fill all three blanks to create a dictionary comprehension that maps sensor names to their message types if the sensor is active.

ROS

sensors = {'laser': LaserScan, 'camera': Image, 'imu': Imu}
active_sensors = {'laser': True, 'camera': False, 'imu': True}
active_msgs = { [1]: [2] for [3] in sensors if active_sensors[[1]] }

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

Asensor

Bsensors[sensor]

Dname

Attempts:

3 left

💡 Hint

Common Mistakes

Using inconsistent variable names causes NameError.

Using the wrong key to check active_sensors causes logic errors.

The comprehension iterates over sensor names, uses the name as key, and maps to the message type from the sensors dict.

Practice

1. What is the primary tool used in ROS to visualize sensor data like laser scans, camera images, and IMU readings?

easy

A. rqt_graph

B. RViz

C. Gazebo

D. rosbag

Solution

1. Step 1: Identify visualization tools in ROS

   RViz is designed specifically for visualizing sensor data and robot state.

2. Step 2: Compare with other tools

   Gazebo is for simulation, rqt_graph shows node connections, rosbag records data but does not visualize directly.

3. Final Answer:

   RViz -> Option B

4. Quick Check:

   Visualizing sensor data = RViz [OK]

Hint: Remember: RViz = visualize sensor data graphically [OK]

Common Mistakes:

• Confusing Gazebo (simulation) with RViz (visualization)
• Thinking rosbag directly shows sensor visuals
• Mixing rqt_graph with visualization tools

2. Which ROS message type is typically used to represent laser scan data for visualization in RViz?

easy

A. geometry_msgs/Twist

B. sensor_msgs/Image

C. sensor_msgs/Imu

D. sensor_msgs/LaserScan

Solution

1. Step 1: Identify message types for sensors

   Laser scan data is published as sensor_msgs/LaserScan in ROS.

2. Step 2: Match message types to sensors

   Image is for cameras, Imu for inertial data, Twist for robot velocity commands.

3. Final Answer:

   sensor_msgs/LaserScan -> Option D

4. Quick Check:

   Laser data = LaserScan message [OK]

Hint: LaserScan message type carries laser data [OK]

Common Mistakes:

• Choosing Image for laser data
• Confusing Imu message with laser data
• Selecting Twist which is for movement commands

3. Given the following ROS Python snippet subscribing to a camera topic, what will be printed when an image message is received?

def callback(data):
    print(f"Received image with height: {data.height}")

sub = rospy.Subscriber('/camera/image_raw', sensor_msgs.msg.Image, callback)
rospy.spin()

medium

A. Received image with height: None

B. Error: 'Image' object has no attribute 'height'

C. Received image with height:

D. No output because callback is never called

Solution

1. Step 1: Understand the callback function

   The callback prints the height attribute of the Image message received.

2. Step 2: Confirm Image message has height attribute

   sensor_msgs/Image includes a height field representing image rows.

3. Final Answer:

   Received image with height: <image height value> -> Option C

4. Quick Check:

   Image message has height attribute = prints height [OK]

Hint: Image messages have height attribute accessible in callback [OK]

Common Mistakes:

• Assuming height is None or missing
• Thinking callback is not triggered
• Confusing attribute names in Image message

4. You wrote this ROS node to visualize IMU data but get an error:

def imu_callback(msg):
    print(msg.orientation.x)

rospy.Subscriber('/imu/data', sensor_msgs.msg.Imu, imu_callback)
rospy.spin()

What is the likely cause of the error?

medium

A. Missing import of sensor_msgs.msg.Imu

B. IMU topic name is incorrect

C. Orientation field does not have x attribute

D. Callback function signature is wrong

Solution

1. Step 1: Check for imports

   Using sensor_msgs.msg.Imu requires importing sensor_msgs.msg.Imu before subscribing.

2. Step 2: Verify topic and callback correctness

   Topic name '/imu/data' and callback signature are correct; orientation.x exists in Imu message.

3. Final Answer:

   Missing import of sensor_msgs.msg.Imu -> Option A

4. Quick Check:

   Import Imu message before subscribing [OK]

Hint: Always import message types before subscribing [OK]

Common Mistakes:

• Assuming topic name is wrong without checking
• Thinking orientation.x does not exist
• Using wrong callback parameters

5. You want to visualize laser scan data and camera images simultaneously in RViz. Which of the following steps correctly sets this up?

hard

A. Launch RViz, add LaserScan and Image displays, set topics to /scan and /camera/image_raw respectively

B. Launch Gazebo, add LaserScan and Image plugins, set topics to /laser and /camera/image

C. Use rosbag play with recorded data, RViz auto-detects topics and shows all sensors

D. Write a node to merge laser and camera data into one topic, then visualize in RViz

Solution

1. Step 1: Understand RViz display setup

   RViz allows adding displays for different sensor types and setting their topics manually.

2. Step 2: Match topics and displays

   LaserScan display subscribes to /scan, Image display subscribes to /camera/image_raw for camera images.

3. Step 3: Evaluate other options

   Gazebo is simulation, rosbag does not auto-add displays, merging topics is unnecessary for visualization.

4. Final Answer:

   Launch RViz, add LaserScan and Image displays, set topics to /scan and /camera/image_raw respectively -> Option A

5. Quick Check:

   RViz displays + correct topics = visualize sensors [OK]

Hint: Add displays in RViz and set correct sensor topics [OK]

Common Mistakes:

• Confusing Gazebo with RViz for visualization
• Expecting rosbag to auto-configure displays
• Merging topics unnecessarily