Changes between Version 4 and Version 5 of PS1_IPP_Czarlog_20190318

Timestamp:

Mar 18, 2019, 4:46:54 PM (7 years ago)

Author:

fairlamb

Comment:

--

PS1_IPP_Czarlog_20190318

@@ -1 @@
-== PS1 IPP Czar Logs for the week YYYY.MM.DD - YYYY.MM.DD == 
+== PS1 IPP Czar Logs for the week 2019.03.18 - 2019.03.24 == 
 [[PageOutline]]
 
 (Up to [wiki:PS1_IPP_CzarLogs PS1 IPP Czar Logs])
+
+Czar of the week: John, with MEH as czar-lord (previously: TdB)
 
 === Monday : 2019.03.18 ===
@@ -49 +51 @@
  * MEH: sending more chips to cleanup for warps in full state
   * ipp091 excess load from being harassed from cleanup and failed BBU, leaving in neb-host repair now
+
+
+JRF: (afternoon czar formation ft. MEH) 
+
+
+The recipes directory contains a bunch of configurations:
+{{{
+ippitc/src/ipp-20170121/ippconfig/recipes
+}}}
+
+
+We'll look at the {{{reductionClasses.mdc}}} config file:
+
+Contains the configuration for how to process something. In this case the '''CHIP_PPIMAGE''' stage is set to '''CHIP_NOMASKTEST''' instead of the usual '''CHIP'''.
+
+# test for MOPS request reprocessing without masking
+{{{
+NOMASKTEST             METADATA
+        CHIP_PPIMAGE      STR     CHIP_NOMASKTEST
+        .
+        .
+        .
+        BACKGROUND_PSWARP       STR     BACKGROUND
+        PSVIDEOPHOT             STR     PSVIDEOPHOT
+END
+}}}
+
+There are separate configs for each camera (go up a directory then into the relevant camera dir). There are a bunch of configs here are empty in the main config, but have entries for the separate cameras. This is because data from each camera should be treated separately.
+
+
+'''WATCH OUT''': If you reprocess something with a different config then the stamp server will use whatever the latest config was for a request!
+Therefore, it's best to do some crazy reprocessing locally, so as not to pollute the database with entries that could confuse the current stamp request system.
+
+Time to reprocess some stuff for Rob with no masks (as seen on PSNSC_MOPS page and czar log from 2019.02.18 - 2019.02.24):
+{{{
+chiptool -definebyquery -set_label mops.nomasktest  -set_workdir neb://@HOST@.0/gpc1/mops.nomasktest -set_data_group mops.nomasktest -set_dist_group NULL -set_tess_id RINGS.V3 -set_end_stage warp -set_reduction NOMASKTEST -dbname gpc1 -exp_name o7403g0726o
+chiptool -definebyquery -set_label mops.nomasktest  -set_workdir neb://@HOST@.0/gpc1/mops.nomasktest -set_data_group mops.nomasktest -set_dist_group NULL -set_tess_id RINGS.V3 -set_end_stage warp -set_reduction NOMASKTEST -dbname gpc1 -exp_name o7403g0707o
+chiptool -definebyquery -set_label mops.nomasktest  -set_workdir neb://@HOST@.0/gpc1/mops.nomasktest -set_data_group mops.nomasktest -set_dist_group NULL -set_tess_id RINGS.V3 -set_end_stage warp -set_reduction NOMASKTEST -dbname gpc1 -exp_name o7403g0688o
+chiptool -definebyquery -set_label mops.nomasktest  -set_workdir neb://@HOST@.0/gpc1/mops.nomasktest -set_data_group mops.nomasktest -set_dist_group NULL -set_tess_id RINGS.V3 -set_end_stage warp -set_reduction NOMASKTEST -dbname gpc1 -exp_name o7403g0669o
+}}}
+As you can see we're using the NOMASKTEST reduction that we just had a look at the config for.
+
+Don't forget to add the label to pantasks to make it run!
+
+
+Time to fix some stuck jobs!
+Some files are needed from ippb05, but it has been misbehaving and was set to down ealier today. We shall quickly put it to repair so that the files can be accessed:
+{{{
+neb-host ippb05 repair --note "JRF: down -> repair: so that some broken updates can clear on ippmonitor"
+}}}
+Then we shall revert the chip for the stuck job so that it can continue:
+{{{
+chiptool -revertprocessedimfile -fault 2 -label ps_ud_MOPS -dbname gpc1
+}}}
+You don't need to specify the chip_id, it'll just revert all faults that are stuck.
+
+
+If you come across a stamp that you suspect maybe be stuck, have a look at it using:
+{{{ 
+pstamptool -dbname ippRequestServer -dbserver ipp113 -pendingdependent -simple
+}}}
+remove '-simple' to get some more information.
+
 === Tuesday : 2019.03.19 ===