Welcome to the NOAA Institutional Repository | The use of complex quality control for the detection and correction of rough errors in rawinsonde heights and temperatures, a new algorithm at NCEP/EMC - :11422 | National Weather Service (NWS)
Stacks Logo
Advanced Search
Select up to three search categories and corresponding keywords using the fields to the right. Refer to the Help section for more detailed instructions.
 
 
Help
Clear All Simple Search
Advanced Search
The use of complex quality control for the detection and correction of rough errors in rawinsonde heights and temperatures, a new algorithm at NCEP/EMC
  • Published Date:
    1997
Filetype[PDF - 2.81 MB]


Details:
  • Personal Authors:
  • Corporate Authors:
    National Centers for Environmental Prediction (U.S.)
  • Series:
    Office note (National Centers for Environmental Prediction (U.S.)) ; 419
  • Document Type:
  • Description:
    Complex quality control (cqc) was a new concept when introduced to NCEP by Lev Gandin in the late 1980's. The basic idea is that no decisions are to be made on data quality until the results from all checks, in numerical form, are available. In addition, data are to be corrected when possible. Since Lev's arrival at NCEP, the author has worked with him to introduce cqc for the quality control of rawinsonde heights and temperatures and Doppler profiler winds. The principles were also used in the quality control of many other data types.This note describes the code that resulted from rethinking the strategy for rawinsonde heights and temperatures. The mandatory and significant levels are now treated together, rather than first all the mandatory levels, and then the significant levels. The data are considered, one level at a time, from the ground upward. There is also a greater opportunity for complex errors to be corrected since, whenever an error is corrected, then all residuals are recalculated and computations begin anew from the lowest level. Only after all possibly correctable errors are considered are observational errors looked for.The note begins with a general consideration of errors, then turns to methods of error detection and correction. The detail becomes higher as the code specifics are described. Sample output from the code is described, examples are given, and statistical results of use of the code are presented.

  • Supporting Files:
    No Additional Files