This page details the meaning of the bitmasks provided with Data Release 9 of the Legacy Surveys. The bits are
enumerated as a power (i.e. 7
written in a column of bits means two-to-the-power-of-7).
MASKBITS
These definitions apply to both the values in the coadd/*/*/*maskbits*
files and to MASKBITS
columns in the Tractor
and sweeps catalogs. See also the legacypipe bitmask definitions.
Bit |
Name |
Description |
---|---|---|
0 |
|
touches a pixel that is outside the |
1 |
|
touches a pixel within half of the locus of a radius-magnitude relation. Set for Tycho sources with |
2 |
|
touches a pixel that was saturated in at least one \(g\)-band image |
3 |
|
touches a pixel that was saturated in at least one \(r\)-band image |
4 |
|
touches a pixel that was saturated in at least one \(z\)-band image |
5 |
|
touches a pixel that has any of the |
6 |
|
touches a pixel that has any of the |
7 |
|
touches a pixel that has any of the |
8 |
|
touches a pixel in a |
9 |
|
touches a pixel in a |
10 |
|
touches a pixel in a blob where we "bailed out" of source fitting |
11 |
|
touches a pixel within the locus of a radius-magnitude relation. Set for Gaia stars with G < 16. The |
12 |
|
touches a pixel in an SGA large galaxy |
13 |
|
touches a pixel in a globular cluster |
14 |
|
touches a pixel that was saturated in at least one \(i\)-band image (always zero prior to DR10) |
15 |
|
touches a pixel that has any of the |
FITBITS
A bit-mask detailing any peculiarities regarding how a source was fit. See also the legacypipe bitmask definitions and the
issue that prompted the development of FITBITS
.
Bit |
Name |
Description |
---|---|---|
0 |
|
the source was forced to be type PSF |
1 |
|
the source had its background levels independently fit |
2 |
|
the source hit the radius limit during fitting (based on the limits for galaxy models in the Tractor code) |
3 |
|
the source hit the Sersic index limit during fitting (e.g., see the Sersic model limits in the Tractor code) |
4 |
|
the source was not fit (all parameters for the source were frozen at the reference catalog values) |
5 |
|
the source is a bright star (see also |
6 |
|
the source is a medium-bright star (see also |
7 |
|
the source is a Gaia source |
8 |
|
the source is a Tycho-2 star |
9 |
|
the source is an SGA large galaxy |
10 |
|
fitting the source shifted its position by > 1 arcsec |
11 |
|
fitting the source shifted its position by > 2.5 arcsec |
12 |
|
the source was a Gaia source that was treated as a point source |
13 |
|
the source was found during iterative detection |
ALLMASK_X
/ANYMASK_X
ANYMASK_X
denotes a source that touches a bad pixel in any of a set of overlapping X
-band images whereas
ALLMASK_X
denotes a source that touches a bad pixel in all of a set of overlapping X
-band images.
See, also, the legacypipe bitmask definitions. The
ANYMASK
and ALLMASK
bit masks are defined as follows, mostly from the CP (NOIRLab Community Pipeline) Data Quality bits,
which we map to the values in the table.
Bit |
Name |
Description |
---|---|---|
0 |
|
bad columns, hot pixels, etc. |
1 |
|
saturated |
2 |
|
interpolated |
4 |
|
single exposure cosmic ray |
6 |
|
bleed trail |
7 |
|
multi-exposure transient |
8 |
|
edge pixel |
9 |
|
edge pixel |
11 |
|
marked as touching an outlier pixel by |
WISEMASK_W1
/WISEMASK_W2
WISEMASK_W1
and WISEMASK_W2
have identical bit definitions, the only difference is that WISEMASK_W1
applies to masking in the W1 band
and WISEMASK_W2
to masking in the W2 band.
Bit |
Name |
Description |
---|---|---|
0 |
|
Bright star core and wings |
1 |
|
PSF-based diffraction spike |
2 |
|
Optical ghost |
3 |
|
First latent |
4 |
|
Second latent image |
5 |
|
AllWISE-like circular halo |
6 |
|
Bright star saturation |
7 |
|
Geometric diffraction spike |
Aaron Meisner's unWISE documentation details how these masks were derived.
CCD_CUTS
The survey CCDs and forced photometry files include a bitmask ccd_cuts
that
is used by the legacypipe code to discard CCDs that have low-quality observations before processing imaging for the Legacy Surveys. Any observations with
non-zero vales of ccd_cuts
are discarded prior to processing.
In this table, the column
names
are as they appear in, e.g., the survey CCDs file. The overall zero-points (zpt0
) are:
\(g, r\) = [25.74, 25.52] for 90Prime (BASS)
\(z\) = 26.20 for Mosaic-3 (MzLS)
\(g, r, z\) = [25.08, 25.29, 24.92] for DECam (DECaLS)
Bit |
Name |
Description |
---|---|---|
0 |
|
Some error from the legacyzpts code (e.g., the CP had a WCS error, usually due to being very shallow) |
1 |
|
Not a \(g\)-, \(r\)- or \(z\)-band observation |
2 |
|
Mosaic-3 one-third-pixel interpolation problem |
3 |
|
Exposure time < 30 seconds |
4 |
|
Number of matching CCDs < 20 |
5 |
|
Zeropoint for CCD is different than the average for the exposure: abs( |
6 |
|
Zeropoint is too low: |
7 |
|
Zeropoint is too high: |
8 |
|
Sky is too high; |
9 |
|
Exposure is listed in the |
10 |
|
Photometric calibration RMS is too large: |
11 |
|
Astrometric calibration RMS is too large: rms (\(\sqrt(\mathtt{ccdrarms^2 + ccddecrms^2})\) > 0.4 arcsec for DECam; 0.2 arcsec for 90Prime; 0.1 arcsec for Mosaic-3 |
12 |
|
Bad seeing measure: (seeing < 0 arcsec OR seeing > 3.0 arcsec), where, e.g., |
13 |
|
Defined as |
14 |
|
Depth cut code (this is run after the other cuts) |
15 |
|
Remove full exposures if more than 70% of the CCDs are cut |
16 |
|
Flagged as bad in DES |
Some of the exact values used to create the CCD_CUTS
bitmask are recorded in the legacyzpts
code for 90Prime, Mosaic-3 and DECam.