LAP Scheduling (2011-07-11 draft)

The colored stripes on this image represent the 2-hour bands in RA that the LAP processing will be broken into. In order to accomplish this, once we are in a steady state, we will need to complete a single filter in a given band within six days. This will require ~30-40 projection cells to be queued (and presumably completed) each day. We are currently (2011-07-11) working on the band from 14-16 hours (210-240 degrees) although we have not yet ramped up to a satisfactory processing rate.

The reason that we will do each filter across an entire band instead of completing five-filter data on individual projection cells is that we are attempting to make the best use of exposure sharing to minimize the processing time. This also reduces the number of exposures to keep on disk at any given time, as we are cleaning processed data as we go according to the following process:

• Block of runs are queued for a set of projection cells.
• Exposures are processed through to the final stacking stage.
• When all final stacks have completed for a run, the exposures that comprise that run are marked as inactive.
• A cleanup task operating on completed runs identifies exposures that are marked inactive for all runs they contribute to, and sets the data (chip/warp/diff/destreak/quickstack) from that exposure to be cleaned.

I have appended an example list of commands that will queue LAP across the entire sky. Once we have processing operating continually, a standard month should look as follows:

• Day 1: Begin a new month of processing between a two hour band of RA. Queue first filter (g?) for data between dec = (-30,-14).
• Day 2: Queue first filter dec = (-14, 2)
• Day 3: Queue first filter dec = (2, 18)
• Day 4: Queue first filter dec = (18, 38)
• Day 5: Queue first filter dec = (38, 62)
• Day 6: Queue first filter dec = (62, 90)
• Day 7: Switch to second filter (r?) and queue data for this RA band dec = (-30, -14)