This is a checklist of the things that we know about that need to be processed (and where they go):

summitcopy

• service located in ~ipp/summitcopy (unless explicitly specified all files are relative to this directory)
• Downloads images off of the summit
  • 1 image = 1 exposure for GPC1
  • what about the other images?
• production code can be found in ptolemy.rc and input files. From input file inclusion, also configured by pantasks.pro, summit.copy.pro, and site.mhpcc.pro (likely / how to know the configuration is not loaded from somewhere else?) read from $PSCONFDIR/$PSCONFIG/share/pantasks/modules
• On this date (2010-11-04, update it if you checked) if you know how to read the summit.copy.pro, it tells you that:
  • It is started when? how often?
  • What does it do?
• Files of interest for that service:
  • pantasks.stderr.log: what does it contain?
  • pantasks.stdout.log: what does it contain?
  • pcontrol.log: what does it contain?
  • pantasks_log directory...
• Status can be asserted through czartool with the 'Current nightly science status' and the dedicated table (look for 'All science exposures')

registration

• in charge of burntool
• all images have been burntooled
• How are labels built?

stdscience

• OSS.nightlyscience exposures have gone through warp, then go to WSdiff

• MD%.nightlyscience exposures have gone through warp, then go to stack and diff (SSdiff and WSdiff)

• ThreePi.nightlyscience go through warp and WWdiff

• M31.nightlyscience go through warp
  • stacks?
  • what kind of diffs?
  • background stuff?

• STS.nightlyscience go through warp and diff (WSdiff)

• clean up faults on stdscience
• useful link for cleaning up faults: Processing

distribution

• magic, destreak, dist for MD, ThreePi, M31, STS
• currently no magic or destreak for OSS

publishing

• IPP-MOPS -> OSS unmagicked
• IPP-MOPS -> MD, ThreePi, STS(?) magicked

addstar

• currently only ThreePi
• AddstarPantasks - how to run addstar pantasks
• MinidvodbCopy - how to set up the automated transfer of minidvodbs

update

• we don't know anything about update
• how do we clean up faults on update?

pstamp

• we don't know anything about pstamp

replication

• we leave it off for now (?)

cleanup

• we know nothing about cleanup

detrend

• currently off, but the verifies are queued up daily

other

• check db replication status - if problems contact serge

• check diskspace - if problems contact chris or bill

• ISP processing (we need to start doing it)