Differences

This shows you the differences between two versions of the page.

--- kvalobs:kvoss:system:qc2:requirements:algorithms:rarr_24 [2011-12-09 09:13:26]
alexanderb Correct documented default for update_flagchange
+++ kvalobs:kvoss:system:qc2:requirements:algorithms:rarr_24 [2022-05-31 09:29:32] (current)
@@ Line 13: / Line 13: @@
 The calculated RR_24 updates the corrected value in the kvalobs database.
+A warning is given if fmis=0 and original!=-1.
 ==== Configuration and Parameters ====
@@ Line 21: / Line 23: @@
 ^ Option ^ Default ^ Description ^
-| endpoint_cflags | fmis=4&fd=2    | specify the flags for accumulation endpoints. Endpoints not matching these flags will not be detected |
+| endpoint_cflags | fmis=[04]&fd=2&fhqc=0    | specify the flags for accumulation endpoints. Endpoints not matching these flags will not be detected |
 | endpoint_uflags | no constraints | ::: |
 | missingpoint_cflags | fmis=3&fd=2 | specify the flags for the missing points before the accumulation |
@@ Line 34: / Line 36: @@
 | measurement_hour | 6 | specifies the hour at which the data are expected. Series containing data with other times  will be rejected with a warning. |
 | min_neighbors | 1 | specifies the minimum number of neighbor stations with good data |
-| days_before_no_neighbor_warning | 28 | specifies the number of days after which a WARN is written to the logfile if there are not enough neighbor data |
+| max_neighbors | 5 | specifies the maximum number of neighbor stations to use |
+| InterpolationDistance | 100 | radius in km inside which to search neighbor stations |
+| warning_distance_closest_neighbor | 50 | minimum neighbor distance to print an INFO message about not so good neighbors |
+| days_before_no_neighbor_warning | 14 | specifies the number of days after which a WARN is written to the logfile if there are not enough neighbor data |
+| days_before_redistributing_zeroes_warning | 14 | specifies the number of days after which a WARN is written to the logfile if a non-dry accumulation has only dry neighbors |
 ==== Parameters ====
 This algorithm has only been tested for paramid 110.
+==== Log Messages ====
+There might be many different WARN messages in the log file ''/var/log/kvalobs/kvqc2d.log'' from this algorithm. These messages are (as of version 1.3.14pre3):
+  * ''original = missing/rejected for endpoint'' -- an endpoint (i.e. a row matching ''endpoint_?flags'') has a missing original value; this might also indicate a row which somehow obtained the same flags as an endpoint.
+  * ''fmis=0 and original!=-1 for endpoint'' -- fmis should only be 0 for dry accumulations [[kvalobs:kvalobs-flagg#manglende_observasjon_missing|flagg-spec]]
+  * ''fd=2 and original!=corrected for endpoint'' -- redistribution has apparently been performed without setting fd=7
+  * ''endpoint matches warn_and_stop_flags'' or ''missing point ... matches warn_and_stop_flags for accumulation'' -- a row matches ''warn_and_stop_?flags'', which is ''never'' by default
+  * ''missing point ... has different fd flag than endpoint'' -- a redistribution seems to have been done without setting fd flags consistenly
+  * ''missing point ... has fmis!=3 while fd=2 for endpoint'' -- normally, all missing rows (if they exist) should have fmis=3 before redistribution
+  * ''missing point ... has fmis!=1 while fd=7 for endpoint'' -- normally, all missing rows should have fmis=1 after redistribution
+  * ''found ... but expected ... rows with corrected values for accumulation ...'' -- normally, only one row should have a corrected value if the endpoint has fd=2, and all rows if fd=6/7
+  * ''redistributed sum ... starting ... differs from original in endpoint ...'' -- the sum of corrected values in the accumulation period does not match the original value in the endpoint row; unless fhqc!=0, an attempt will be made to fix this automatically
+  * ''fhqc mess for accumulation from .. to endpoint ...'' -- some rows in the accumulation period have fhqc=0, while others have fhqc!=0
+  * ''suspicious row ... before endpoint ..; giving up'' -- a row with missing original value has been found before the assumed accumulation period; to avoid a wrong redistribution in case the correct start date for the accumulation has not been detected, the algorithm stops
+  * ''no really good neighbors at obstime ... for accumulation ending ...'' -- the nearest neighbor is quite far away (more than ''warning_distance_closest_neighbor'')
+  * ''accumulation ... > 0 would be redistributed to zeros for endpoint ...'' -- there is non-zero accumulated precipitation, but all accessible neighbor stations are dry so that the redistribution cannot be performed
+  * ''could not avoid difference of ... between distributed sum and accumulated value at endpoint ...'' -- some precipitation has been lost due to numerical (rounding) problems