70µm NF Focal Plane Survey, Fine

Data Reformatting Requirements

Array Data Desired:

70 µm Narrow

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-911: 70 µm Darks
• MIPS-313: 70 µm Narrow illumination correction
• MIPS-137: 70 µm Narrow Field Focal Plane Survey, Coarse.
• IPF run is to occur after FTU# 14 (PAC filer and OET CTA Frame Tool inputs)

Calibration Dependencies

• Calibration product needed:
• 70 µm Narrow 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 118 for the 70 µm NF array. .
  • 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: calibrated data file with appropriated header keywords. The name of this file will be "mips_YYY118.fits", where where "YYY" is 3-digit string denoting run number, and "118" is IPF code for 70 µm NF data. This file is sent to B. Wheaton's centroiding program.
• Output from Centroid program: Centroid data file. The calibrated data is centroided and the centroided data filename is CAYYY118.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 the coarse survey result in significant changes to these files, these files will not be changed for the fine survey.

Data Analysis

Task 138 is run both in Campaign R and Campaign V. The results from both runs are used to update Frame Table # 15.
• Process data for Campaign R:
  1. JPL MIPL transfers downlink data to SSC.
  2. SSC downlink ops processes data and 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_YYY118.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_YYY118.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 sscist21L /home/sscmip/users/waw/fps/fps.doc.
  7. The output files CSYYY118.m and CAYYY118.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 R.
• The entire process above is repeated for Campaign V.
• Results from the IPF filter for Campaign R and Campaign V 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

• 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

• After each run 138-R and 138-V the MIPS team recieves the results from the IPF team and reviews them.
• The MIPS team reviews the MF file from the multi-run IPF 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 #15.

Failure Modes and Responses

1. Failure of one campaign (R or V) 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
2. Results of R & V inconsistent, neither obviously bad, then average the results.
3. Both results are bad - then reschedule observations.

Additional Notes