Common Concepts

Configure a sensor prim, request outputs through a RenderProduct, step the renderer and map the results. Your First Lidar Sensor walks through this sequence; camera users can start with Cameras.

These concepts apply across models except where stated; partial-output policies differ by model.

What each page covers

• Sensor Configuration — prims, applied schemas, identity and timing attributes.

• Output Configuration — RenderProducts, RenderVars, channels and renderer options.

• Sensor Outputs — tensors, params, counts, validity, mapping and lifetime.

• Sensor Scheduling — capture rates, stepping and partial-output delivery.

• Sensor Definition Validation — check a definition before rendering, through C++ or Python.

• Runtime Parameter Updates — live edits, fixed parameters and rejected updates.

• Sensor Configuration
• Output Configuration
• Sensor Outputs
• Sensor Scheduling
• Sensor Definition Validation
• Runtime Parameter Updates

Related

• Your First Lidar Sensor — the worked walk-through that applies these concepts to one sensor, from prim to consumed output.

• Overview — what ovrtx sensors are for, the modalities, and how this documentation is organized.

• Cameras — camera output straight from the renderer: attributes, render modes, outputs and the camera how-tos.

• Visual Sensors — the Camera generic core model and the Camera single-view stereo depth model.

• Non-Visual Sensors — the lidar, radar and acoustic models.

• Reference — the generated schema tables, the composite output types and the glossary.

• Troubleshooting — the symptom index and the by-design limitations.