Fix computing unmasked pixels in rmsimage.py#317
Open
AlexKurek wants to merge 1 commit into
Open
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
1 participant
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.
There is a mismatch between local slice coordinates and the global array.
The code uses
np.where(mask[a:b, c:d] == False)to find unmasked pixels. This returns indices relative to the sliced box starting from (0,0).A few lines down, these local coordinates are applied directly to the full image array:
arr[pix_unmasked].It ends up calculating the mean and std for the top-left corner of the entire image instead of the intended sliced region (a:b, c:d).
In case of my 1.5 GB FITS the .gaul files are identical after this, so maybe it is a rare situation.