Differences

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

--- kvalobs:kvoss:system:qc2:test:acceptance:qc2opelog [2010-03-25 23:20:25]
paule
+++ kvalobs:kvoss:system:qc2:test:acceptance:qc2opelog [2022-05-31 09:29:32] (current)
@@ Line 4: / Line 4: @@
 ^Step ^Direction ^Expected Result ^Pass/Fail Criteria or Comment ^
-|001 | Locate the Qc2 log file in $KVALOBS/var/log and remove all entries: | -- | -- |
+|001 | Locate the Qc2 log file in $PREFIX/var/log/kvalobs and remove all entries: | -- | -- |
+| |$ cd $PREFIX/var/log/kvalobs | NB PREFIX=/metno/kvalobs in local dev-vm116 installation, probably NULL for the debian roll-out | -- |
 | |$ rm Qc2.log Qc2.log.? |  | -- |
 | |     NB the "?" is to be typed :-)| -- | -- |
-|002 |start kvQc2 (either standalone or with $KVALOBS/bin/kvQc2 e.g. see QC2-OPE-CFG) | -- | -- |
+|002 |start kvQc2 (either standalone or with ~/bin/kvQc2 e.g. see QC2-OPE-CFG) | -- | -- |
-| |ls $KVALOBS/var/log |The Qc2.log file has been created (e.g. see below)  | -- |
+| |$ ls $PREFIX/var/log/kvalobs |The Qc2.log file has been created (e.g. see below)  | -- |
 <code>
-kvalobs@pak:~/var/log$ ls
+kvalobs@pak:~/var/log/kvalobs$ ls
 postgresql  Qc2.log
 kvalobs@pak:~/var/log$ cat Qc2.log
@@ Line 27: / Line 28: @@
 | |Hint: the logfiles rotate and tail -f will stall when a rotation occurs. Just cancel and restart the command. | -- | -- |
 |004 |Unpack the following config files to the Qc2Config directory: | -- | -- |
-| |{{:kvoss:system:qc2:test:acceptance:alg001-qcd2027.cfg.gz|}} |--  | -- |
+| |{{kvalobs:kvoss:system:qc2:test:acceptance:alg001-qcd2027.cfg.gz|}} |--  | -- |
-| |{{:kvoss:system:qc2:test:acceptance:alg004.cfg.gz|}} |--  | -- |
+| |{{kvalobs:kvoss:system:qc2:test:acceptance:alg004.cfg.gz|}} |--  | -- |
 | |The test database must contain corresponding data, e.g. see ALG001 and ALG004 | -- | --|
 | | **It is assumed that kvQc2 is still up and running! ** |||
@@ Line 83: / Line 84: @@
 --------------- ProcessUnitT Writing Data -32767 95350 2024-3-24 6:0:0
 </code>
+**__!!!!__** Look ... something to follow up:
+<code>
+20100326001908: INFO
+--------------- ProcessUnitT Writing Data -32767 95350 2024-3-24 6:0:0
+</code>
+**FIXED**
+<code>
+kvalobs=#  select * from data where stationid=95350 and obstime>'2024-03-24 04:00:00' and obstime<'2024-03-24 08:00:00' and paramid=211;
+ stationid |       obstime       | original | paramid |       tbtime        | typeid | sensor | level | corrected |   controlinfo    |     useinfo      |                          cfailed
+-----------+---------------------+----------+---------+---------------------+--------+--------+-------+-----------+------------------+------------------+------------------------------------------------------------
+| 2024-03-24 05:00:00 |     -7.2 |     211 | 2024-03-24 04:49:35 |    311 | 0      |     0 |      -7.2 | 1111200000000012 | 30000000000000C1 | QC1-4-211:1,hqc
+| 2024-03-24 06:00:00 |   -32767 |     211 | 2024-03-24 06:33:36 |    311 | 0      |     0 |      -7.6 | 1000501100000000 | 5894700000000041 | QC1-4-211:1,hqc,QC1-4-211:1 Qc2 UnitT corrected was:-32767
+| 2024-03-24 07:00:00 |     -7.3 |     211 | 2024-03-24 11:50:47 |    311 | 0      |     0 |      -7.3 | 1110200000000012 | 31000004000000C1 | QC1-4-211:1,hqc
+(3 rows)
+</code>
+In the example output the old corrected value was written to the logfile and not the new interpolated value. This has been corrected. This demonstrates the power of testing!
 ===== Added the following as a reminder to discuss! =====