A twin is a simulation of a sensor, or of a whole mission, built from the same checked physics as the firmware. It is used to design the readout and calibration before hardware exists, and to check every built unit against.
They show that the method holds up on hard, published work. On three of the four, the checks found misprints or wording errors in the sources.
The 4.5PN inspiral phase of a compact binary, the template detectors use. Blanchet, Faye, Henry, Larrouturou & Trestini, PRL 131, 121402, 2023.
The Event Horizon Telescope GRMHD code comparison, a torus around a spinning black hole. Porth et al., ApJS 243, 26, 2019.
Navier–Stokes in four space dimensions, compared with Berera, Ho & Clark 2020 and Ho et al. 2025.
The relativistic clock correction, on 7 days of real satellite data: 2,826 broadcast messages, 562,966 clock points, GPS week 2431.
A partner brings their sensor and the place it is going: a ship in a given sea state, a vehicle on rough ground, a survey site, an orbit. We build the twin of that sensor in those conditions and run it before anyone travels, so the field trial starts with known weak points instead of discovering them.
The twin is written in the same checked equations as the device firmware, so the simulation and the instrument cannot quietly drift apart. A wrong unit, sign or law is refused before the twin runs.
The method has reproduced published results before it is used on a partner’s sensor: four published papers above, and commercial atom-interferometer instruments below.
Expected performance in their conditions, the points where the sensor fails, and what to change, before the cost of a field trial. Become a pilot partner →
43.9a gradiometer, against a published ~40 E/√Hz
449a gravimeter, against a published 500 nm/s²/√Hz
1,408whole 24-hour navigation missions simulated
How it ran. Everything ran on a single laptop. The black-hole solver and the 4D forced runs are hand-written code with their physics checked by Phy.