CoRL 2026 · Late-Breaking Results

Prompt-to-Radar

A generative radar world model for Real2Sim2Real robot navigation

Anuvab SenSaibal Mukhopadhyay
Georgia Institute of Technology

TL;DRTrain a robot's radar perception on simulated radar from a world model, then take it back to the real robot: navigation success rises 8 points and collision runs drop four-fold.

Radar StudioA prompt (“busy intersection with pedestrians at night”, then “highway with trucks in the rain”) becomes generated scenes; each is ray-traced into simulated radar data and SSMRadNet detects objects from it. Part two runs an uploaded city drive through the same chain.
+8 ptsnavigation success in unseen corridors
4× fewerruns with a collision, same policy
+5–16 APon real RADIal data, three detectors
96 APFFT-RadNet with world-model data
Abstract

Radar sees in the dark. Learning it shouldn't need months of driving.

Radar keeps working in darkness, rain and glare, but learning radar perception needs labeled data for hard scenes that are costly to collect on a physical robot. We present Prompt-to-Radar, a generative radar world model that reconstructs real scenes from a robot’s map or video, varies obstacles and trajectories, and renders labeled simulated radar data through a configurable, ray-traced sensor model.

Adding its data improves real RADIal detection for three detector architectures by 5–16 points in AP and 9–15 points in F1. We close the Real2Sim2Real loop on a LoCoBot: with the navigation policy unchanged, a detector trained on generated plus real radar raises navigation success in unseen corridors by 8 percentage points and cuts runs with a collision four-fold. These results show that radar perception learned in a world model transfers to physical robot navigation.

Core question

Can a robot learn its radar perception inside a world model, and keep what it learned when it drives a real corridor?

Method

From a sentence to a planner input

Ray tracing runs once per scene and is cached. Every block after it runs live on every frame, with its own knobs.

Radar Studio pipeline: a text prompt or drive video goes through Sionna RT ray tracing, an RF chain with 12-bit ADC, an adaptive AFE with AdaOja tracking, and SSMRadNet detection, producing camera boxes, range-azimuth and range-Doppler maps
FigureA prompt (via video diffusion) or a real drive video sets the scene; Sionna RT, an RF chain with a 12-bit ADC and an adaptive front end produce simulated radar data, not real measurements. Every box is detected on that simulated data.

Generate

A video diffusion transformer turns a prompt into driving scenes; a drive video or robot map also works.

Simulate

Sionna RT traces every echo from geometry and radio materials; waveform, front end and ADC run on top.

Adapt

An analog combiner sends 16 antennas to 12 ADCs along a subspace tracked by AdaOja.

Perceive

SSMRadNet returns class, range, azimuth and radial velocity from ADC data.

Navigate

Detections become tracks: free space, closing speed and obstacles that persist.

Generated and real scenes

The boxes come from simulated radar, not the camera

The camera view is only for display. SSMRadNet sees simulated radar data, and its detections are projected back onto the video.

From a text prompt

“Busy intersection with pedestrians at night”

The video diffusion model generates the scene, objects are lifted into 3D, the scene is ray-traced, and SSMRadNet detects vehicles and people on the simulated radar. Night, rain and crowds cost a sentence, not a data campaign.

InputGenerated scene.
OutputBoxes from simulated radar.
From an internet drive

A 20-second drive through Kraków

Any drive video works as a scene source. Objects found in the video set up the ray-traced scene, the radar chain produces ADC data, and the detections are drawn back as 3D boxes for vehicles and poses for people.

InputUploaded drive.
OutputRadar-derived detections.
Full driveInput and detections side by side.
Late-breaking result

Real2Sim2Real on a LoCoBot

The robot's real corridors are rebuilt in the world model, SSMRadNet is trained there with exact labels, and the detector goes back on the robot with the navigation policy unchanged.

The robot

A TI IWR1443BOOST radar on a LoCoBot

76–81 GHz, three transmitters and four receivers in TDM-MIMO for 12 virtual channels, alongside 2D LiDAR, RGB-D and stereo cameras. Every sensor is recorded in sync while the navigation stack builds a live occupancy map.

SSMRadNet runs on the robot because it is about 100× lighter than the other radar detectors and fits the robot's NPU.

RealReal corridor runs, every sensor in sync.
MapOccupancy map and pose.
RadarDoppler–angle map.
Real

Collect and map

Drive the corridors, record all sensors, and build an occupancy map with pose.

Sim

Rebuild and train

Rebuild the real corridor in simulation from the robot's map, render the robot's radar along recorded and new trajectories with boxes and chairs moved, and train SSMRadNet with exact labels.

Real

Deploy and navigate

Run the trained detector on the physical robot with the same navigation policy, in unseen corridors with boxes and chairs.

Navigation · successful runs out of 100
Real only8 collision runs
87
Simulated only6 collision runs
83
Simulated + real2 collision runs
95
050100

SSMRadNet perception, 100 trials per condition in unseen corridors with boxes and chairs, identical navigation policy.

Detection · real RADIal test set
DetectorReal only
AP / F1
+ World model
AP / F1
FFT-RadNet91 / 8696 / 95+5
T-FFTRadNet85 / 8694 / 96+9
SSMRadNet78 / 8094 / 95+16

AP and F1 in %. The gain shown is in AP. Both training conditions are from this study.

Inside the radar simulator

One receive chain, from a ray-traced street to bits and boxes

Ray tracing is cached, so the same scene can be re-run with a different waveform, front end, ADC count or weight precision in seconds. Everything below is simulated radar data.

Geometry

A ray-traced street

Buildings around the Frauenkirche in central Munich come from OpenStreetMap and are built into a 3D scene that Sionna RT traces. Walls and ground carry radio-material properties, so every echo comes from real street geometry, not a statistical channel model.

The transmitter stays put while a 32×32 array moves and turns along the street; the measured beam keeps following it.

1,024elements · 5.0 mm pitch · 30 GHz band
As the array turns, the measured beam (right) follows the transmitter.
Radar image with all 1,024 elements.
32 by 32 receiver array layout
The 32×32 receiver array.
Waveform

Sensing and communication in one burst

The chain is waveform-agnostic, so the FMCW chirp can be swapped for OFDM with everything else unchanged. The first symbol is a known pattern: dividing the received symbol by it returns the echoes, whose peaks are path lengths. The remaining symbols carry 16-QAM data.

5,000 subcarriers 600 kHz apart at 30 GHz give 0.1 m path bins. Transmit drive was lowered 200× so receiver noise shows.

0 errorsin 1.575 M bits at ≈7% EVM
Symbol 1 senses the street; the rest carry data.
The street, the 16-QAM constellation, and the radar image from the same bursts.
Structure

The channel is low-rank

Converting all 1,024 elements every frame is what costs power and bandwidth. An SVD of each stored channel shows that the two strongest modes already hold most of the energy, so the analog front end combines antennas along those few modes and converts only a handful of signals.

85–93%of each frame's energy in two SVD modes
Energy captured versus SVD modes kept
Energy captured versus SVD modes kept, per frame and on average.
Munich scene with transmitter and 32 by 32 array
The scene and array those frames come from.
Tracking

Following a moving line of sight

The shortcut only helps if the tracker keeps up. The array is moved so the line of sight swings 13.6° in eight frames, and because the true subspace is known from the ray-traced channel, the tracker's error is measured exactly.

With 10 updates per frame the error stays at 0.20–0.22 over frames 1–6 and rises to 0.33 at frame 7, where the swing is fastest.

0.38 → 0.20tracking error with 10 AdaOja updates per frame
Tracking error versus frame for 5 and 10 updates per frame
Tracking error against the true subspace (lower is better).
Moving line of sight scene
The moving line of sight, frames 1–8.
Power

Power versus noise

The front end is a circuit-level model with bias knobs. With ray tracing cached, only the live chain is re-run, so each bias setting's cost shows up directly in the radar image.

Starving only the first amplifier raises the noise floor by 11.9 dB; the Friis cascade formula predicts 12.0 dB. Cutting LO drive 16× saves 59% of receiver power for 0.04 dB of contrast on one scene.

31.7 → 5.6 mWevery stage turned down, noise floor +18.5 dB
Left: full power. Right: every receiver stage turned down. Bars show power by stage.
Precision

Low-precision analog features

The analog feature extractor's weights can be cut to a few bits. With one mantissa bit (7-bit weights) image contrast drops only 0.26 dB. Binary ±1 rows that span the tracked subspace go further; signs alone fail, even with 20% more rows.

2.04 bitsper weight, image within −48 dB of full precision
Full-precision versus 1-mantissa-bit weights and image contrast versus mantissa bits
Full-precision vs. 1-mantissa-bit weights, and contrast vs. mantissa bits.
Image error versus full precision for each weight scheme
Image error vs. full precision for each weight scheme, 3 seeds each.
Adaptive front end

Fewer ADCs on a real drive video

In Radar Studio, an analog combiner turns each transmit slot's 16 antenna signals into 12 measurements, so 12 ADCs convert instead of 16. The 16 channels are reconstructed digitally for SSMRadNet, and AdaOja updates the subspace every frame.

Over the Kraków drive, detections link into consistent tracks: vehicles first, then a crowd of pedestrians late in the drive.

≈10%reconstruction error once AdaOja converges
Analog front end reconstruction error over the drive
Reconstruction error over the 20 s drive.
Range-time tracks by class
Range–time tracks by class.
Detections per frame by class
Detections per frame by class.
3.0 Mray-traced paths over 2,070 scenes, 18 GB
33–141×cheaper to re-run a frame than re-trace it
−59%receiver power for 0.04 dB of contrast
2.04 bitsper weight, binary feature extractor
Citation

BibTeX

@inproceedings{sen2026prompt2radar,
  title     = {Prompt-to-Radar: A Generative Radar World Model
               for Real2Sim2Real Robot Navigation},
  author    = {Sen, Anuvab and Mukhopadhyay, Saibal},
  booktitle = {Conference on Robot Learning (CoRL),
               Late-Breaking Results},
  year      = {2026}
}