pub fn airframe_not_as_written(file: &OrkFile) -> Option<String>Expand description
Why the rocket in file was not read exactly as written, or None if it was. A rocket read
otherwise flies in none of its configurations, whatever its motors (ADR-055, the
rule for which configurations fly), so a program that puts a motor of its own into a
configuration design left out, as hpr sim --motor does, asks this first: a
configuration’s LeftOut names only the first reason on NotFlown’s list, and a missing
curve comes before the airframe.