nd <? echo "MIPS-".$caid." IOC Task Cookbook"; ?>

SED Slit Location and Orientation

Principal: Jocelyn Keene
Deputy: Jane Morrison, Bill Wheaton
Data Monkey(s): Jane Morrison and Bill Wheaton
Priority: Critical
Downlink Priority: Normal
Analysis Time: Campaign I: 3600 minutes, Campaign J: 3600 minutes. Combining results from I and J 120 minutes.
Last Updated:

Objective

To determine the position and orientation of the SED slit relative to the PCRS.

Description

Put the CSMM in its nominal SED position to direct light from a bright 70 µm source into the SED optical train. Step the image across the slit by moving the spacecraft in 10 arc second steps for a total 6 steps. At each step using the CSSM to chop off the source. Integrate 3 sec each on and off the source along the slit. Insert each scan above within the standard FPS "PCRS sandwich" measurements and a set of stim observations. Dither the spacecraft in the v direction (across the slit) by 5 arcseconds and repeat the above observations. Repeat each stepping across the slit and dithering at 2 other locations along the slit.
This task is run in campaigns I and J. 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 12. The results from campaign I is also used to update Frame Table 10. The frame table updates for all the campaigns can be found in the following table: Frame Table Updates.

Data Collected

The observing strategy is described below. A total of 168 observations area obtained.

Calibration Star

For the selected calibration star see the IER for this survey. The requirements on the SED focal plane calibration star are as follows:

In CVZ

Mips requirements: stellar brightness corresponding to S/N of 30 (3 sec integrations) 0.212 Jy, K mag 1.25

Observing Strategy

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 moving the target along the slit.

V offset, the amount of motion in the V direction which results in moving the target across the slit.

SED FPS observational parameters:

W offset = 80 arc seconds

V offset = 10 arc seconds

W dither = none

V dither = 5 arc seconds

mirror locations for chopping .

position 1 = 0
position 2 = -60

Observational Strategy

Starting at an initial position on the left side of the array take 28 observations across the slit. Move to the center of the array and take another 28 observations across the slit. Then move to the right-side of the array and take 28 observations across the slit.

Step 1

PCRS observation

Step 2 (Two observations) Observations on Left-side of slit

Position the telescope at initial V and W offset positions, in the arrangement the target will fall on the left side of the slit.

Step 3 (Two observations)

Turn stim off and take DCE
Turn stim on and take DCE

Step 4 (Two observations) REPEATED 6 times(with Vstep between sets of observations) Total number of observations 12.

With stim off and take 1 DCE at mirror position 1.
Move mirror to position 2 and take a second DCE.
Move spacecraft according to V step (across slit) 10 arc seconds.

Step 5 (14 observations)

Stay at the same position as in step 4 (no v steps or w steps)
Repeat steps 3- 4

Step 6

PCRS observation

Step 7 (28 observations)

Dither in the V direction 5 arcseconds
repeat steps 3-5

Step 8 (28 observations) Observations on center of slit

Move the spacecraft according to W step (80 arcseconds)
repeat steps 3-5

Step 9 (28 observations) Observations on right-side of slit

Move the spacecraft according to W step (80 arcseconds)
repeat steps 3-5

Number of DCE observations from step 3-5, 28. Step 3-5 repeated 6 times for a total of (6 * 28) = 168 observations.

Data Reformatting Requirements

Array Data Desired:

70 µm - SED

Data Reformatting Option:

Normal - One FITS multi-image extension file per AOR. (Output from MIPS DATPACK, one DCE in each image extension.

Task Dependencies

MIPS-299: SED Slit Illumination Function
MIPS-132: 70 µm WF FPS, coarse
MIPS-911 70 µm darks
IPF run is to occur after FTU# 9 (PAC filer and OET CTA Frame Tool inputs)

Calibration Dependencies

Calibration product needed:

70 µm SED IC

70 µm darks

Items needed by IPF team for this task to run with the IPF filter software:

IPF team Labeling convention for files: XXYYYZZZ.m where,
- XX for type of file (example FF for Offset file, IF for output data, CS for Centroid supplemental file)
- YYY for the version number, '001' to '499' for Coarse survey, '501' to '999' for Fine Surveys
- ZZZ for the Frame table number associated with the Prime Frame being calibrated. Use 121 for the 70 µm SED mode.
CB file: The OET Centroid File and Generation Tool is run to generate a centroid B file (CB file)
A and As files: SIST generates a A and AS files (attitude history files) and emails them to IPF team.
FF file: The MIPS team generates an Offset file (match derived frames to prime frames) and ftps to IPF team (this can be done before launch and has been).
CS file: The MIPS team generated a CS file (Centroid supplemental file) to IPF team. This can be done before launch and has been.

Output and Deliverable Products

Output of MIPS DAT:
A calibrated data file with appropriated header keywords.
The name of this file will be "mips_YYY21.fits", where where "YYY" is 3-digit string denoting run number, and "121" is IPF code for 70 µm SED data.
This file is sent to B. Wheaton's centroiding program.
Output from Centroid program:
A centroided data file.
The calibrated data is centroided and the centroided data filename is CAYYY121.m, where the YYY is the version number. This file is sent to the IPF team.
Output from IPF team which the MIPS team analyzes:
- IF file: output data from a single IPF run.
- MF file: output data from a multi-run IPF run
The FF file (offset file) and CS file (centroid supplemental file) have been generated and sent to the IPF team. Unless the results from campaign I result in significant changes, these files will not be changed for campaign J.

Data Analysis

Process data for Campaign I:
1. JPL MIPL transfers downlink data to SSC.
2. SSC downlink ops processes data places results in sandbox.
3. SSC MIPS IST uses FTZ to transfer data from sandbox to SSCIST21. The MIPS IT team repackages the data to run with the Arizona data analysis tool (DAT).
4. The data are calibrated using the MIPS DAT.
  1. Run mips_sloper : with following options:
    - mips_sloper filename
    - IF we do not use the default directory for the calibration files. Then use the -j option.
    - -j dirname : directory below $MIPS_DIR/Cal to find calibration files.
  2. Run mips_caler : with following options:
    - mips_caler -I illumination_correction_filename -D dark_filename-C pathname
    - -C path is the path to where the calibration files live. If you do not use the -C then the default will be used.
    - -D dark filename.
    - -I illumnation correction filename
  3. The calibrated data file mipsfps_YYY121.fits (YYY a 3-digit integer string, identifying the run number) is a FITS multi-extension image file, one extension per DCE.
  4. Run Xsloper_view and check to make sure data seems reasonable:
5. The calibrated data file mipsfps_YYY121.fits (YYY a 3-digit integer string, identifying the run number) is placed on SSCIST21: /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 sscist21:/home/sscmip/users/waw/fps/fps.doc.
7. The output files CSYYY121.m and CAYYY121.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.
11. End of Campaign I.
The entire process above is repeated for Campaign J.
Results from the IPF filter for Campaign I and Campaign J 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.
The MIPS IT and IST team analyzes the multirun results.

Software Requirements

STINYTIM for PSF generation.
SSC downlink system.
MIPS DAT
IDL for IDL program mipspos.pro for star centroiding.
At JPL, IPF Filter program.

Actions Following Analysis

The MIPS team reviews the MF file from the 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 #12.

Failure Modes and Responses

Failure of one campaign (I or J) to produce useful data
- If one of the runs looks bad, then go back and analyze the data better. We may need to plot the data to look for bad data, we may need to edit the CA file and resend it to the IPF team.
- We might need to ask the IPF team to look closer at their analysis.
- If one set is bad and can not be fixed, then use data from other campaign, if data appear reasonable and change is not large
Results of I & J inconsistent, neither obviously bad, then average the results.
Both results are bad - then reschedule observations.