LSST Applications  21.0.0-155-g0c33f26d+0510337a8f,22.0.0+000ed19a8b,22.0.0+06dd0f93dc,22.0.0+8ca4520534,22.0.0+c025529d5f,22.0.0+dfc68d4d09,22.0.0+e6ee2fa291,22.0.1-1-g7d6de66+c46fc0dfe8,22.0.1-1-g87000a6+2036d5eaca,22.0.1-1-g8e32f31+e6ee2fa291,22.0.1-13-g5845b92+99fc5a924b,22.0.1-14-g6272d78+ec7fbbaa4d,22.0.1-2-g92698f7+000ed19a8b,22.0.1-2-ga9b0f51+dfc68d4d09,22.0.1-21-g5bd0cb7e+18dfaba0c2,22.0.1-22-g41e933f+cc8a8bd2b1,22.0.1-23-ged5e717+c46fc0dfe8,22.0.1-24-g4fd6b65+3e3a8936a6,22.0.1-25-gbfca4b99+b4523d8147,22.0.1-3-g59f966b+0dff74cfa2,22.0.1-3-g849a1b8+7d70fd69ff,22.0.1-3-g85f6b2a+dfc68d4d09,22.0.1-3-geb91c39+c46fc0dfe8,22.0.1-36-g99137b0eb+ec953d57b4,22.0.1-4-g037fbe1+6eccae7d65,22.0.1-4-g243d05b+407143e2a6,22.0.1-4-g2c3f5ac+2e8da71d76,22.0.1-4-g35e927a+3ce437aeab,22.0.1-4-gf0e1808+069725d854,22.0.1-5-g096abc9+fb28b9dcc5,22.0.1-5-g15c806e+7e58257bcf,22.0.1-7-gba73697+7e58257bcf,22.0.1-8-g903eb1c+c46fc0dfe8,master-g6e05de7fdc+bdf610cf3e,master-g99da0e417a+c025529d5f,w.2021.43
LSST Data Management Base Package
How Mask Planes are handled in afw

There is no universally-adopted standard on how the bits in a mask are to be interpreted, and accordingly the LSST code tries to be flexible.

The mapping name --> bitmask is defined by a dictionary in the Mask class (e.g. EDGE -> 4 -> 2^4 == 0x10).

When Mask is created, the dictionary is initialised with a number of useful values; a convenience function is provided to list them:

>>> import lsst.afw.image as afwImage
>>> Mask = afwImage.MaskU # Mask will make a "MaskU", a 16-bit Mask
>>> msk = Mask()
>>> msk.printMaskPlanes()
Plane 0 -> BAD
Plane 3 -> CR
Plane 5 -> DETECTED
Plane 6 -> DETECTED_NEGATIVE
Plane 4 -> EDGE
Plane 2 -> INTRP
Plane 1 -> SAT
>>>
>>> def showMask(msk, msg="???"):
... print "%-15s" % msg, " ".join(sorted([str(x) for x in msk.getMaskPlaneDict().items()]))
std::vector< SchemaItem< Flag > > * items
double x
table::Key< int > a
Backwards-compatibility support for depersisting the old Calib (FluxMag0/FluxMag0Err) objects.
A base class for image defects.

(where we slipped in a convenient function showMask to show masks in name-order)

You can add more mask planes:

>>> rhl = msk.addMaskPlane("RHL")
>>> showMask(msk, "msk")
msk ('BAD', 0) ('CR', 3) ('DETECTED', 5) ('DETECTED_NEGATIVE', 6) ('EDGE', 4) ('INTRP', 2) ('RHL', 7) ('SAT', 1)
>>> msk |= Mask.getPlaneBitMask("RHL") # set the RHL bits

That last example was a little misleading; I could just as well have written Mask.addMaskPlane("RHL") as addMaskPlane is a class static function — it adds the named mask plane to all masks. I can remove a mask plane just as easily with Mask.removeMaskPlane("RHL"):

>>> Mask.removeMaskPlane("RHL")
showMask(Mask(), "default Mask")
default Mask ('BAD', 0) ('CR', 3) ('DETECTED', 5) ('DETECTED_NEGATIVE', 6) ('EDGE', 4) ('INTRP', 2) ('SAT', 1)

(note that getMaskPlaneDict is not static; we needed to create an object to be able to call it).

Unfortunately we have a problem; we set the beloved RHL bit in msk, but now it's gone. The resolution is that each mask remembers the version of the mask dictionary that was current when it was created, so:

>>> showMask(msk, "msk")
msk ('BAD', 0) ('CR', 3) ('DETECTED', 5) ('DETECTED_NEGATIVE', 6) ('EDGE', 4) ('INTRP', 2) ('RHL', 7) ('SAT', 1)

If you want to get rid of msk's RHL bit, use msk.removeAndClearMaskPlane("RHL") or msk.removeAndClearMaskPlane("RHL", True) if you want to drop RHL from the default mask too. This does two things: It clears any RHL bits that are set in the Mask (it isn't static, so it can do that), and it removes RHL from the Mask's dictionary.

It's clear that you can make things inconsistent if you try:

>>> Mask.clearMaskPlaneDict()
>>> p0 = Mask.addMaskPlane("P0")
>>> p1 = Mask.addMaskPlane("P1")
>>> print "Planes:", p0, p1, Mask.addMaskPlane("P1") # a no-op -- re-adding a plane has no effect
Planes: 0 1 1
>>> msk = Mask()
>>> Mask.removeMaskPlane("P0")
>>> Mask.removeMaskPlane("P1")
>>> showMask(Mask(), "default Mask")
default Mask
>>> showMask(msk, "msk")
msk ('P0', 0) ('P1', 1)
>>> p1 = Mask.addMaskPlane("P1")
>>> p0 = Mask.addMaskPlane("P0")
>>>
>>> msk2 = Mask()
>>> showMask(msk2, "msk2")
msk2 ('P0', 1) ('P1', 0)

But you can't actually do much harm:

>>> msk |= msk2
Traceback (most recent call last):
File "<stdin>", line 1, in <module>
File "/Users/rhl/LSST/afw/python/lsst/afw/image/imageLib.py", line 5415, in __ior__
_imageLib.MaskU___ior__(*args)
lsst.pex.exceptions.exceptionsLib.LsstCppException: 0: lsst::pex::exceptions::RuntimeErrorException thrown at src/image/Mask.cc:896 in void lsst::afw::image::Mask<unsigned short>::checkMaskDictionaries(const lsst::afw::image::Mask<afwImage::MaskPixel> &)
0: Message: Mask dictionary versions do not match; 3 v. 6
std::shared_ptr< RecordT > src
Definition: Match.cc:48
def line(points, frame=None, origin=afwImage.PARENT, symbs=False, ctype=None, size=0.5)
Definition: ds9.py:104
std::int32_t MaskPixel
default type for Masks and MaskedImage Masks
std::vector< Tracepoint > Traceback
Definition: Exception.h:95

The version numbers aren't actually compared directly, rather a hash of the contents is computed, so:

>>> showMask(msk, "msk")
msk ('P0', 0) ('P1', 1)
>>> msk.removeAndClearMaskPlane("P0")
>>> msk.removeAndClearMaskPlane("P1")
>>> p0 = Mask.addMaskPlane("P0")
>>> p1 = Mask.addMaskPlane("P1")
>>> showMask(msk, "msk")
msk ('P0', 1) ('P1', 0)
>>> msk |= msk2

(We removed the errant planes from msk, then re-added the ones that are already defined in the default dictionary)

Adding planes has no such difficulties, so they are added to all pre-existing dictionaries that don't have conflicts:

>>> msk = Mask()
>>> Mask.addMaskPlane("P2")
>>> showMask(msk, "msk")
msk ('P0', 1) ('P1', 0) ('P2', 2)

However, as expected,

>>> msk2 = Mask()
>>> msk.removeAndClearMaskPlane("P2")
>>> msk |= msk2

will raise an exception.

What did I mean by, "conflicts"? Here's an example:

>>> Mask.removeMaskPlane("P0")
>>> Mask.addMaskPlane("P3")
>>> Mask.addMaskPlane("P0")
>>> showMask(msk, "msk")
msk ('P0', 1) ('P1', 0) ('P2', 2)
>>> showMask(Mask(), "default Mask")
default Mask ('P0', 3) ('P1', 0) ('P2', 2) ('P3', 1)

Note that msk hasn't acquired a P3 plane as plane 1 is already in use.