Reading Sensor PointClouds

When to Use

Use this skill when the user asks how to access PointCloud output data, map Coordinates, Counts, Intensity, RCS, RadialVelocityMs, or TimeOffsetNs tensors, slice valid entries, or move sensor point clouds through CPU/CUDA memory. Use an interpreting pointcloud skill instead when the tensors are already available and the question is what their channels mean.

Inputs

Resolve inputs in this order: existing repository files and referenced snippets, explicit user request, then broader agent context.

• Target API surface: Python, C/C++, or both.
• Sensor modality, RenderProduct path, PointCloud RenderVar/output name, and requested tensor channels.
• Mapping target: CPU, linear CUDA memory, or host copy after map.
• Valid-entry handling: Counts, Flags, desired slice/copy behavior, and whether data must outlive the mapping.
• Repository source snippets referenced below. Treat these snippets as the API source of truth.

Prerequisites