Every packet tells
a part of the story.
Record an unordered stream. Reconstruct the mission. Surface the faults that disappear between individual samples.
Watch the mission unfold
Scrub through source telemetry. Select a vehicle or jump directly to a finding.
Positions come from source CSV samples, including packets rejected by processing policy. Lines connect observations; positions are held at the last sample without interpolation.
Fault timeline
Click a one-second interval to inspect its findings. Times refer to event time.
Inspect the evidence
Findings below come directly from the C++ replay engine's JSON output.
| Event time | Vehicle / seq | Rule | Evidence |
|---|
Same log. Same rules. Same findings.
The binary recorder stores its rule configuration with the telemetry. Replay restores those rules, resolves bounded out-of-order arrival, and evaluates the same per-vehicle state machines. Strict mode rejects damaged logs; salvage mode exposes only the verified prefix.
CRC detects accidental corruption. Stream flushing is not an fsync durability guarantee. This is a simulation engineering toolkit, not certified flight software.
Local processor benchmark
Run make benchmark to record local performance.
View all raw measurements ↗