Expand description
Two recordings of one synthetic flight, and a logger in each stage of a staged one: the check
of hpr_flightdata::timeline’s clock offset (two recordings, in the plan for the readings).
What it is for. A flight’s truth says how each logger’s clock stood against launch, so the
offset two logs’ liftoffs recover can be held to the true one. Each flight here carries two
loggers, drawn independently from the ranges LoggerDraw::draw states, with their noise on
streams of their own, each clock’s zero moved by up to MAX_CLOCK_S either way, as a board’s
is by when it was switched on. The offset’s bound must hold on every flight, and its 90%
interval must pass ADR-257 §1’s test on Set::PairA and Set::PairB with its
shares fitted on Set::PairCalibration, each on a seed of its own.
Stages (Staged) fly validation/designs/synthetic-two-stage-75mm-54mm.json, handed in
by the caller, as the designs are (super::designs), with a logger in each stage. The
booster’s truth after the split is HPR Sim’s point-mass descent on the truth’s grid, from the
integrator’s dense output (docs/physics/staging.md), so the check says how well two stages’ liftoffs line their
clocks up, not how well a booster’s fall is modeled.
How far to trust it. Two boards here share a flight and differ only in noise, rate and step. Real boards also sit at different stations, and may see the pad’s shock differently; the one real pair checked, RocketPy’s Prometheus, is on the guide’s page.
Structs§
- Check
- One set’s check of the offset.
- Pair
Cell - How one pair of logger families’ offsets did.
- Said
- What a flight’s two logs said of the clock offset.
- Staged
- The two-stage design’s flights.
- TwoLogs
- Two logs of one flight, each on its own clock.
Constants§
- MAX_
CLOCK_ S - The most a logger’s clock zero is moved from where its log starts, s, either way: about five minutes on the pad, as a board switched on before the rocket went out to the rail is.