MOPEX Online Manual

Appendix 2: Fatal Bit Patterns

It is highly likely that when you reduce your Spitzer data, you will include at least one set of mask files as input into the pipeline. The pixels in the mask files all contain coded information, or "bit definitions", depending on the status of a particular pixel. For example, a pixel with bit 10 flagged in the IRAC channel 1 pmask file indicates that that particular pixel in the IRAC channel 1 array has an excessive dark current that will affect all observations, while bit 14 indicates that the pixel is dead. For a full list of bit definitions, see the links from the IRAC and MIPS Data Products pages, and Chapter 9 of the IRS Data Handbook (pdf). When running MOPEX, you need to decide which of these codes you wish to set as "fatal", i.e. which of the flagged problems you consider so bad that the corresponding pixel in your data frame should be discarded. This is done by specifying a "Fatal Bit Pattern" as follows:

Fatal Bit Pattern = 2^{(value of 1st required fatal bit)} + 2^{(value of 2nd fatal bit)} + .... + 2^{(value of nth fatal bit)}

e.g. if you wished to set bits 7, 8, 9, 10 and 14 as fatal for your IRAC PMask file then you would set your PMask Fatal Bit Pattern to: (2⁷ + 2⁸ + 2⁹ + 2¹⁰ + 2¹⁴) = 18304, and you would include the following line in your namelist:

PMask_Fatal_BitPattern = 18304

The Fatal Bit Patterns for the other mask files can be set with the keywords DCE_Status_Mask_Fatal_BitPattern and RMask_Fatal_BitPattern. The most up-to-date recommended Fatal Bit Patterns for each instrument are listed in the relevant sample namelists linked at the bottom of the MOPEX page.

Contents

Previous: Appendix 1: Full List of MOPEX scripts

Next: Appendix 3: Full List of Modules in MOPEX