... Fazio4.1
see http://ssc.spitzer.caltech.edu/geninfo/gto/abs/pid8 for details.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
... respectively4.2
see: http://ssc.spitzer.caltech.edu/obs/bg.html for plots of the IR background at various Galactic latitudes, and the SSC's classification of low/medium/high backgrounds.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
... time4.3
In Cookbook v3.0 and earlier, this calculation was performed using 200 sec frame times. The calibration of 200 sec frames is no longer supported - See the SOM.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
... tab6.1
This is necessary because the flux density for a peak-up target has not yet been entered, which is required before storing the AOR in Spot's memory - we will return to this soon.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
... mag6.2
This bright magnitude limit of $ V = 7.0$ is 0.5 mag brighter than that given in v2.6 and earlier of this Cookbook, and reflects a revision to the PCRS peak-up procedure based on in-orbit tests.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
... here6.3
Like much of the documentation related to Spitzer's PCRS, dissemination of this information is restricted by the International Traffic in Arms Regulation. Please contact the Spitzer Helpdesk at help@spitzer.caltech.edu if you are concerned about a nearby companion to a potential PCRS peak-up target star.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
... Cookbook7.1
Please see that section if you have not already, because it includes important information about a factor of cos$ \delta$!
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
...fig:orionmipsaorv1time9.1
Careful readers will note that the total time for the AOR is not equal to the sum of the times given here. There are ``hidden'' overheads, e.g., the time devoted to taking stim flashes. We as observers have no control over the frequency or duration of the stim flashes, or anything else in the ``hidden'' overheads. We do, however, have control over all the overheads shown here - e.g., by varying the scan rate, the slew and settle times change; by reducing the number of AORs in the program, the total slew overhead can be reduced.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
... grid.10.1
Using more grid elements than this (e.g., $ 14\times 14$) results in an error in Spot - to see the detailed error, we pull up the AOR, increase the grid elements to 14, and explicitly ask Spot to calculate observing time. It checks on the number of commands, the number of strings, the size of the command sequence, and the number of instructions for the spacecraft we're generating via this AOR. We run over on the number of instructions. We can break our AOR up into pieces (see the previous MIPS chapter for an example of this concept), or we can just reduce the size of our map slightly, which is what we have done here. This whole issue may be remedied in a future software release, but for now it's safest to break up the AOR or reduce its size.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
... hours!13.1
Note that for Cycle-4, the maximum duration of an IRAC observation has been extended from 6 to 8 hours. Observers should attempt to minimize the number of AORs constituting their proposal (and therefore the overall time request) in order to minimize the overheads associated with repointing.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.