pub fn find_cut(log: &FlightLog) -> Option<Cut>Expand description
Where the boost’s log is cut, decided at each sample of the height track from it and the ones
before it (the module’s rules); None where the log holds no height track, its track is a GNSS
receiver’s, any SPEED_WINDOW_S of it holds more samples than the analyzer’s fastest rate
allows (readings::MIN_INTERVAL_S), it never lifts off or climbs too slowly (STILL_M_S), it never holds
readings::SPEED_MIN_SAMPLES in a SPEED_WINDOW_S window (a log slower than 8 Hz, or one
whose samples can’t be read), its
fitted speed reaches
readings::TRANSONIC_SPEED_M_S before the cut, or it never slows by DROP_SHARE of its
top speed and DROP_FLOOR_M_S for HOLD_S, at a speed the lowest of the last HOLD_S.
The cut stands where the window’s line is more than LIFTOFF_RISE_M above the pad’s:
three bad samples side by side on the pad can lift the line past that for a sample, and the
speed then falls back as it does at burnout. The pad is read again wherever the line stands
still (STILL_M_S), dropping the top speed and fall read before, so a pad spike faster than
the flight’s own top, or a step up on the pad that stays, doesn’t stay the top
(#1362), unless it comes too close to ignition for the line to stand still between
it and the climb (#1441).
A GNSS receiver’s altitude in the boost can drop out at ignition and burnout and lag the climb, by up to 440 m in one flight a flyer reports, while its fix reads valid (GNSS in boost): on set A’s first 60 synthetic flights such tracks were cut up to 11 s after burnout or not at all (a sweep run once, with an earlier rule’s 1 s hold in the cut). A staged flight is cut at the first burnout whose coast lasts long enough for that fall; untested on one.