Home' RTCA Documents for Review : Guidelines for In Situ Eddy Dissipation Rate Contents 12
© 2017, RTCA, Inc.
The EDR algorithm, as defined in this context, also does not include the method whereby
the calculated EDR data, or data used for the EDR calculation (if the calculation is done
on the ground) is transmitted to the ground processor, as this is dependent upon the aircraft,
airlines, and communications provider. In addition, definition of different downlink rates,
data formats, and “bundling” of reports to conserve communications costs are not within
the defined processor system, as each airline will have unique requirements.
Because of the need to be practical, the EDR algorithm test procedures are specific to a
single aircraft type flying at a specific flight condition. The testing is to be conducted in a
pseudo-operational environment (i.e., not in an operational/in-flight environment). It is
assumed that any changes made by the developer in order to properly adhere to the stated
test requirements to execute the test implementation do not significantly improve the
algorithm performance with respect to the benchmark statistics used in this validation
process, and thus verifies operational comparability.
Developers are responsible for ensuring the operational implementation of their algorithm
performs correctly; for example, that it uses the correct input data sources, that there is low
sensor noise, that it is properly tuned for the deployed platform, and that the data is of
expected quality. This guidelines document does not attempt to validate in-flight
performance. It is thus assumed that fulfillment of these responsibilities in conjunction
with demonstrating compliance with the validation protocol will establish operational
Because of the dynamic nature of the atmosphere and the complicated aircraft response
process (e.g., different airframes, weight classes, dynamic performance, system set-up
(input rates, etc.)), the algorithm performance requirements presented in this document
assume the following: controls-fixed straight and level flight (i.e., no autopilot), a single
operating condition (i.e., representative cruise), isotropic winds (i.e., the same statistical
properties along the vertical and horizontal axis), and an aircraft simulation based on a
single aircraft system at an 8 hertz (Hz) sampling frequency.
It is therefore assumed that demonstrating comparability of EDR algorithms using the
validation procedure (and thus on the specific datasets contained therein) will ensure
operational comparability of the EDR algorithms in most, if not all, operational contexts.
For example, there are normal conditions under which operational comparability may not
be achievable; these could include times when the aircraft is performing maneuvers such
as banking. Some form of quality control (QC) based on these conditions may be
The goal of the validation test procedures laid out in this document is to ensure the
“operational comparability” of the output values of EDR algorithms. Therefore, any tests
specified within this document are associated with the EDR algorithm itself and the
Links Archive Addressing Human Factors/Pilot Interface Issues Navigation Previous Page Next Page