Repository navigation
Terminology and Evidence
ArduPlaneTools reports what its input files support and identifies important gaps. These common terms help distinguish a recorded fact from the interpretation built around it.
| Term | Meaning in APT |
|---|---|
| Recorded evidence | A retained log message, field, parameter value or state used by an analysis. A record describes what the logger captured; it may be sampled after the physical or firmware transition that caused it. |
| Interpretation | A bounded conclusion produced by applying the module's documented detection and ownership rules to recorded evidence. It should not be read as a direct physical measurement unless the source supports that claim. |
| Measured value | A supported sensor or telemetry observation, such as logged voltage or receiver-reported RSSI. Its accuracy and timing still depend on the source sensor and logging path. |
| Logged value | Any value retained in the input record. It may be a sensor estimate, firmware state, command, configured parameter or repeated telemetry value; “logged” does not automatically mean independently measured. |
| Commanded value | A firmware command or PWM output recorded in the log. It is not proof of physical actuator movement, motor rotation or thrust. |
| Unavailable | The required evidence was absent, invalid, outside the supported interval or not sufficiently aligned. APT does not convert unavailable evidence to zero or silently estimate it. |
| Censored / incomplete | Observation ended at a boundary such as a mode exit or end of log before the expected completion or recovery evidence appeared. APT retains the bounded evidence without inventing the missing endpoint. |
Flight window is one detected armed-flight interval used to scope analysis. A BIN may contain several flight windows, and evidence outside a window is not automatically assigned to it.
Analysis attempt is a module-specific interval extracted inside the relevant evidence scope. Examples include a landing attempt, a deliberate slow-flight attempt or a TAKEOFF-mode execution. One flight can contain several attempts, and an attempt is not the same thing as the whole flight.
Event ownership means that a message or sample belongs to the applicable flight, mode execution or attempt under the detector's chronological rules. A nearby timestamp alone does not guarantee ownership.
Boundary evidence is the logged observation used to start, end or censor an interval. Logging cadence means the observed boundary may differ from the exact internal or physical transition time.
Firmware event or state describes what ArduPlane reported, accepted or commanded. For example, a TAKEOFF Triggered AUTO message is firmware launch-acceptance evidence; it does not prove hand release or liftoff.
Completion evidence is the specific transition required by the analysis. A mode exit is not promoted to TAKEOFF control completion, and a GPS stop is not automatically physical touchdown.
Probable demand-opposed attitude departure is the Stall Analysis classification for the required sequence in which logged attitude stops following continuing nose-up FBWA demand. It is evidence of an attitude departure under that model, not confirmation of an aerodynamic stall.
Ambiguous attempt is a real manoeuvre that lacks complete or consistent decisive evidence. No demonstrated departure means the usable attempt did not demonstrate the required signature; it does not establish a safe speed.
Recovery observation records supported changes in attitude, airspeed, demand, mode or commanded power after an event. A control input or mode switch alone does not guarantee that stable flight was restored.
Aircraft-side RC failsafe evidence comes from the ArduPlane BIN. Radio Link uses sampled RC-input validity, failsafe messages, mode changes and clearing evidence to identify episodes and aircraft response.
RF measurement is a supported transmitter-side or receiver-reported metric such as EdgeTX 1RSS, RQly or RSNR. These values do not establish the exact aircraft failsafe boundary unless pairing, alignment and telemetry age are sufficiently supported.
Sampled invalid span is the interval between logged invalid and revalidated RC-input observations. It is not the exact physical RF-loss duration.
Pairing asks whether a BIN and CSV belong to the same session. Alignment estimates the relationship between their timelines. Manual CSV selection permits analysis but does not prove pairing; pairing alone does not guarantee sufficiently precise alignment for episode-specific RF values.
Telemetry unavailable means no usable RF observation was present. Zero-filled placeholders are excluded rather than treated as poor signal. Repeated values can be held between telemetry updates and are not necessarily independent RF measurements.
Observed-time coverage is the portion of a Range-Walk section represented by usable observations. It does not prove RF refresh freshness or continuous receiver reception.
Parameter history is the sequence of logged parameter values applicable at different times. Where supported, APT uses the value applicable to the event rather than assuming one value for the whole log.
Provenance identifies where evidence came from, such as aircraft BIN, transmitter CSV, a configured parameter or operator-entered Range-Walk metadata. Sources are kept distinct so one does not silently stand in for another.
Log fingerprint is the SHA-256 content identity used by Battery Pack Management. Identical copies of the same BIN share the same fingerprint even if their filenames differ.
The in-app Docs window contains a focused glossary for each module. Source copies are available with the project:
Getting started
Battery & packs
Flight analysis
Radio & diagnostics
Reference