ROS2 Point Cloud Penalty

Hard Performance Debug 0% pass rate
#qos#keep-all#latency#pointcloud#lidar#dds#performance-debug

Practice the ROS2 Point Cloud Penalty coding problem in Performance Debug. Browser-based execution with automated grading — no local ROS install required. 0% of engineers pass this challenge.

Performance Bug

LiDAR processing pipeline end-to-end latency: 450ms. Acceptable maximum: 100ms.

Symptoms

  • Pipeline: lidar_driver → /pointcloud → pointcloud_processor → /processed
  • Driver publishes at 20Hz; processor takes 60ms per frame
  • Latency climbs steadily over time: 200ms → 500ms → 1000ms+
  • CPU during processing: normal
  • No error messages

What you know

  • Both nodes run in the same process
  • Publisher sends a new frame every 50ms
  • Each frame takes 60ms to process
  • Latency is measured from message timestamp to processing completion

What you don't know

  • Why latency keeps growing instead of stabilizing
  • What configuration change would make the processor always work on the freshest data

Your task

Fix the QoS configuration so the processor always handles the latest point cloud, keeping latency below 200ms.

Performance Debug format: The system runs but at wrong speed. Find and fix the bottleneck.

Frequently asked questions

What is the ROS2 Point Cloud Penalty practice problem?

It is a hands-on Performance Debug challenge on SimuCode where you implement and run ROS2 code in the browser with runtime-verified tests.

How do I practice ROS2 Point Cloud Penalty online?

Open this page, sign in, and solve the problem in the built-in IDE. Your solution is graded against real ROS2 execution checks.

What skills does ROS2 Point Cloud Penalty test?

This Hard problem focuses on qos, keep-all, latency skills used in robotics interviews and production systems.