Build a Profile from a Spec Sheet#

Build a Radar generic wpmDmat model profile by separating published values, derived values and parameters that need calibration. The lidar profiling guide explains this method; Choose Parameter Values maps radar specifications to attributes.

Before you start. Review the model, attributes, parameter mapping and scan authoring before building a profile.

Profiling workflow#

Start with published specifications, retain defaults for unavailable values, and record each value’s source. Validate the profile against recordings or controlled scenes. See the lidar profiling guide for the shared method.

Build the profile in this order:

  1. List the device’s operating modes. A radar datasheet usually describes several: a near and a far scan, a short-range and a long-range mode, a wide and a narrow field of view. Each mode has its own maximum range, field of view, resolution and waveform, and often its own cycle time. Write them down separately.

  2. Author one scan configuration per mode. The first scan, s001, comes with the model’s schema; every further mode is one more instance of the scan schema, s002 and upward. Run More Than One Scan Pattern covers the authoring.

  3. Transfer the datasheet values of each mode into its scan, and stay inside that mode. The table on Choose Parameter Values says which attribute takes which field.

  4. Fill the shared identification and rate attributes on the prim: the output rate, the start offset and the identification strings. The next section says what goes where.

  5. Leave calibration-dependent values at their defaults and mark them. Record which values you copied, which you derived and which are defaults waiting for a measurement; the four source-confidence categories the lidar tutorials use (Source confidence) serve a radar profile just as well.

  6. Compare authored limits with the output parameters using Choose Parameter Values, then run the seven checks in Validate a Parameterization.

Parameter sources#

Keep each scan’s values within one operating mode. Multiple scans share the authored frame rate and run in sequence.

Author identification, rate and start offset with the shared sensor attributes. See radar defaults and scan-rate behavior.

Map the remaining specifications using the datasheet table. Check which controls apply to the selected processing mode. Label default values that still need calibration or simulation tuning.

Verification#

Run Sensor Definition Validation to check the layer before rendering. Then compare authored scan limits with output parameters using the configuration check.

Use targets at known ranges and angles to verify coverage and coordinates. Check material labels, scan order and motion against the intended behavior. Scene motion requires an active motion BVH (AUTO or ENABLE); see Simulate Moving Targets for setup and behavior when disabled. Follow the seven scenarios in Validate a Parameterization.

Potential issues#

If a published field has no corresponding attribute, it may describe calibration data, processing firmware or proprietary post-processing that the model does not simulate: a tracked object list, a vendor’s clutter suppression, a per-unit antenna calibration. Record the gap as a labeled default rather than using an unrelated attribute. See unmapped specifications.

Check units. maxAzAngDeg and maxElAngDeg take half-angles, not the full field of view; Half-angles shows how to catch the mistake. waveLengthMm is in millimeters (about 3.9 for a 77 GHz radar), and WAVEFORM processing derives the carrier frequency from it. The chirp duration and chirpRepetitionTimeSequence entries are in seconds and the chirp bandwidth in hertz, not in microseconds and megahertz. omni:sensor:frameRate is the rational pair (20, 1), not the plain number 20.