LSSTApplications
10.0+286,10.0+36,10.0+46,10.0-2-g4f67435,10.1+152,10.1+37,11.0,11.0+1,11.0-1-g47edd16,11.0-1-g60db491,11.0-1-g7418c06,11.0-2-g04d2804,11.0-2-g68503cd,11.0-2-g818369d,11.0-2-gb8b8ce7
LSSTDataManagementBasePackage
|
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:
(where we slipped in a convenient function showMask
to show masks in name-order)
You can add more mask planes:
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")
:
(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:
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:
But you can't actually do much harm:
The version numbers aren't actually compared directly, rather a hash of the contents is computed, so:
(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:
However, as expected,
will raise an exception.
What did I mean by, "conflicts"? Here's an example:
Note that msk
hasn't acquired a P3
plane as plane 1
is already in use.