Super-Boresight Pointing History File (SBPHF) Generation Testing for S12.0 -------------------------------------------------------------------------- F. Masci, 3/1/2005 Purpose: -------- For each raw Boresight Pointing History File (BPHF) associated solely with _IRAC_ AORs, we plan to create a refined version (SBPHF) using the results of astrometric pointing refinement from the post-BCD thread. We have focussed on IRAC due to the availability of robust astrometric match statistics in one or more of it's bands. With a refined BPHF, one can then attempt to refine all IRAC bands self-consistently since all bands observe the sky simultaneously. Plan: ----- For S12.0, we plan to generate the SBPHFs and manually use them (with the pipeline operator's assistance) in end-to-end testing for further offline analysis. S13.0 will attempt to archive and register these for use in subsequent reprocessing of IRAC campaigns. Script Functions: ----------------- The SBPHF generation script ($SIRTF_SCRIPTS/GenSBPHFsForCampaign.pl) performs the following basic functions. * Reads in the following required inputs from the command-line: a campaign string, instrument-FOV (Euler angle offsets) table file and an output directory for the SBPHF products and QA files. * Query for all raw (12-hour based) BPHFs in the specified campaign using the "getBestTelemetryFilesForCampaign" stored procedure (CRs6210,6211). * Query for all AOR-based refined pointing table files in the specified campaign using the "getRefinedPointingTblFilesForCampaign" stored procedure (CR6187). * Sorts all AOR-based refined pointing table files for each input raw (12-hour based) BPHF into unique filelists. * Executes the "gnsbph" module on each input raw BPHF and corresponding refined pointing table list for the entire campaign. * Exits with a report on the actual number of SBPHFs made compared to the total number of raw-BPHF in the campaign. Script Tutorial: ---------------- Can be obtained by executing the script with no command-line arguments, e.g., in the segment test environment: sscpipe1% source /ssctst1/sos1/config/S12.0/downlink/operator.csh sscpipe1% $SIRTF_SCRIPTS/GenSBPHFsForCampaign.pl =============================================================== Script GenSBPHFsForCampaign.pl, Version 1.0 Frank Masci (fmasci@ipac.caltech.edu) Copyright (C) 2005 California Institute of Technology. Last modified 02-01-2005 Purpose: Queries the SODB to create filelists of raw Boresight Pointing History Files (BPHFs) and AOR/ensemble-based refined image pointing tables covering the same time range, reads in from the command-line a namelist, a campaign [char(10)] string, an optional filetype, an Euler-angle offset FOV table for the given instrument, and then executes the "gnsbph" software to generate "Super-Boresight" Pointing History Files (SBPHFs) corresponding to the input BPHFs. Output SBPHFs are written to the directory specified by the "-o" command-line option. Corresponding QA files for each input AOR-based refined pointing table are written to the execution directory. Required environment variables: (These can be set by sourcing the relevant "operator.csh"): WRAPPER_UTILS INFORMIXSERVER TARGETDB SODB_ROLE SIRTF_BIN Usage: GenSBPHFsForCampaign.pl -n [Optional;default=internal params.] -c [Required] -t [Optional;default='pointingHistory'] -f [Required] -o [Required] =============================================================== Input Namelist/Calibration files. --------------------------------- Two configuration files are currently required by the script: * The namelist: "gnsbph.nl". This has been checked into the operations TFS under the IRAC-1_INT POV. If not already there, please see AI-1488. * The _calibration_ file: "instrument_FOV.tbl". This is the latest version that is delivered together with all other IRAC calibrations. Test Procedure: --------------- Here's a suggested step-by-step guide on how to generate a set of SBPHFs for a given campaign. The example below uses campaign IRAC003700. *** Please perform this testing when you have processed a substantial number of AORs in a given campaign through to, and including the post-BCD pointing refinement step (IRAC PlscriptId 27). By substantial, I mean as many AORs as you have ingested for a given test campaign. 1. source /sos/config/$SOS_REL/downlink/operator.csh where $SOS_REL has been pre-defined in the I&T environment. 2. Create a directory, e.g., "superBS/" under a /scr/.. drone partition or area which has >~300MB. This is the maximum you will ever need for a campaign run. 3. cd superBS/ and execute the following: GenSBPHFsForCampaign.pl -n gnsbph.nl -c IRAC003700 -f instrument_FOV.tbl \ -o OutSBPHFs_IRAC003700 | tee LOG_IRAC003700.txt A log of the output will be captured in the file "LOG_IRAC003700.txt". 4. This run will create a subdirectory "OutSBPHFs_IRAC003700/" in the execution directory containing all outputs. e.g., SBPHF.0758376000.08.1.AOR0008700928.ps SBPHF.0758376000.08.1.AOR0008701184.ps SBPHF.0758376000.08.1.pntg SBPHF.0758376000.08.RefndTbl.list SBPHF.0758380300.08.1.AOR0008712192.ps SBPHF.0758380300.03.1.pntg SBPHF.0758380300.03.RefndTbl.list etc.. 5. There will be a QA ".ps" file for every AOR found in the campaign with existing refined pointing table (from post-BCD processing), and a ".pntg" file for each raw BPHF. Cognizants/Contacts: -------------------- Please contact either of the following people if a problem arises, or, if products are ready for validation and analysis. We will be more specifically interested in looking at the ".ps" files (step 5. above) and the contents of the output logs, (e.g., "LOG_IRAC003700.txt" in step 3. above). * Frank Masci (fmasci@ipac.caltech.edu), x3154 * Howard McCallon (hlm@ipac.caltech.edu), x1862