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:user:version:kvqc2d-1.1.2 [2011-05-08 19:52:45] paule |
kvalobs:kvoss:system:qc2:user:version:kvqc2d-1.1.2 [2022-05-31 09:29:32] (current) |
||
---|---|---|---|
Line 1: | Line 1: | ||
- | |||
- | .... in preparation ... FIXME | ||
- | |||
====== kvqc2d Version: 1.1.2 ====== | ====== kvqc2d Version: 1.1.2 ====== | ||
Line 16: | Line 13: | ||
^ Algorithm(+) ^Description | ^ Algorithm(+) ^Description | ||
- | | SingleLinear | As in previous release kvqc2d_1.1.0: | + | | SingleLinear | As in previous release kvqc2d_1.1.0: |
| Redistribute | As in previous release kvqc2d_1.1.0: | | Redistribute | As in previous release kvqc2d_1.1.0: | ||
| DipTest | New algorithm: https:// | | DipTest | New algorithm: https:// | ||
Line 22: | Line 19: | ||
(+) This is the name to specify in the configuration file. | (+) This is the name to specify in the configuration file. | ||
- | **Example | + | **Install |
For this release all the configuration files need to be re-installed since the use of AlgoCode=" | For this release all the configuration files need to be re-installed since the use of AlgoCode=" | ||
Line 30: | Line 27: | ||
This includes a tar file of all of the required contents for easier deployment | This includes a tar file of all of the required contents for easier deployment | ||
- | To install new configuration files and setup the associated | + | To install new configuration files and setup the associated |
+ | |||
+ | **New cfg files** | ||
< | < | ||
- | # after logging | + | # log into the operational machine as the kvalobs user |
+ | |||
+ | # stop the existing kvqc2d | ||
+ | $ kvstop -l | ||
+ | |||
+ | #setup new configuration | ||
$ cd / | $ cd / | ||
- | $ rm ./*.cfg | + | # remove the old files (-i is suggested below so that the user is prompted to confirm removal and verify that only the desired files are removed). |
- | $ rm ./*.hold | + | $ rm -i ./*.cfg |
+ | $ rm -i ./ | ||
+ | # fetch the new files, e.g.: | ||
$ wget https:// | $ wget https:// | ||
$ tar xvzf cfg.tar.gz | $ tar xvzf cfg.tar.gz | ||
Line 43: | Line 49: | ||
# The configuration files are now in place. | # The configuration files are now in place. | ||
- | --------------------------------------------- | + | # restart kvqc2d when ready: |
+ | $ kvstart | ||
+ | |||
+ | </ | ||
+ | |||
+ | **cron jobs** | ||
+ | < | ||
# In order to set up the crontab for the weekly redistribution run | # In order to set up the crontab for the weekly redistribution run | ||
+ | $ cd / | ||
+ | # The scripts are present in the cfg.tar.gz archive and should be present if the new cfg file installation steps above have been followed. | ||
$ chmod +x Redistribution_14days_off_cron.sh | $ chmod +x Redistribution_14days_off_cron.sh | ||
$ chmod +x Redistribution_14days_on_cron.sh | $ chmod +x Redistribution_14days_on_cron.sh | ||
Line 63: | Line 77: | ||
Notes: the new scripts in cron renames " | Notes: the new scripts in cron renames " | ||
+ | |||
+ | The Redistribution algorithm will then run automatically to the following schedule: | ||
+ | * typically daily run at **06:35** looking at the last 4 days | ||
+ | * **01:20** Wednesday Night/ | ||
+ | |||
+ | Previously the management of the Redistribution configuration files (i.e. hold -> cfg -> hold) has been handled manually. | ||
**Example Configuration Files** | **Example Configuration Files** | ||
^SingleLinear_v32^ | ^SingleLinear_v32^ | ||
- | |||
- | *NB* Different/ | ||
< | < | ||
Line 188: | Line 206: | ||
93 15.0 | 93 15.0 | ||
94 15.0 | 94 15.0 | ||
- | 104 100 | ||
105 3.0 | 105 3.0 | ||
113 15.0 | 113 15.0 | ||
Line 209: | Line 226: | ||
</ | </ | ||
+ | **Note:** Previously " | ||
+ | |||
+ | ====== Notes on first production run ====== | ||
+ | |||
+ | * Released into operations on 2011-05-18 circa 09:38 UTC | ||
+ | |||
+ | Algorithms ran as expected: | ||
+ | |||
+ | ^DipTest^ | ||
+ | |||
+ | First result (note __only one__ Dip was identified): | ||
+ | |||
+ | < | ||
+ | kvalobs=# select * from data where stationid=79600 and obstime between ' | ||
+ | | ||
+ | -----------+---------------------+----------+---------+----------------------------+--------+--------+-------+-----------+------------------+------------------+----------------------------- | ||
+ | 79600 | 2011-05-18 15:00:00 | 2.9 | 90 | 2011-05-18 14: | ||
+ | 79600 | 2011-05-18 16:00:00 | 3.1 | 90 | 2011-05-18 15: | ||
+ | 79600 | 2011-05-18 17:00:00 | 3.5 | 90 | 2011-05-18 16: | ||
+ | 79600 | 2011-05-18 18:00:00 | 22 | 90 | 2011-05-18 17: | ||
+ | 79600 | 2011-05-18 19:00:00 | 3.1 | 90 | 2011-05-18 18: | ||
+ | 79600 | 2011-05-18 20:00:00 | 3.5 | 90 | 2011-05-18 19: | ||
+ | 79600 | 2011-05-18 21:00:00 | 2.4 | 90 | 2011-05-18 20: | ||
+ | 79600 | 2011-05-18 22:00:00 | 2 | 90 | 2011-05-18 21: | ||
+ | |||
+ | |||
+ | **Propagated downstream? | ||
+ | |||
+ | In this link the data appears as ' | ||
+ | |||
+ | [[http:// | ||
+ | |||
+ | But when resetting the limit qa=6 ... | ||
+ | |||
+ | [[http:// | ||
+ | |||
+ | the data is visible downstream. | ||
+ | |||
+ | **...more DipTest data from later runs are included hereafter as they are spotted: | ||
+ | |||
+ | < | ||
+ | 15270 | 2011-05-21 02:00:00 | 20.1 | 81 | 2011-05-21 01: | ||
+ | 15270 | 2011-05-21 03:00:00 | 18.5 | 81 | 2011-05-21 02: | ||
+ | 15270 | 2011-05-21 04:00:00 | 2.7 | 81 | 2011-05-21 03: | ||
+ | 15270 | 2011-05-21 05:00:00 | 17 | 81 | 2011-05-21 04: | ||
+ | 15270 | 2011-05-21 06:00:00 | 17.2 | 81 | 2011-05-21 05: | ||
+ | 15270 | 2011-05-21 07:00:00 | 19.4 | 81 | 2011-05-21 06: | ||
+ | </ | ||
+ | |||
+ | ^Single Linear^ | ||
+ | |||
+ | < | ||
+ | 39100 | 2011-05-18 11:00:00 | 9.9 | 213 | 2011-05-18 10: | ||
+ | 39100 | 2011-05-18 12:00:00 | 9.9 | 213 | 2011-05-18 11: | ||
+ | 39100 | 2011-05-18 13:00:00 | 10.2 | 213 | 2011-05-18 12: | ||
+ | 39100 | 2011-05-18 14:00:00 | 9999 | 213 | 2011-05-18 13: | ||
+ | 39100 | 2011-05-18 15:00:00 | 10 | 213 | 2011-05-18 14: | ||
+ | 39100 | 2011-05-18 16:00:00 | 9.9 | 213 | 2011-05-18 15: | ||
+ | 39100 | 2011-05-18 17:00:00 | 9.8 | 213 | 2011-05-18 16: | ||
+ | </ | ||
+ | |||
+ | |||
+ | ^Redistribution^ | ||
+ | |||
+ | The algorithm ran but no redistribution took for place for the last 4 days. Results will be checked again after the next runs ... and here they are: | ||
+ | |||
+ | < | ||
+ | 48780 | 2011-05-11 06:00:00 | -1 | 110 | 2011-05-11 05: | ||
+ | 48780 | 2011-05-12 06:00:00 | 1.9 | 110 | 2011-05-12 05: | ||
+ | 48780 | 2011-05-13 06:00:00 | | ||
+ | 48780 | 2011-05-14 06:00:00 | | ||
+ | 48780 | 2011-05-15 06:00:00 | | ||
+ | 48780 | 2011-05-16 06:00:00 | | ||
+ | 48780 | 2011-05-17 06:00:00 | | ||
+ | 48780 | 2011-05-18 06:00:00 | 54.8 | 110 | 2011-05-18 09: | ||
+ | 48780 | 2011-05-19 06:00:00 | 8.2 | 110 | 2011-05-19 05: | ||
+ | </ | ||
+ | |||
+ | ^crontab control of weekly, two week redistribution^ | ||
+ | |||
+ | The crontab called the scripts successfully but the timing was wrong so the wrong script was called resulting in no algorithm running (but no other impact). | ||
+ | |||
+ | Problem identified as the wrong time in the crontab (hours and minutes mixed up ... pilot error!) | ||
+ | |||
+ | The erroneous entry: | ||
+ | |||
+ | < | ||
+ | # kvqc2d | ||
+ | 23 0 * * 3 / | ||
+ | 23 0 * * 4 / | ||
+ | </ | ||
+ | |||
+ | shall be changed to | ||
+ | |||
+ | < | ||
+ | # kvqc2d | ||
+ | 25 23 * * 3 / | ||
+ | 25 23 * * 4 / | ||
+ | </ | ||
+ | |||
+ | and installed on Friday (i.e. day=5) so that the cron runs next week. The belated 14 day run is now ready to go for this week. | ||
+ | These are real time notes on 2011-05-19 | ||
+ | **Update** For 2011-05-25 (Wednesday) to 26 (Thursday) : the cron cycling worked OK. |