24µm Focal Plane Survey, Fine

Principal: Jocelyn Keene
Deputy: Jane Morrison, Bill Wheaton
Data Monkey(s): Jane Morrison, Bill Wheaton
Priority: Critical
Downlink Priority: Normal
Analysis Time: Campaign Q: 2880 minutes, Campaign R: 2880 minutes, analysis of combining Campagin Q and Campaign R: 120 minutes
Last Updated:

Objective

To measure the pixel locations (i.e. array orientation, scale, and distortion) as a function of scan mirror angle for the 24µm array to an accuracy of 0.14 arc secs. This will allow us to determine the mapping of the celestial coordinates to pixel coordinates.

Description

Use an IER based on the 24 µm photometry compact source AOT to measure the locations on the sky of several positions on the array as a function of scanning mirror angle.
This task is run in campaigns Q and R. The data from each campaign is processed separately by the MIPS and IPF teams. The IPF team then combines the results from both campaigns. The results from the IPF multi-run are used to update Frame Table 14.

Data Collected

The IER is very similar to the one for the 24µm coarse Survey. The only difference is the mirror positions chosen map out more of the array. Also for the fine survey the IER is repeated twice. Each IER collects 336 DCEs. Therefore the total number of observations will be 672.

Calibration Star

See IER for the star chosen. This star was chosen as the 24 µm focal plane calibrator based on the following requirements:

Star needs to used as the PCRS star as well as the MIPs focal plane star. Note that PCRS stars have a V magnitude between 7-10 (this catalog is based on the Tycho and Hipparcos stars).

In CVZ

MIPs requirements: stellar brightness corresponding to S/N of 30 (3 sec integrations) at least 14 mJy, K mag 6.53 (range 14 to 500 mJy or K = 6.5 to 1.3)

Observing Strategy

Figure 1. Observing Pattern at 3 locations on the detector. Note size of box is not the total size of the array but a portion of the central region which depends on array and if it is a coarse or fine survey

Definitions:

W axis direction is defined by the Frame Table, and is always within +/- 90 degrees of the TPF z axis as projected on the sky. Motion along this axis corresponds to motion in the spacecraft motion (left/right).

V axis direction is defined by the Frame Table, and is always within +/- 90 degrees of the TPF y axis as projected on the sky. Motion along this axis corresponds to motion in the scan mirror direction (up/down).

W offset, the amount of motion in the W direction which results in the spacing between left array, middle array and right array observations

V offset, the amount of motion in the V direction which occurs between a set of observations.

24 µm Fine FPS observational parameters:

W offset = 138 arc seconds

V offset = 69 arc seconds

W dither = 3.75 arc seconds

V dither = 3.75 arc seconds

mirror locations for 1 position shown in figure 1.

position 1 = 0
position 2 = -75
position 3 = 25
position 4 = -50
position 5 = 50
position 6 = -25
position 7 = 75
position 8 = position 1 = 0

Observational Strategy

Step 1

PCRS observation

Step 2

Position the telescope so the data falls on the left side of array
Take 8 DCES at positions shown in figure 1 (left)
dither in V and W
Take 8 DCES at positions shown in figure 1 (left)

Step 3

Move the space craft according to the W offset (138 arc seconds), image should now be on the center of the array.
Take 8 DCES at positions shown in figure 1 (middle)
dither in V and W
Take 8 DCES at positions shown in figure 1 (middle)

Step 4

Move the space craft according to the W offset (138 arc seconds), image should now be on the right side of the array.
Take 8 DCES at positions shown in figure 1 (right)
dither in V and W
Take 8 DCES at positions shown in figure 1 (right)

Step 5

PCRS observation

Step 6: move telescope according to V offset (69 arc seconds) and repeat steps 1-5

Step 7: move telescope according to V offset (69 arc seconds) and repeat steps 1-5

Step 8: move telescope according to V offset (69 arc seconds) and repeat steps 1-5

Step 9: move telescope according to V offset (69 arc seconds) and repeat steps 1-5

Step 10: move telescope according to V offset (69 arc seconds) and repeat steps 1-5

Number of observations from step 1-5, 48. Step 1-5 repeated 7 times for a total of (48 * 7) = 336 observations. For the fine survey this set of observations is repeated a second time for a total of 672 observations.

Data Reformatting Requirements

Array Data Desired:

24 µm

Data Reformatting Option:

SPECIAL

Special Instructions:
A single FITS multi-image extension file is needed for each campaign. One image extension per DCE, processed through DAT. Input data from SSC PIPE0, sent to Jane Morrison at UA for calibration. File "mips_YYY095.fits" returned to SSC for centroiding, where "YYY" is 3-digit string denoting run number, and "095" is IPF code for 24 µm data.

Task Dependencies

MIPS-130: 24 µm Focal Plane Survey, Coarse
MIPS-910: 24 µm Darks
MIPS-305: 24 µm Flats
IPF run is to occur after FTU# 13 (PAC filer and OET CTA Frame Tool inputs)

Calibration Dependencies

Calibration product needed:
Data is downlinked. DSOT sends appropriate APIDs to OET and SIST
CB file: The OET Centroid File and Generation Tool is run to generate a centroid B file (CB file) and it is placed on the DOM
A and AS files: SIST generates a A and AS files (attitude history files) and emails them to IPF team.
O file: The MIPS team generates an 0 file (match derived frames to prime frames) and ftps to IPF team (this can be done before launch).
CS file: The MIPS team generated a CS file (Centroid supplemental file) to IPF team. This can be done before launch.
Generate set of PSF files for centroiding program, as a function of source (X,Y) on array and CSMM position. Use STINYTIM.

Output and Deliverable Products

The FF file (offset file) and CS file (centroid supplemental file) have been generated and sent to the IPF team. The coarse survey should indicate if the FF or CS file should have been changed before this campaign. Therefore we will probably not be changing these files. The name of the FF file is FFYYY095.m, where YYY is the version number of the file and 095 indicates it is for the 24 µm array. "001" to "499" are used for the coarse surveys, while "501" to "999" are used for the fine surveys.The CS file name is CSYYY095.m.

The data is processed through the Arizona dat and the calibrated data with the appropriate header keywords. The name of this file will be "mips_YYY095.fits". Where YYY is the version number and corresponds to the same YYY used for the FF and CS file. This file is returned to the SSC for centroiding.

The calibrated data is centroided and the centroided data filename is CAYYY095.m, where the YYY corresponds to the FF and CS file.

Data Analysis

Process data for Campaign Q:
1. JPL MIPL transfers downlink data to SSC.
2. SSC downlink ops processes through PIPE0, and places results in sandbox.
3. SSC MIPS IST uses FTZ to transfer data (AOR is ?) from sandbox to SSCIST21. The MIPS IT team repackages the dat to run with the Arizona data analysis tool (DAT). Data are FTP'd to UA.
4. The data are calibrated using the MIPS DAT.
  1. Run mips_sloper : with following options:
  2. Run mips_caler : with following options:
  3. Run visualizer and check to make sure data seems reasonable.
  4. The calibrated data file mipsfps_YYY095.fits (YYY a 3-digit integer string, identifying the run number) is a FITS multi-extension image file, one extension per DCE.
5. The calibrated data file mipsfps_YYY095.fits (YYY a 3-digit integer string, identifying the run number) is FTP'd back to SSCIST21 at SSC and placed on /mipsdata/fps/inpdat. File is linked to processing subdirectory (currently /home/sscmip/users/waw/fps).
6. The MIPS IDL Centroid File Generation tool, mipspos.pro, is run according to detailed instructions in /home/sscmip/users/waw/fps/fps.doc.
7. The output files CSYYY095.m and CAYYY095.m are placed on the TFS at SSC and transfered to DOM at JPL.
8. IPF team retrieves previously approved spreadsheet and SSC's CA/CS files from DOM.
9. IPF filter is run using input files: CB,A,AS,O, CA, CS files and the previously approved spreadsheet.
10. The output files (IF files) are placed on the DOM for MIPS team to analyze.
End of Campaign Q.
The entire process above is repeated for Campaign R.
Results from the IPF filter for Campaign Q and Campaign R are analyzed by the MIPS team and compared to one another for consistency.
On approval of consistency, the IPF team runs the IPF multi-run tool and produces an output file, MF, that is placed on the DOM.

Software Requirements

At SSC or UA, STINYTIM for PSF generation.
At SSC, downlink system PIPE0.
At UA, DAT calibration S/W, with repackaging into multi-extension FITS form.
At SSC, IDL program mipspos.pro for star centroiding.
At JPL, IPF Filter program.

Actions Following Analysis

The MIPS team reviews the MF files (combination of Campaign Q and R) from multi-run tool and approves or disapproves.
When approved, SSC generates mini-spreadsheet for review and approval by MCCB, followed by handoff to JPL OET, and uplink of FTU #14 -results from Campaign Q and R) .

Failure Modes and Responses

Failure/Response for FTU 14:

Failure of one campaign (Q or R) to produce useful data
- Use data from other campaign, if data appear reasonable and change is not large?
Results of Q & R inconsistent, neither obviously bad.
- ?