Summary information page of SAS (footprint and SAS2 3-year stack) and MD04 stack data products for loading into the PSPS in Nov. 2011.

IPP

Processing of exposures, creation of stacks and staticsky runs with psphotStack.

images

Camera and stack label / data_group

MD04: reprocessed MD04 data for MD.GR0 and new refstacks

• camera: condor_MD04.V3_01 / condor_MD04.V3_01_dg
• stacks: MD04.refstack.20111012
• MD04 exposures: 1685 (356,349,428,343,209)
• MD04 stacks: 339 (grizy 67,66,65,72,69) will have large variety of N filter staticsky inputs

SAS.footprint.123: 3-year set (from July 2011) -- all in new reference catalog, z-band okay in area covered

• camera: SAS.footprint.123 / SAS.footprint.123.201107%
• stacks: SAS.footprint.123 / SAS.footprint.123.skycell.%.final.201107%

SAS2.123: 3-year set SAS version 2 (from July 2011) -- all in new reference catalog, however a problem was found with the z-band and a replacement is necessary for that filter

• camera: SAS2.123 / SAS2.123.201107% + SAS2.123.synthcat / SAS2.123.synthcat.skycell.%.final.2011080% for z-band replacement
• stacks: SAS2.123 / SAS2.123.skycell.%.final.201107% + SAS2.123.synthcat / SAS2.123.synthcat.skycell.%.final.2011080% for z-band replacement -- for z-band, changed stackRun.label SAS2.123 to SAS2.123.poor_refcat with note

--- Revised SAS run mostly done ---

Revised SAS.footprint.123: (full reprocessing of exposures chip->warp, stack, diff, DS) using the recent ipp-20111110 operations tag and LAP scripts to recover missing stacks (and any exposures) and uses the synthcat for all filters (like normal LAP processing) instead of just z-band as in the July run.

• camera: SAS.footprint.123.rerun20111129 / SAS.footprint.123.20111129
• stacks: SAS.footprint.123.rerun20111129 / SAS.footprint.123.skycell.%.final.1%
• SAS.footprint exposures: 61 (13,12,12,12,12) vs 64 (16,12,12,12,12) in July run. 1 exposure not magicked (g-band) in rerun but used in all 63 of the stacks. should've been done with muti-diffs?
• SAS.footprint stacks: 314 (63,63,63,63,62) vs 315 (5x63) in July run but not all existed even though in stackRun table hence the rerun.

Revised SAS2.123: (full reprocessing of exposures chip->warp, stack, diff, DS) using the recent ipp-20111110 operations tag and LAP scripts to recover missing stacks (and any exposures) and uses the synthcat for all filters (like normal LAP processing) instead of just z-band as in the July run.

• camera: SAS2.123.rerun20111129 / SAS2.123.20111130
• stacks: SAS2.123.rerun20111129 / SAS2.123.skycell.%.final.1%
• SAS2.123 exposures: 620 (5x124) vs 568 (124,124,124,124,72) in July run. Some 28 rerun exposures aren't magicked and aren't used in the stacks (except for 3 g-bands), unsure why.
• SAS2.123 stacks: 1464 (282,287,283,330,282) vs ~1600? (400,400,400,400/327synth,400) in July run but not all existed even though in stackRun table hence the rerun

Examples of changes with revised set:

• footprint g-band stacks for many in skycell 1406 had entry in stackRun but never made (add detail example)
• SAS2.123 various stacks missing/problem
• Header NASTRO missing in July version

  /data/ipp012.0/nebulous/37/43/1126204721.gpc1:SAS2.123:2011:07:23:o5745g0546o.356920:o5745g0546o.356920.cm.239183.smf
  /data/ipp054.0/nebulous/b7/55/1641973959.gpc1:SAS2.123:2011:11:30:o5745g0546o.356920:o5745g0546o.356920.cm.334131.smf
  

• all are with synthcat again

staticsky

Staticsky runs are an ongoing process as issues are solved in psphotStack and data, so a running label/data_group with date and number of filter inputs is generally used. Initially 5x<date> was used to indicate 5 filters only, future runs will likely drop the 5x (and 4x,3x,2x,1x) to indicate it contains N=1-5 available filters and use Nx<date> (i.e., Nx20111202).

MD04:

• MD04.refstack.20111012.5x20111114: initial run with few succeeding, but enough for a sample test set.
• MD04.refstack.20111012.5x20111122 (currently best to use):
  • many improvements to fix faults on MD stacks, analysis header added earlier and psphotStack version added
  • some CMFs lost on the ipp064 disks, 1114 not a good replacement as very few skycells succeeded in that run.
• MD04.refstack.20111012.<N>x20111129, <N=1-5>: run to replace the ones lost on ipp064, and will include skycells with fewer than the full 5 filter complement
  • 8 fault still (7@5x and 1@3x)
  • expected totals: 74 (Nx=1,2,3,4,5: N=3,3,2,2,64) vs 64 (x,x,x,x,64) for 5x20111122

SAS.footprint.123:

• SAS.footprint.123.5x20111114: initial run with a good sample succeeding for a sample test set.
• SAS.footprint.123.5x20111118 (currently best to use):
  • misc. improvements, analysis header added, APER_FLUX array fixed for smoothed image
• SAS.footprint.123.5x20111122: improvements in psphotstack to fix faults, added psphotStack version. some CMFs lost with ipp064 disks, best to use 1118 for now
• SAS.footprint.123.<N>x20111129, <N=1-5>: run using the revised SAS.footprint.123.rerun20111129 to include the missing g-band stacks and replace the CMFs lost on ipp064. Will include skycells with fewer than the full 5 filter complement.
  • 3 fault still (all 5x)
  • expected totals: 61 (x,x,1,7,53) vs 35 (x,x,x,x,35) for 5x20111118

SAS2.123:

• SAS2.123.5x20111118 (currently best to use):
  • misc. improvements, analysis header added, APER_FLUX array fixed for smoothed imaged
• SAS2.123.5x20111122: improvements in psphotstack to fix faults, added psphotStack version. some CMFs lost with ipp064 disks, best to use 1118 for now
• SAS2.123.<N>x20111129, <N=1-5>: run using the revised SAS2.123.rerun20111129 to include the missing stacks and replace the CMFs lost on ipp064. Will include skycells with fewer than the full 5 filter complement.
  • 9 fault still (all 5x)
  • expected totals: 324 (34,4,4,9,273) vs 264 (x,x,x,x,264) for 5x20111118

dvodb

All of these are located at /data/ipp005.0/gpc1/catdirs/(dvodbname)

SAS.20111122

• do not use. Contains camRun labels SAS2.123 and SAS.footprint.123. Don't use because we want dvodbs of each 3 year and footprint.

SAS.20111125

• do not use. Contains wrong z band camRuns
• camRun = SAS2.123 (data_group = SAS2.123.20110723)
• staticskyRun = SAS2.123.5x.2011118
• both camRun and staticskyRun are being redone. When they are done, I will make a new dvodb containing those

SAS.20111201

• camRun = SAS2.123 (data_group SAS2.123.20110723) for griy
• camRun = SAS2.123.synthcat for z
• staticskyRun = SAS2.123.5x.2011118
• both camRun and staticskyRun are being redone. When they are done, I will make a new dvodb containing those

SAS.FP.20111128

• camRun = SAS.footprint.123 (data_group = SAS.footprint.123.201107%)
• statiskyRun = SAS.footprint.123.5x20111118
• both camRun and staticskyRun are being redone. When they are done, I will make a new dvodb containing those

MD04.20111128

• camRun = condor_MD04.V3_01
• staticskyRun = not yet, but MD04%5x20111122
• staticskyRUn is being redone. When it is, I will redo the merges to make a dvodb of condorcamRun + new staticsky

---