This is an old revision of the document!


QC2h-1: Plumatic Controls

The algorithm first checks prioritet 2, 3, and 4 from the specification and applies the correpsonding flag modifications. After that, the sliding aggregation check is performed, excluding any periods with data matching discarded_*flags.

Beyond the standard configuration options detailed in the user guide, the following options are available for Plumatic.

  • highsingle_flagchange (default: fs=8,fmis=2) specifies which flags have to be set if a “high single” is detected (prioritet 2 in qc2h1)
  • highstart_flagchange (default: fs=8,fmis=2) specifies which flags have to be set if a “high start” is detected (prioritet 3 in qc2h1)
  • interruptedrain_flagchange (default: fs=8,fmis=2) specifies which flags have to be set if a “rain interruption” is detected (prioritet 4 in qc2h1)
  • aggregation_flagchange (default: fr=9) specifies which flags have to be set if a sliding aggregation exceeds a threshold (prioritet 1 in qc2h1)
  • discarded_cflags (default: fr=9|fs=8|fmis=2) and discarded_uflags(default: no constraint) specify which rows shall be regarded as “bad” and excluded from further tests
  • stations (no default) resolutions and station ids
  • sliding_alarms (no default) periods (in mutes) and precipitation thresholds
This website uses cookies. By using the website, you agree with storing cookies on your computer. Also you acknowledge that you have read and understand our Privacy Policy. If you do not agree leave the website.More information about cookies
  • kvalobs/kvoss/system/qc2/requirements/algorithms/plumatic.1323346658.txt.gz
  • Last modified: 2022-05-31 09:23:18
  • (external edit)