OVRTX LiDAR runtime capture
Use ovrtx-sensor-capture to establish multi-sensor creation, selection,
stepping, iteration, and cleanup. Then use extend-ovrtx-lidar-capture for the
implementation work.
Required technical surface
- Add a documented sensor/product schema and a typed native builder/decoder for
raw returns. Probe capabilities before calling it.
- Preserve sensor path, RenderVar path, simulation ID, sample time, return ID,
coordinate frame, units, and valid/invalid status through every layer.
- Decode finite positions plus any supported range, intensity, ring/channel,
timestamp, or return index without inventing absent fields.
- Validate an isolated target with measured pose and bounds before a complex
scene. Check axis/unit conversion and first-surface behavior numerically.
- Test no-return, timeout, partial/iterator, terminal error, reset, and cleanup
paths. Run one real native capture after unit tests.
Rendered depth, RGB edges, mesh vertices, random samples, and interpolated point
clouds are diagnostics or derived approximations, never native LiDAR. Summarize
the implemented capability and exact unsupported fields; create visualization
or report artifacts only when requested.
1---2name: ovrtx-lidar-runtime-capture3description: Develop and validate a native OVRTX LiDAR capture path in the public add-on, including sensor/product identity, typed raw-return decoding, timing, coordinate frames, and truthfulness gates. Use when developers customize the add-on for LiDAR. The current multi-sensor LdrColor probe validates routing only and must not be presented as LiDAR output.4---56# OVRTX LiDAR runtime capture78Use `ovrtx-sensor-capture` to establish multi-sensor creation, selection,9stepping, iteration, and cleanup. Then use `extend-ovrtx-lidar-capture` for the10implementation work.1112## Required technical surface13141. Add a documented sensor/product schema and a typed native builder/decoder for15 raw returns. Probe capabilities before calling it.162. Preserve sensor path, RenderVar path, simulation ID, sample time, return ID,17 coordinate frame, units, and valid/invalid status through every layer.183. Decode finite positions plus any supported range, intensity, ring/channel,19 timestamp, or return index without inventing absent fields.204. Validate an isolated target with measured pose and bounds before a complex21 scene. Check axis/unit conversion and first-surface behavior numerically.225. Test no-return, timeout, partial/iterator, terminal error, reset, and cleanup23 paths. Run one real native capture after unit tests.2425Rendered depth, RGB edges, mesh vertices, random samples, and interpolated point26clouds are diagnostics or derived approximations, never native LiDAR. Summarize27the implemented capability and exact unsupported fields; create visualization28or report artifacts only when requested.
NVIDIA-Omniverse