Spitzer Documentation & Tools
MOPEX User's Guide

 

***NEW*** Note that with version 18.5.0 one can use multiprocessing to speed up MOPEX tasks.  The tasks Overlap, Mosaic, Apex (Multi) and Apex User List (Multi) now allow multiprocessing of some steps. In the GUI, this is set in Initial Setup, Multi-Processing Mode.  The options are "on", "off", and "manual".  The default is "on" -- this grabs 3/4 of the available processors.  Setting "manual" lets the user set the number of processors used.  You should see speed-ups of at least 2x. 

 

 If using command-line, add these lines at the top of your namelist:

       do_multiprocess = on | off | manual     default = off

       ncpu_multiprocess = 1                   default = 1

If "manual" is set, set ncpu_multiprocess to the number of processors to use.

6.6.2        APEX QA Modules: APEX QA Settings (Multiframe)

Command Line Equivalent: None

Default Output Directory: <output_dir>

Depends On: None

 

PURPOSE

Set up the input files for the APEX QA Multiframe pipeline.

 

INPUT

Pixel by Size: Check this to set the output pixel size in degrees. The default pixel size depends on the instrument and channel: see the templates for the default sizes.

 

Pixel Size X (deg): Set the X-size of the output pixels in degrees. The pixel size in the X-direction is quoted as a negative value to comply with convention. A positive value will generate an error message. 

Pixel Size Y (deg): Set the Y-size of the output pixels in degrees.

 

Pixel By Ratio: Check this to set the output pixel size by ratio of the input pixel to the output pixel, i.e. to make the output pixels half the size of the input pixels (over-sample the mosaic), set the values of Pixel Ratio X(Y) = 2. The ratio is taken after correction for geometric distortion.

 

Pixel Ratio X: Set the pixel ratio in the X-direction.

Pixel Ratio Y: Set the pixel ratio in the Y-direction.

 

Use PRF File Name: Select this if a single fixed PRF file was used to fit the sources in the APEX Multiframe pipeline

 

Use PRF Map File Name: Select this if a variable PRF map file was used to fit the sources in the APEX Multiframe pipeline.

 

      PRF File Name: The name of the PRF file that was used in source fitting.

      PRF Map File Name:  The name of the PRF Map file that was used in source fitting.

 

Extract Table: Table of extracted sources, usually from an APEX Multiframe or APEX User List Multiframe pipeline. By default, this file is named extract.tbl, but some users may choose to use extract_raw.tbl instead (see Discussion).

 

Delete Intermediate Files: Check this to delete all of the intermediate files created by the APEX QA pipeline. This leaves only the input files and the files created by the final module. This is useful for saving disk space once you are satisfied with your reduction setup. Note that MOPEX will prompt you with a pop-up dialogue box when you set the flow running, to be sure that you meant to select this irreversible option.

 

Use Refined Pointing: Check this to use the alternate FITS pointing keywords created by the offline pointing refinement script (pointing_refine.pl). Do not switch this on unless you have manually run pointing refinement outside of the normal BCD pipeline products. Most users will never use this option, as pointing refinement is not recommended for Spitzer data. If you believe that there is a problem with the pointing of your data with respect to e.g. the 2MASS catalog, please email the Spitzer Helpdesk for assistance.

 

COMMAND LINE INPUT

In the Global Parameters section of the namelist:

MOSAIC_PIXEL_SIZE_X = -0.00033889

MOSAIC_PIXEL_SIZE_Y = 0.00033889

MOSAIC_PIXEL_RATIO_X = 1

MOSAIC_PIXEL_RATIO_Y = 1

PRF_file_name = cal/apex_sh_IRAC1_col129_row129_x100.fits

PRFMAP_FILE_NAME = cal/ch1_prfmap.tbl

EXTRACTION_TABLE = <output_dir>/extract.tbl

delete_intermediate_files = 0

USE_REFINED_POINTING = 0

 

OUTPUT

none

 

DISCUSSION

This module sets up the input files for the APEX QA Multiframe pipeline. If you run APEX QA and find that some sources were not subtracted in the final image, check whether the Select module was run in the APEX (User List) Multiframe pipeline. It is possible that some extracted sources were thrown out by the Select condition. In this case you may choose to use extract_raw.tbl as the Extract Table.