24µm Focal Plane Survey, Coarse

Principal: Jocelyn Keene
Deputy: Jane Morrison, Bill Wheaton
Data Monkey(s): Jane Morrison, Bill Wheaton
Priority: Critical
Downlink Priority: Normal
Analysis Time:
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.

Description

Use an IER based on the 24 µm photometry AOT for a compact source to measure the locations on the sky of several positions on the array as a function of scanning mirror angle. This task is performed in Campaign F and Campaign G. After Campaign G is finished the results from campaign F and campaign G are merged together to update Frame Table # 9.

Data Collected

IER for 24µm Focal Plane Survey, Coarse collects 336 DCEs, of which 234 have the source on the array (others will have only much weaker sources present). The IER is set up so data is collected in 3 columns on the array: on the left-side, center and right-side of the array. After moving the telescope in the V direction according to the V offset, the observational patter is repeated 7 more times (with a V offset between each set).

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 Coarse 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 = -69
position 3 = 23
position 4 = -46
position 5 = 46
position 6 = -23
position 7 = 69
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.

Simulated data

Figure 1: Simulated images of 24 µm Focal Plane Survey Coarse.

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-121: 24 µm Focus Confirmation
IPF run is to occur after FTU#8 (PAC filer and OET CTA Frame Tool inputs)

Calibration Dependencies

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

Output and Deliverable Products

The FF file (offset file) and CS file (centroid supplemental file) have been generated and sent to the IPF team. Unless the results from the coarse survey result in significant changes to these files, these files will not be changed for the fine survey. 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. The CS file name is CSYYY095.m.

The data is processed through the Arizona dat and the calibrated file 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

Data Analysis Campaign F:
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 0002694400) from sandbox to SSCIST21, and repackages to run with the Arizona data analysis tool (DAT). Data are FTP'd to UA.
4. The data are calibrated at UA by running through the MIPS DAT, checking to make sure it seems reasonable. Result is 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 F.
Data Analysis for Campaign G:
1. The entire process (described in Campaign F) is repeated for Campaign G.
Analysis of output from Campaign F and Campaign G
1. Results from the IPF filter for Campaign F and Campaign G are analyzed by the MIPS team and compared to one another for consistency.
2. 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

After this this task has been run in both campaign F and campaign G the MIPS team receives a MF file from the multi-run tool (produced by the IPF team). The MIPS team reviews the MF file 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 #9.

Failure Modes and Responses

Failure/Response:

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

Additional Notes

// LocalWords: doctype html PHP caid http charset iso php IOC Downlink AOT µm // LocalWords: filemtime MIPs Tycho Hipparcos mJy img UA YYY centroiding IPF // LocalWords: FTU OET CTA downlinked APIDs SIST PSF STINYTIM JPL MIPL IST MF // LocalWords: downlink FTZ SSCIST FTP'd mipsfps IDL mipspos CSYYY CAYYY TFS // LocalWords: SSC's MCCB handoff uplink