Changes between Version 19 and Version 20 of PS1_IPP_Czarlog_20190204

Timestamp:

Feb 8, 2019, 12:15:20 PM (7 years ago)

Author:

fairlamb

Comment:

--

PS1_IPP_Czarlog_20190204

@@ -241 +241 @@
 }}}
 
+'''Evening update:'''
+Loads of errors reported in the chip stage from some ps_ud_MOPS.2 processing. Checking the stdout there are a bunch of programming errors and system failures (in the warp stage as well).
+
+I couldn't find the log files using nebulous for some of the exposures...
+
+
+At the top of the list is exposure o5367g0555o. Checking this in the table it's status is still 'update' in the chipRun table (full in expRun). So it looks like it's stuck, therefore I ran the wfix as per PSNSC instructions:
+{{{chiptool -dbname gpc1 -definebyquery -set_label PSNSC.wfix.20180525  -set_workdir neb://@HOST@.0/gpc1/PSNSC.wfix.20180525  -set_dist_group NULL -set_tess_id RINGS.V3 -set_end_stage warp -set_reduction SWEETSPOT -set_data_group PSNSC.wfix.20180525.x.date -exp_name o5367g0555o}}}
+
+I will check back shortly to see if this has cleared and run the remaining process on this exposure.
+
+
+Then I'll check all the other exposures.
+
 
 === Friday : 2019.02.08 ===
 
+
+'''Morning clean up'''
+JRF: I didn't finish clearing up last night as it got late and the telescope opened. So continuing on:
+
+I'll query the state of the exposures still listed as problems in the chiptool table:
+SELECT exp_name, exp_id, label, data_group, chipRun.state FROM rawExp LEFT JOIN chipRun USING (exp_id) WHERE exp_name IN ("o5563g0048o", "o5563g0068o", "o6081g0423o", "o6089g0580o", "o6215g0082o", "o6215g0062o", "o6783g0595o", "o6036g0249o", "o5368g0203o", "o5561g0743o", "o5522g0420o", "o6072g0424o", "o6215g0072o", "o5918g0460o", "o5218g0041o", "o5218g0057o", "o5362g0570o", "o5362g0583o", "o5476g0223o", "o5476g0289o", "o5855g0127o", "o5328g0034o", "o5328g0050o")
+
+From these, the following are done, indicated by the state="full":
++-------------+--------+---------------------+----------------------------+-------+---------+
+| exp_name    | exp_id | label               | data_group                 | state | chip_id |
++-------------+--------+---------------------+----------------------------+-------+---------+
+| o5218g0041o | 125344 | PSNSC.wfix.20180525 | PSNSC.wfix.20180525.x.date | full  | 2128159 | 
+| o5218g0057o | 125358 | PSNSC.wfix.20180525 | PSNSC.wfix.20180525.x.date | full  | 2128160 | 
+| o5362g0570o | 181829 | PSNSC.wfix.20180525 | PSNSC.wfix.20180525.x.date | full  | 2128161 | 
+| o5362g0583o | 181842 | PSNSC.wfix.20180525 | PSNSC.wfix.20180525.x.date | full  | 2128162 | 
+| o5476g0223o | 235917 | PSNSC.wfix.20180525 | PSNSC.wfix.20180525.x.date | full  | 2128164 | 
+| o5476g0289o | 235984 | PSNSC.wfix.20180525 | PSNSC.wfix.20180525.x.date | full  | 2128163 | 
++-------------+--------+---------------------+----------------------------+-------+---------+
+
+Therefore, set their old chips, the ones stuck in update, to clean:
+SELECT exp_name, exp_id, label, data_group, chipRun.state, chipRun.chip_id FROM rawExp LEFT JOIN chipRun USING (exp_id) WHERE exp_name IN ("o5218g0041o", "o5218g0057o", "o5362g0570o", "o5362g0583o", "o5476g0223o", "o5476g0289o") AND chipRun.state="update";
++-------------+--------+--------------+------------------+--------+---------+
+| exp_name    | exp_id | label        | data_group       | state  | chip_id |
++-------------+--------+--------------+------------------+--------+---------+
+| o5218g0041o | 125344 | ps_ud_MOPS.2 | ecliptic.rp.23hr | update |  486920 | 
+| o5218g0057o | 125358 | ps_ud_MOPS.2 | ecliptic.rp.23hr | update |  486927 | 
+| o5362g0570o | 181829 | ps_ud_MOPS.2 | ecliptic.rp.1hr  | update |  489051 | 
+| o5362g0583o | 181842 | ps_ud_MOPS.2 | ecliptic.rp.1hr  | update |  489062 | 
+| o5476g0223o | 235917 | ps_ud_MOPS.2 | ecliptic.rp.1hr  | update |  489311 | 
+| o5476g0289o | 235984 | ps_ud_MOPS.2 | ecliptic.rp.1hr  | update |  489341 | 
++-------------+--------+--------------+------------------+--------+---------+
+use:
+{{{
+chiptool -dbname gpc1 -updaterun -set_state goto_cleaned -set_label goto_cleaned -chip_id XXXXXX
+}}}
+
+
+Query the remaining with:
+SELECT exp_name, exp_id, label, data_group, chipRun.state, chipRun.chip_id FROM rawExp LEFT JOIN chipRun USING (exp_id) WHERE exp_name="XXXXXXX";
+
+All of these are stuck in the update step with the MOPS.2 label. I guess I never send this to be reprocessed. So I will do that using the wfix label, then I'll send the old to cleaned
+
+* HOWEVER... reading the wiki the LAP.PV3 may need to be processed without SWEETSPOT reduction, and instead use default...MEH will explain all later.
+
+
 JRF: ME, MEH, and TdB shall be going though reprocessing some data for Rob without some pixels removed (as an NEO is suspected to be falling into a masked area).