Point cloud processing basics in ROS - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to include the header file for point cloud processing in ROS.

ROS

#include [1]

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

A<geometry_msgs/Twist.h>

B<ros/ros.h>

C<sensor_msgs/Image.h>

D<pcl/point_cloud.h>

Attempts:

3 left

💡 Hint

Common Mistakes

Including unrelated headers like ros.h or sensor_msgs/Image.h

Forgetting the angle brackets <> around the header name

The header <pcl/point_cloud.h> is needed to work with point clouds in ROS.

2fill in blank

medium

Complete the code to declare a pointer to a PointCloud of type PointXYZ.

ROS

pcl::PointCloud<pcl::PointXYZ>::Ptr cloud(new [1]);

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

Apcl::PointXYZ

Bsensor_msgs::PointCloud2

Cpcl::PointCloud<pcl::PointXYZ>

Dros::NodeHandle

Attempts:

3 left

💡 Hint

Common Mistakes

Using just PointXYZ instead of PointCloud

Using unrelated types like sensor_msgs::PointCloud2

We create a new PointCloud object of type PointXYZ to initialize the pointer.

3fill in blank

hard

Fix the error in the code to convert a ROS PointCloud2 message to a PCL PointCloud.

ROS

pcl::fromROSMsg([1], *cloud);

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

Acloud_msg

Bcloud

Cros_cloud

Dcloud_ptr

Attempts:

3 left

💡 Hint

Common Mistakes

Passing the PCL cloud pointer instead of the ROS message

Using variable names that refer to pointers instead of messages

The function fromROSMsg takes a sensor_msgs::PointCloud2 message, usually named cloud_msg.

4fill in blank

hard

Fill both blanks to filter points in the cloud by their z coordinate.

ROS

pcl::PassThrough<pcl::PointXYZ> pass;
pass.setInputCloud(cloud);
pass.setFilterFieldName([1]);
pass.setFilterLimits([2], 10.0);
pass.filter(*filtered_cloud);

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

A"z"

B"x"

C5.0

D0.0

Attempts:

3 left

💡 Hint

Common Mistakes

Using the wrong coordinate axis like "x"

Setting filter limits incorrectly or reversed

We filter points by the z coordinate, setting the lower limit to 5.0.

5fill in blank

hard

Fill all three blanks to create a voxel grid filter and downsample the point cloud.

ROS

pcl::VoxelGrid<pcl::PointXYZ> sor;
sor.setInputCloud([1]);
sor.setLeafSize([2], [3], [3]);
sor.filter(*downsampled_cloud);

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

Acloud

B0.1f

C0.05f

Dfiltered_cloud

Attempts:

3 left

💡 Hint

Common Mistakes

Using the wrong input cloud variable

Setting inconsistent leaf sizes for x, y, z

The input cloud is cloud. The leaf size is set to 0.1 for x, y, and z to downsample evenly.

Practice

1. What is the main purpose of point cloud processing in ROS?

easy

A. To control robot motors directly

B. To convert raw 3D sensor data into useful information

C. To send text messages between robots

D. To create 2D images from cameras

Solution

1. Step 1: Understand point cloud data

   Point clouds are collections of 3D points from sensors like LIDAR or depth cameras.

2. Step 2: Purpose of processing

   Processing these points helps robots understand their environment by turning raw data into meaningful info.

3. Final Answer:

   To convert raw 3D sensor data into useful information -> Option B

4. Quick Check:

   Point cloud processing = useful 3D info [OK]

Hint: Point clouds = 3D data, processing = making sense [OK]

Common Mistakes:

• Confusing point clouds with text or 2D images
• Thinking point clouds control motors directly
• Mixing point cloud data with unrelated robot functions

2. Which ROS message type is commonly used to receive point cloud data?

easy

A. sensor_msgs/PointCloud2

B. sensor_msgs/Image

C. geometry_msgs/Twist

D. std_msgs/String

Solution

1. Step 1: Identify message types for sensor data

   Images use sensor_msgs/Image, movement commands use geometry_msgs/Twist, text uses std_msgs/String.

2. Step 2: Point cloud message type

   Point clouds use sensor_msgs/PointCloud2 to send 3D point data in ROS.

3. Final Answer:

   sensor_msgs/PointCloud2 -> Option A

4. Quick Check:

   Point cloud data = PointCloud2 message [OK]

Hint: PointCloud2 is the standard for 3D points in ROS [OK]

Common Mistakes:

• Choosing Image message for point clouds
• Confusing Twist with point cloud data
• Using String message for sensor data

3. Given this ROS Python snippet, what will be printed?

import sensor_msgs.point_cloud2 as pc2
from sensor_msgs.msg import PointCloud2

cloud = PointCloud2()
points = [(1, 2, 3), (4, 5, 6), (7, 8, 9)]
for point in pc2.read_points(cloud, field_names=("x", "y", "z")):
    print(point)

medium

A. SyntaxError due to wrong import

B. (1, 2, 3)\n(4, 5, 6)\n(7, 8, 9)

C. No output because cloud is empty

D. RuntimeError because cloud is not initialized properly

Solution

1. Step 1: Check PointCloud2 initialization

   The cloud variable is created but not filled with points data, so it is empty.

2. Step 2: Effect on read_points

   Reading points from an empty cloud yields no points, so the loop prints nothing.

3. Final Answer:

   No output because cloud is empty -> Option C

4. Quick Check:

   Empty cloud means no points printed [OK]

Hint: Empty PointCloud2 means no points to read [OK]

Common Mistakes:

• Assuming points list fills cloud automatically
• Expecting printed points without proper cloud data
• Confusing import errors with runtime behavior

4. What is wrong with this ROS Python code snippet for filtering points by distance?

import sensor_msgs.point_cloud2 as pc2
from sensor_msgs.msg import PointCloud2

cloud = PointCloud2()
filtered_points = []
for point in pc2.read_points(cloud, field_names=("x", "y", "z")):
    dist = (point[0]**2 + point[1]**2 + point[2]**2)**0.5
    if dist > 5:
        filtered_points.append(point)
print(filtered_points)

medium

A. cloud is empty, so no points to filter

B. Distance calculation uses wrong formula

C. read_points does not accept field_names argument

D. filtered_points should be a set, not a list

Solution

1. Step 1: Check cloud data initialization

   The cloud variable is created but not populated with any points, so it is empty.

2. Step 2: Effect on filtering loop

   Since no points exist, the loop does not run and filtered_points remains empty.

3. Final Answer:

   cloud is empty, so no points to filter -> Option A

4. Quick Check:

   Empty cloud means no filtering possible [OK]

Hint: Empty cloud means no points to filter [OK]

Common Mistakes:

• Assuming cloud has points without initialization
• Thinking distance formula is incorrect
• Believing read_points rejects field_names argument

5. You want to filter a point cloud to keep only points within 3 meters from the robot. Which approach correctly applies this in ROS Python?

hard

A. Convert PointCloud2 to Image and filter pixels by color

B. Publish the original PointCloud2 message without changes

C. Use geometry_msgs/Twist to filter points by distance

D. Use pc2.read_points to iterate points, calculate distance, and append points with distance <= 3 to a new list

Solution

1. Step 1: Understand filtering by distance

   Filtering means selecting points based on their distance from origin (robot).

2. Step 2: Correct method in ROS Python

   Use pc2.read_points to read points, compute distance for each, and keep those within 3 meters.

3. Step 3: Why other options fail

   Publishing original data does not filter; Twist messages control movement, not points; converting to Image loses 3D info.

4. Final Answer:

   Use pc2.read_points to iterate points, calculate distance, and append points with distance <= 3 to a new list -> Option D

5. Quick Check:

   Filter points by distance using read_points [OK]

Hint: Filter points by distance using read_points and condition [OK]

Common Mistakes:

• Publishing unfiltered data expecting filtering
• Using movement messages to filter points
• Converting point clouds to images for filtering