Implementing pixel level bitmasking #181
Draft
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR implements pixel level bitmasks to keep track of the reasons why some pixels are being masked during a reduction run. Additionally two global bitmasks are also implemented,
DRPQUALandDRPSTAGE, to keep track of the overall quality of the reduction and the stage of the reduction, respectively.Main changes are:
lvmdrp.utils.bitmaskRSSandImageclassesDRPQUALheader keyword toRSSandImageclasses (closes drpqual not populated properly in Sframe and hence not in drp_all.fits #124 and closes add the QUALITY header keyword to the primary header of reductions #125)DRPSTAGEheader keyword toRSSandImageclasses