Joint Astronomy Centre
Show document only
JAC Home
JCMT
UKIRT
Contact info
JAC Divisions
OMP
Outreach
Seminars
Staff-only Wiki
Weather
Web Cameras
____________________

Observing at UKIRT
Service Observing
UKIDSS Survey Operations
Target of Opportunity
Calibration & Utilities
UKIRT Archive
Public wiki
Accessing Flexed Data
Accessing UKIDSS Data
Reduction Cookbooks
Telescope
Site Quality
Instruments
Newsletter/Publications
UKIRT Faults
JAC Safety Manual
Eliminating Data with Bad Pixel Masks

JACH | JCMT | UKIRT | Computer Services | USG

Eliminating Data with Bad Pixel Masks

A bad pixel mask is a data frame that indicates which pixels on the detector array are good and which bad. It may be used to mask off faulty detectors. Normally the mask contains 0 to indicate good, and 1 to indicate bad. It should be the same size as the area of the data array read by the data acquisition system. Bad pixel masks are held in the $cgs4_masks/ directory.

Besides flagging faulty detectors, a bad pixel mask can also be used for masking off un-illuminated areas at the edge of the detector array.

A bad pixel mask can be created by the software using one of three methods:

  1. By setting all the data values lying outside a given range to bad. Some sample data are plotted as a histogram, and the required range is selected using a cursor. This is called `thresholding'.
  2. By setting all the pixels outside a given window on the detector array to bad.
  3. By thresholding an error array.

Masks generated by any method may be combined together.

The data reduction system can change masks by responding to a `DRMASK maskname' command entered into the data reduction queue. There is also an option to specify no mask at all (#).

Bad pixel masks can be any size or shape. When a mask is created, it assumes the same size and shape as the data from which it was created. The size and shape of the mask created by windowing can also be specified. Of course, allowing masks to be any size means there is a chance that the wrong type of mask may be specified when reducing some data. The data reduction system will check the bad pixel mask against each integration being reduced to ensure it is the right size and will report if it is not.

Portable--CGS4DR is shipped with several bad pixel masks specific to the current arrays:

fpa61
--- Masks the known dead, hot and variable pixels for the 58 62 InSb array in CGS4.
fpa61_lc
--- To be used with the CGS4 long focal length camera observations when the whole array is illuminated.
fpa61_75
--- To be used with the CGS4 short focal length camera observations and the 75 or 150 lines per millimetre gratings.
alice_fpa42
--- Masks the known dead, hot and variable pixels for the InSb 256256 array in IRCAM3.
fpa46_short
--- Masks the known dead, hot and variable pixels for the InSb 256256 array in CGS4 using the short camera.

For the echelle, it is better to make your own windows as the illuminated area is a strong function of the grating angle.

Note that there are problems with pixel conventions when manipulating masks. Some packages use the STARLINK pixel convention and some the Figaro convention which differ by 0.5 in each direction. Combining masks can lead to errors. The usual way around this problem is to use the Figaro functions XCSUB and YCSUBgif[2]To be released `real soon now'! to adjust to the appropriate origin. Portable--CGS4DR conforms to the Figaro pixel convention where the data is centered on the half-integer values i.e. the origin is at (0.5,0.5).


JACH | JCMT | UKIRT | Computer Services | USG


Last Modification Date 1996/03/12 - Last Modification Author: frossie
Phil Daly (pnd@jach.hawaii.edu)
Contact: Tom Kerr. Updated: Wed Oct 6 12:07:27 HST 2004

Return to top ^