From arrays to a sequence of events

A sensor frame, a controller output, and an applied mirror command are different events. Their ordering depends on exposure time, data availability, clock alignment, and actuator delay. A nominal frame rate cannot fill in missing timestamps.

Noether Replay reads the Adaptive Optics Telemetry (AOT) format, preserves available metadata, and checks whether the recording supports a consistent sequence. Calibration epochs are assigned only when they cover the complete exposure and its timing uncertainty.

What the software checks

  • Event order: exposure, observation availability, controller completion, command issue, and actuator effect.
  • Command provenance: which observation produced a command, and whether the record establishes that it was physically applied.
  • Calibration: validity intervals, ambiguous epochs, and observations outside a calibration’s lifetime.
  • Evidence integrity: exact array bytes, shapes, units, timing, and source metadata bound to the analysis.
  • Noise conditioning: propagation of temporal and cross-channel covariance through filtered observation windows.

Inspectable examples

ExampleWhat it establishes
Synthetic event reconstruction72 known events, an omitted frame identifier, and four observations outside calibration validity.
Public PAPYRUS telemetry ↗Three 200-sample arrays imported. Missing event times prevent inference of an exact physical event sequence.
Correlated-noise example ↗In the declared synthetic AR(1) case, ignoring temporal correlation understates variance after averaging by 44.44%.

Shadow policies can produce hypothetical commands from recorded observations. The measured outcomes still belong to the controller that generated the recording; they are not assigned to the shadow policy.

Why it matters for autonomy

Controller qualification starts with trustworthy measurements. Before testing a replacement policy, a team needs to know which commands reached the instrument, which calibration was valid, and whether a timing claim is supported by the record.

Noether Replay provides that offline foundation. It does not drive hardware, certify an instrument, or use a recording as proof of a different controller’s performance.

Code and data