Changes between Version 9 and Version 10 of IPP_for_PS2

Timestamp:

Apr 10, 2018, 3:38:05 PM (8 years ago)

Author:

watersc1

Comment:

--

IPP_for_PS2

@@ -39 +39 @@
 
  * The filter is not being interpreted from the header correctly.  The configuration lists the FILTERID keyword being used for both FPA.FILTERID and FPA.FILTER concepts.  The header lists FILTERID='i.00002 ' AND FILTER='i       ', but the tgpc2 database lists the filter as 'i'.  The header keywords and configuration both match what is being done with GPC1, so this mis-interpretation is not understood.
+  * A closer look shows that GPC1 uses FILTERID for both concepts.  ppStats uses the FPA.FILTER concept to populate the filter, so this is the source of the problem.  I'm hesitant to fix this right away, as it will require changing all the entries in the database already.  It might be best to wait until things are more stable and we're in a true commissioning phase.
  * The nightly_science desperate diff routine depends on the existence of a morning dark to signal that all observations have been taken.  These are not currently being taken, which prevented one diff from being constructed automatically.  I launched the diff with the command
 {{{difftool -definewarpwarp -dbname tgpc2 -set_workdir neb://@HOST@.0/tgpc2/OSS.nt/2018/03/30 -set_label czw.up -set_data_group OSS.20180330 -set_reduction SWEETSPOT -set_dist_group SweetSpot -exp_id 5729 -template_exp_id 5737 -input_label czw.up -template_label czw.up -good_frac 0.1 -backwards -trace db 5 -rerun}}}.
@@ -48 +49 @@
 
  * The i-band GPC1 stacks with label="LAP.PV3.20140730.final" are being ingested into the tgpc2 database to allow for warp (GPC2) - stack (GPC1) difference image processing.  The stackRun.filter column will need to be modified, as difftool blocks diffs that do not have the same filter.  The ingest process uses the stack_id value from the gpc1 database, so the tgpc2.stackRun and tgpc2.stackSumSkyfile tables will have a much higher auto-increment value.  The stackInputSkyfile entries are lost, as they reference warpSkyfile entries that do not exist.
+ * The i-band GPC1 stacks with label="LAP.PV3.20140730.final" are being ingested into the tgpc2 database to allow for warp (GPC2) - stack (GPC1) difference image processing.  The stackRun.filter column will need to be modified, as difftool blocks diffs that do not have the same filter.  The ingest process uses the stack_id value from the gpc1 database, so the tgpc2.stackRun and tgpc2.stackSumSkyfile tables will have a much higher auto-increment value.  The stackInputSkyfile entries are lost, as they reference warpSkyfile entries that do not exist.