Changes between Version 42 and Version 43 of PSNSC_MOPS

Timestamp:

Feb 7, 2019, 6:57:20 PM (7 years ago)

Author:

Mark Huber

Comment:

--

PSNSC_MOPS

@@ -124 +124 @@
   * can bump up the parse limit (in pstamp.pro) from 10->20 and should help for short term -- added as config in ipp-20170121r40242 update (see below)
  * unclear which refcat used in returned stamps (ie for astrometry in MOPS recovery work 2MASS/GAIAv1) -- really useful for warps->diffs to also have but PSREFCAT isn't propagated... -- keyword added now 2018xxxx 
+ * more broken images may be hiding without triggering error in pstamp -- expected pixels seen in other exposure in quad, chip being skipped due to broken?
  * broken files is plaguing precovery of priority events (fault 25,26 ) -- reprocessing to fix as needed -- unacceptable that LAP.PV3 files are broken being a recent reprocessing so just jusing DEFAULT recipe and calling mopsfix/mops.fixbrokenLAP.20180323 ; w-band not in LAP.PV3 reprocessing, typically old ecliptic.rp and those not reprocessed for wref stack, so using SWEETSPOT config and calling PSNSC.wfix.20180525
+   * ecliptic.rp or LAP.PV3W w-band
 {{{
 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 XXXXXX
-
+}}}
+   * LAP.PV3 grizy-band -- probably should have used -set_reduction LAP_SCIENCE 
+{{{
 chiptool -dbname gpc1 -definebyquery -set_label mopsfix  -set_workdir neb://@HOST@.0/gpc1/mops.fixbrokenLAP.20180323  -set_dist_group NULL -set_tess_id RINGS.V3 -set_end_stage warp -set_data_group mops.fixbrokenLAP.20180323 -exp_name XXXXXX
 }}} 
@@ -135 +139 @@
 warptool -dbname gpc1 -updaterun -set_state goto_cleaned -set_label goto_cleaned -warp_id XXXXX
 }}}
-  * more broken images may be hiding in without triggering error in pstamp -- expected pixels seen in other exposure in quad, chip being skipped due to broken?
-  * red herring cases on ippMonitor for ps_ud_MOPS or ps_ud_MOPS.2 
+  * errors in updates may happen (red cases on ippMonitor) for ps_ud_MOPS or ps_ud_MOPS.2, setting chip and warp to fully update can check if broken or just in odd fault state for imfile/skyfile(s)
 {{{
 chiptool -dbname gpc1 -setimfiletoupdate  -set_label ps_ud_WEB -chip_id XXXXXX