-
Notifications
You must be signed in to change notification settings - Fork 4
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Preprocessing steps #305
Preprocessing steps #305
Conversation
…nto preprocessing-steps
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This looks good.
It occurs to me that the code assumes that DECam images always come in raw, and that's how we're usually doing it. But you can pull in reduced DECam images. When you do that, how do you specify that the steps_done field should be different from what's in the DECam class?
I think the original idea would be to use a separate Instrument class for processed exposures. |
Refactor the way we request certain preprocessing steps to be done, e.g., applying flat or bias or fringe to certain images.