Chirp-radar baseline

Purpose

Create a compact, editable synthetic radar dataset with one LFM-chirp emitter per record. This path is for a radar-oriented downstream experiment, not a general survey of radar operating conditions.

Audience and prerequisites

Use it after the Quickstart when you need chirp records instead of communication-modulation labels. Install the required propagation extra with uv pip install -e '.[sionna]'.

Inputs

The shipped YAML fixes the sample rate, duration, scene bandwidth, seed, record count, one-emitter density, and the emitter parameters through emitter_zoo.families[].params. Each record contains an up-sweeping LFM chirp with a 200 kHz chirp bandwidth, 20 microsecond pulse duration, and a complete post-pulse gate before the selected Sionna TDL channel. The template fixes a 9.6 GHz carrier, static typed TX/RX poses, 20 dBm TX power, and applies TDL-A per emitter. The waveform is created with scipy.signal.chirp, then composed into complex IQ; provenance records that implementation. TDL-A is a 3GPP link-level fading profile; its model boundary and source traceability are documented in the local TR 38.901 propagation reference. Materializing the YAML gives you a starting configuration to copy and adapt.

Run

rfgen init chirp-radar ./chirp-config
cd ./chirp-config
rfgen validate --config-dir .
rfgen generate --config-dir .
rfgen inspect ./rfgen-output

Observable output and interpretation

The command publishes a local Signal Dataset snapshot at ./chirp-config/rfgen-output. Each record contains IQ, a radar-family label, and provenance describing the configured synthetic scene and sionna-tdl model. The clean emitter has a post-pulse gate; after fading, received samples are not expected to preserve that clean-waveform shape. This is a controlled chirp-under-fading workflow, not a site-specific radar propagation claim. TDL-A is a one-way link-fading model: it does not model a target, range-dependent round-trip delay, radar cross section, or target Doppler. For coupled target returns with round-trip delay, Doppler, and radar cross section, use the separate radar-response path: Generate a coupled radar dataset.

Verification boundary

This path is qualified only for the shipped template and pinned CPU environment: 24 records, radar label/storage readability, finite propagated IQ, persisted TDL-A provenance and receiver profile, inspection, and record-level repeats whose ground truth is exact and whose waveform is equal within the tolerance the path declares (zero for this path, which contains no environment-bound solver). It does not establish radar detection performance, site-specific propagation realism, or coverage of radar hardware and waveforms.

Customize safely

Work from a copy of config.yaml, validate it before generation, and use a new output location for every changed configuration. Read Scenes and Labels before interpreting a modified experiment.