Changes between Version 10 and Version 11 of IPP_for_PS2
- Timestamp:
- Apr 10, 2018, 3:38:24 PM (8 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
IPP_for_PS2
v10 v11 46 46 * 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. 47 47 * Occasionally the OBJECT field is not cleared before engineering data is taken. This has not resulted in non-science exposures being processed, but it is a possibility. 48 49 50 48 * 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. 51 * 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.
