pub fn separated_part_issue_warnings(
result: &FlightResult,
max_mach: Option<Peak>,
) -> Vec<IssueWarning>Expand description
The separated parts’ issues a flight meets (ADR-200), read from the bodies that
flew on their own (FlightResult::bodies), whatever the rocket’s drag: each part’s descent
is a point under its open devices (crate::recovery), never the rocket’s drag.
- #179 when a body aft of a stage boundary flew on its own: a booster dropped at a separation, or a parallel stage. Its first stage is past the nose’s (stage 0), whatever devices it carries; the error is unsized, so no speed at the split is excluded.
- #354 when a body started its own flight with no drag area open (zero, or not a
number, so a broken one can’t hide it), and no device opened at that same instant (an event
at its start time, as a device fired by the split with no lag is): it flies with no drag
until its first device opens. A canopy that fills from nothing (a fill time) opened on the
stack at the split also starts at zero, so it warns too: an over-warning, on the safe side.
The flight refuses such a part while it climbs through a fired device’s lag, and refuses one
that lands with nothing open (
crate::recovery), so what is left is mostly a part already falling.
Each warns once, whatever the number of bodies that meet it, and only for a flight with a top
Mach number (max_mach), as the others.