Point cloud processing basics in ROS - Practice Problems & Coding Challenges

Challenge - 5 Problems

❓ component_behavior

intermediate

What is the output of this ROS node processing a point cloud?

Consider a ROS node subscribing to a point cloud topic and applying a passthrough filter on the 'z' axis to keep points between 0.5 and 1.5 meters. What will the filtered point cloud contain?

ROS

void cloudCallback(const sensor_msgs::PointCloud2ConstPtr& cloud_msg) {
  pcl::PointCloud<pcl::PointXYZ>::Ptr cloud(new pcl::PointCloud<pcl::PointXYZ>);
  pcl::fromROSMsg(*cloud_msg, *cloud);

  pcl::PassThrough<pcl::PointXYZ> pass;
  pass.setInputCloud(cloud);
  pass.setFilterFieldName("z");
  pass.setFilterLimits(0.5, 1.5);
  pcl::PointCloud<pcl::PointXYZ> cloud_filtered;
  pass.filter(cloud_filtered);

  // Publish cloud_filtered
}

A The output cloud is unchanged from the input cloud.

B The output cloud contains all points except those with z values between 0.5 and 1.5 meters.

C The output cloud contains points with x values between 0.5 and 1.5 meters.

D The output cloud contains only points with z values between 0.5 and 1.5 meters inclusive.

💡 Hint

Think about what the passthrough filter does with the specified field and limits.

The passthrough filter keeps points within the specified limits on the chosen field. Here, it filters points on the 'z' axis between 0.5 and 1.5 meters.

📝 Syntax

intermediate

Which option correctly converts a ROS PointCloud2 message to a PCL PointCloud?

Given a sensor_msgs::PointCloud2ConstPtr named cloud_msg, which code snippet correctly converts it to pcl::PointCloud?

A pcl::PointCloud<pcl::PointXYZ>::Ptr cloud(new pcl::PointCloud<pcl::PointXYZ>); pcl::fromROSMsg(*cloud_msg, *cloud);

B pcl::PointCloud<pcl::PointXYZ>::Ptr cloud(new pcl::PointCloud<pcl::PointXYZ>); pcl::fromROSMsg(cloud_msg, *cloud);

C pcl::PointCloud<pcl::PointXYZ> cloud; pcl::fromROSMsg(*cloud_msg, cloud);

D pcl::PointCloud<pcl::PointXYZ> cloud; pcl::fromROSMsg(cloud_msg, cloud);

💡 Hint

Remember to dereference the pointer when passing the message and the cloud.

The function pcl::fromROSMsg expects a dereferenced PointCloud2 message and a reference to a PCL point cloud. Option A correctly uses pointers and dereferences.

🔧 Debug

advanced

Why does this ROS node crash when processing a point cloud?

This ROS node subscribes to a point cloud topic and tries to apply a voxel grid filter but crashes with a segmentation fault. Identify the cause.

ROS

void cloudCallback(const sensor_msgs::PointCloud2ConstPtr& cloud_msg) {
  pcl::PointCloud<pcl::PointXYZ> cloud;
  pcl::fromROSMsg(*cloud_msg, cloud);

  pcl::VoxelGrid<pcl::PointXYZ> sor;
  sor.setInputCloud(cloud.makeShared());
  sor.setLeafSize(0.1f, 0.1f, 0.1f);
  pcl::PointCloud<pcl::PointXYZ> cloud_filtered;
  sor.filter(cloud_filtered);

  // Publish cloud_filtered
}

A The pcl::VoxelGrid object is not initialized properly before use.

B The leaf size is too large, causing the filter to crash.

C The call cloud.makeShared() is invalid because cloud is not a pointer, causing a segmentation fault.

D The fromROSMsg function is called with a pointer instead of a dereferenced message.

💡 Hint

Check how makeShared() is used and what type cloud is.

makeShared() is a method of pcl::PointCloud pointers, not objects. Calling it on an object causes a crash.

❓ state_output

advanced

What is the number of points after applying this voxel grid filter?

A point cloud has 10000 points. A voxel grid filter with leaf size 0.5m is applied. The cloud covers a 5m x 5m x 5m cube. Approximately how many points remain after filtering?

A About 1000 points remain after filtering.

B About 250 points remain after filtering.

C About 10000 points remain after filtering.

D About 5000 points remain after filtering.

💡 Hint

Calculate the number of voxels in the cube and assume one point per voxel after filtering.

The cube volume is 5x5x5 = 125 m³. With 0.5m leaf size, the number of voxels is (5/0.5)^3 = 10^3 = 1000. The filter reduces points to roughly one per voxel.

🧠 Conceptual

expert

Which option best describes the role of the ROS tf library in point cloud processing?

In point cloud processing within ROS, what is the primary purpose of using the tf library?

A To convert point cloud data into 3D mesh models.

B To transform point clouds between different coordinate frames for alignment and fusion.

C To filter out noise points from the point cloud data.

D To visualize point clouds in RViz.

💡 Hint

Think about coordinate frames and how point clouds from different sensors are combined.

The tf library manages coordinate transforms, allowing point clouds from different frames to be aligned correctly.

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