LDAP: couldn't connect to LDAP server
Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
|
kvalobs:kvoss:system:qc2:requirements:algorithms:mist [2009-12-06 19:17:18] paule |
kvalobs:kvoss:system:qc2:requirements:algorithms:mist [2022-05-31 09:29:32] (current) |
||
|---|---|---|---|
| Line 13: | Line 13: | ||
| - Update the correcte dvalue following the rules below: | - Update the correcte dvalue following the rules below: | ||
| - | //If an existing corrected value exists and it was generated by HQC// | + | |
| * do not update, leave correction from HQC | * do not update, leave correction from HQC | ||
| - | //If an existing corrected value exists and not from HQC:// | + | |
| * check if existing value: | * check if existing value: | ||
| * if FALSE update corrected with T1 | * if FALSE update corrected with T1 | ||
| - | //If no corrected value exists:// | + | |
| * update corrected value with T1 | * update corrected value with T1 | ||
| Line 31: | Line 31: | ||
| ==== Quality Control Level ==== | ==== Quality Control Level ==== | ||
| - | * ... | + | * Non-real time (Qc2) |
| Line 38: | Line 38: | ||
| It shall be possible to run the algorithm for | It shall be possible to run the algorithm for | ||
| - | * ... | + | * Any arbitrary time range. |
| - | * ... | + | * In automatic mode for ann arbitrary sliding time window (e.g. the last N days from today). |
| - | * ... | + | * The algorithm is specific to hour temperature measurements. |
| ==== Characteristics of the data to which the method is applied ==== | ==== Characteristics of the data to which the method is applied ==== | ||
| Line 46: | Line 46: | ||
| __CONTROLINFO AND/OR USEINFO__ | __CONTROLINFO AND/OR USEINFO__ | ||
| - | * ... | + | * The trigger for the method is the identification of a missing original value (i.e. -32767). |
| __TYPEID, PARAMIDS, OTHER METADATA__ | __TYPEID, PARAMIDS, OTHER METADATA__ | ||
| - | * ... | + | * Paramid=211 |
| + | |||
| + | Note: The MinT and MaxT data are located in the paramids 213 and 215 respectively, | ||
| ==== Flag Settings ==== | ==== Flag Settings ==== | ||
| Line 56: | Line 59: | ||
| __SPECIFICATION OF CONTROLFLAGS TO BE SET FOR EXPECTED RESULTS OF THE ALGORITHM, I.E. CONSIDER BOTH POSITIVE AND NEGATIVE RESULTS__ | __SPECIFICATION OF CONTROLFLAGS TO BE SET FOR EXPECTED RESULTS OF THE ALGORITHM, I.E. CONSIDER BOTH POSITIVE AND NEGATIVE RESULTS__ | ||
| - | | + | Follow the standard defined in the original kvalobs specification. |
| + | |||
| + | controlinfo(7), | ||
| + | |||
| + | | |ftime=0|Ikke kontrollert| | ||
| + | |QC2d-2|**ftime=1**|**Interpolert/ | ||
| + | |QC2d-2|**ftime=2**|**Interpolert/ | ||
| + | |QC2d-2|ftime=3|Forsøkt interpolert/ | ||
| + | |||
| + | and add to cfailed that the method appiled was TAN, TAX average. | ||
| + | |||
| + | NB if the TAN TAX method is used (i.e. the correct information is available) and no HQC is overwritten, | ||
| __EXPECTIONS OF THE USEINFO FLAGS CORRESPONDING TO CONTROLINFO FLAG SETTINGS__ | __EXPECTIONS OF THE USEINFO FLAGS CORRESPONDING TO CONTROLINFO FLAG SETTINGS__ | ||
| - | * ... | + | * TBD |