| 32 | | === Thursday : YYYY.MM.DD === |
| | 32 | === Thursday : 2015.10.08 === |
| | 33 | * 09:30 EAM: running updates on the outstanding ws diff inputs. I've generated a scripts in ~ipp to handle this situation so we don't have to keep re-inventing the commands. The script is called "~ipp/fix.ws.nightlyscience". Here are examples using it to find and fix the WS diff run inputs and then the diff runs: |
| | 34 | * list state of inputs to the outstanding WS diff runs: |
| | 35 | {{{ |
| | 36 | ipp@ippc19:/home/panstarrs/ipp>fix.ws.nightlyscience ippuser list |
| | 37 | +---------+---------+---------+------------------+---------+---------+-------+ |
| | 38 | | chip_id | warp_id | diff_id | data_group | state | state | state | |
| | 39 | +---------+---------+---------+------------------+---------+---------+-------+ |
| | 40 | | 1676749 | 1624170 | 1218073 | SNIa.20151002 | cleaned | full | new | |
| | 41 | | 1677272 | 1624691 | 1222131 | ThreePi.20151003 | full | cleaned | new | |
| | 42 | | 1677283 | 1624702 | 1222307 | ThreePi.20151003 | full | cleaned | new | |
| | 43 | | 1677582 | 1624994 | 1222718 | OSS.20151003 | cleaned | cleaned | new | |
| | 44 | +---------+---------+---------+------------------+---------+---------+-------+ |
| | 45 | }}} |
| | 46 | * generate chiptool and warptool commands to fix the problems above: |
| | 47 | {{{ |
| | 48 | ipp@ippc19:/home/panstarrs/ipp>fix.ws.nightlyscience ippuser update |
| | 49 | chiptool -dbname gpc1 -setimfiletoupdate -set_label ws_nightly_update -chip_id 1676749 |
| | 50 | chiptool -dbname gpc1 -setimfiletoupdate -set_label ws_nightly_update -chip_id 1677582 |
| | 51 | warptool -dbname gpc1 -setskyfiletoupdate -set_label ws_nightly_update -warp_id 1624691 |
| | 52 | warptool -dbname gpc1 -setskyfiletoupdate -set_label ws_nightly_update -warp_id 1624702 |
| | 53 | warptool -dbname gpc1 -setskyfiletoupdate -set_label ws_nightly_update -warp_id 1624994 |
| | 54 | }}} |
| | 55 | You can cut and paste the above lines, redirect them into a script to be sourced, or pipe the output directly to csh. After running the above, you will see the states get updated: |
| | 56 | {{{ |
| | 57 | ipp@ippc19:/home/panstarrs/ipp>fix.ws.nightlyscience ippuser list |
| | 58 | +---------+---------+---------+------------------+--------+--------+-------+ |
| | 59 | | chip_id | warp_id | diff_id | data_group | state | state | state | |
| | 60 | +---------+---------+---------+------------------+--------+--------+-------+ |
| | 61 | | 1676749 | 1624170 | 1218073 | SNIa.20151002 | update | full | new | |
| | 62 | | 1677272 | 1624691 | 1222131 | ThreePi.20151003 | full | update | new | |
| | 63 | | 1677283 | 1624702 | 1222307 | ThreePi.20151003 | full | update | new | |
| | 64 | | 1677582 | 1624994 | 1222718 | OSS.20151003 | update | update | new | |
| | 65 | +---------+---------+---------+------------------+--------+--------+-------+ |
| | 66 | }}} |
| | 67 | The runs get set to the label 'ws_nightly_update' which I've added to the input script for stdscience, so it is always available. |
| | 68 | |
| | 69 | After the inputs are processed, you may find the diff runs still fail (likely, as this is why they never completed in the first place). You can list the diff runs like this: |
| | 70 | {{{ |
| | 71 | ipp@ippc19:/home/panstarrs/ipp>fix.ws.nightlyscience ippuser diffstate |
| | 72 | +---------+------------------+---------------------------+------------------+-------+-------+ |
| | 73 | | diff_id | skycell_id | label | data_group | state | fault | |
| | 74 | +---------+------------------+---------------------------+------------------+-------+-------+ |
| | 75 | | 1222131 | skycell.1565.069 | ThreePi.WS.nightlyscience | ThreePi.20151003 | new | 2 | |
| | 76 | | 1222307 | skycell.1566.012 | ThreePi.WS.nightlyscience | ThreePi.20151003 | new | 2 | |
| | 77 | | 1218073 | skycell.1051.065 | SNIa.WS.nightlyscience | SNIa.20151002 | new | 5 | |
| | 78 | | 1222718 | skycell.0885.058 | OSS.WS.nightlyscience | OSS.20151003 | new | 5 | |
| | 79 | +---------+------------------+---------------------------+------------------+-------+-------+ |
| | 80 | }}} |
| | 81 | You can also examine the logs with the command: |
| | 82 | {{{ |
| | 83 | fix.ws.nightlyscience ippuser difflogs |
| | 84 | }}} |
| | 85 | Finally, the script will generate difftool commands to set the quality flags for the failures: |
| | 86 | {{{ |
| | 87 | ipp@ippc19:/home/panstarrs/ipp>fix.ws.nightlyscience ippuser difffix |
| | 88 | difftool -dbname gpc1 -updatediffskyfile -fault 0 -set_quality 66 -diff_id 1222131 -skycell_id skycell.1565.069 |
| | 89 | difftool -dbname gpc1 -updatediffskyfile -fault 0 -set_quality 66 -diff_id 1222307 -skycell_id skycell.1566.012 |
| | 90 | difftool -dbname gpc1 -updatediffskyfile -fault 0 -set_quality 42 -diff_id 1218073 -skycell_id skycell.1051.065 |
| | 91 | difftool -dbname gpc1 -updatediffskyfile -fault 0 -set_quality 42 -diff_id 1222718 -skycell_id skycell.0885.058 |
| | 92 | }}} |
| | 93 | In this case, the fault 2 entries had missing stack inputs, so they get quality 66 while the fault 5s were one of the more traditional psphot failures. |