Changes between Version 14 and Version 15 of PS1_IPP_Czarlog_20190318

Timestamp:

Mar 25, 2019, 10:26:23 AM (7 years ago)

Author:

fairlamb

Comment:

--

PS1_IPP_Czarlog_20190318

@@ -426 +426 @@
 
 Checking out some stalled update.OSS.broke things that are not faulted, so do not appear in IPP monitor:
-
+{{{
 SELECT chip_id, chipProcessedImfile.fault, warpRun.warp_id,warpRun.label,warpRun.state,warpSkyfile.fault,chipRun.label chiplabel,chipRun.state FROM warpRun JOIN warpSkyfile USING (warp_id) JOIN fakeRun USING (fake_id) JOIN camRun USING (cam_id) JOIN chipRun USING (chip_id) JOIN chipProcessedImfile USING (chip_id) WHERE warpRun.label LIKE "update.OSS.broke" AND warpRun.state LIKE "update" GROUP BY warpRun.warp_id;
-{{{
+
 +---------+-------+---------+------------------+--------+-------+--------------+--------------+
 | chip_id | fault | warp_id | label            | state  | fault | label        | state        |
@@ -490 +490 @@
 
 Most things just seem stuck on the old missing files from ippb05 problem (so I put it into repair for the time being).
-
+{{{
 chiptool -dbname gpc1 -setimfiletoupdate -chip_id 1268153 -set_label update.OSS.broke
 chiptool -dbname gpc1 -setimfiletoupdate -chip_id 1280537 -set_label update.OSS.broke
@@ -500 +500 @@
 chiptool -dbname gpc1 -setimfiletoupdate -chip_id 1726939 -set_label update.OSS.broke
 chiptool -dbname gpc1 -setimfiletoupdate -chip_id 1730278 -set_label update.OSS.broke
-
+}}}
 
 === Thursday : 2019.03.21 ===
@@ -510 +510 @@
 {{{
     pstamptool -dbname ippRequestServer -dbserver ipp113 -pendingdependent -simple
-}}}
+
 10818461 new warp 475995 skycell.1432.053 gpc1 /data/ipp113.0/pstamp/work/2019/01/10/914957 ps_ud_MOPS.2 F 0 1 MOPS 918857 /data/ipp113.0/pstamp/work/2019/01/10/914957/checkdep.10818461.log 500
 10818468 new warp 475962 skycell.1432.053 gpc1 /data/ipp113.0/pstamp/work/2019/01/10/914957 ps_ud_MOPS.2 F 0 1 MOPS 918857 /data/ipp113.0/pstamp/work/2019/01/10/914957/checkdep.10818468.log 500
@@ -516 +516 @@
 10959534 new warp 475962 skycell.1432.054 gpc1 /data/ipp113.0/pstamp/work/2019/03/21/918857 ps_ud_MOPS F 0 0 MOPS 918857 /data/ipp113.0/pstamp/work/2019/03/21/918857/checkdep.10959534.log 500
 10959535 new warp 475957 skycell.1432.054 gpc1 /data/ipp113.0/pstamp/work/2019/03/21/918857 ps_ud_MOPS F 0 0 MOPS 918857 /data/ipp113.0/pstamp/work/2019/03/21/918857/checkdep.10959535.log 500
-
+}}}
 Let's query these:
 {{{
@@ -544 +544 @@
     ppImage: psphotSourceSize.c:122: psphotSourceSizeReadout: Assertion `status' failed.
 }}}
-This implies that there is failure in the software, likelt because of code changes, so it cannot reprodue previous results.
+This implies that there is failure in the software, likely because of code changes, so it cannot reproduce previous results.
 
 Get the exposure names for these, then reprocess them (since they are w-band we should use the following, see the PSNSC_MOPS page for details): 
@@ -559 +559 @@
 1   MOPS    918857  weryk_5C941E46  2019-03-21 23:30:40 25  263293  00:15:07    2019-03-21 23:45:01
 }}}
+
 Let's check out this exposure, 263293:
 {{{
 SELECT rawExp.exp_name, rawExp.exp_id, chipRun.chip_id, chipRun.label chip_label, chipRun.state chip_state, warpRun.warp_id, warpRun.label warp_label, warpRun.state warp_state FROM rawExp JOIN chipRun USING (exp_id) JOIN camRun USING (chip_id) JOIN fakeRun USING (cam_id) JOIN warpRun USING (fake_id) WHERE exp_id=263293;
-}}}
-{{{
+
 +-------------+--------+---------+----------------------------+------------+---------+----------------------------+------------+
 | exp_name    | exp_id | chip_id | chip_label                 | chip_state | warp_id | warp_label                 | warp_state |