Bad pixels#3
Open
MurrayForbes wants to merge 3 commits into
Open
Conversation
…reflects the state of the button.
Do error checks on the data in the file before allowing code to overlay the bad pixel markers.
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.
Hristo,
This was prompted by a night where I found a star was drifting on and off a hot pixel, with a noticeable effect on the photometry. Using markers to show each bad pixel will allow the user to (try to) position the FOV so no stars of interest are near a bad pixel.
I intend to write code in Tangra to create the 'bad pixels' file and then also replace each hot pixel with the average value of the surrounding pixels (to be done after the dark and flat corrections have been applied). The 'bad pixels' will be found from hot pixels in a dark frame and cold pixels in a flat frame.