Skip to content
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

DM-6147 #13

Merged
merged 1 commit into from
May 23, 2016
Merged

DM-6147 #13

merged 1 commit into from
May 23, 2016

Conversation

r-owen
Copy link
Contributor

@r-owen r-owen commented May 19, 2016

No description provided.

@r-owen r-owen changed the title DM-6157 DM-6147 May 19, 2016
@@ -619,7 +625,7 @@ def getIsrExposure(self, dataRef, datasetType, immediate=True):
return exp

def saturationDetection(self, exposure, amp):
"""!Detect saturated pixels and mask them using mask plane "SAT", in place
"""!Detect saturated pixels and mask them using mask plane config.saturatedMaskName, in place
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I like this change!

Copy link
Contributor Author

@r-owen r-owen May 20, 2016

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks. I'm not convinced this should be a config param, but since it is, the old docs were wrong.

@parejkoj
Copy link
Contributor

I feel like there should be a test that does both saturation and suspect detection, to help define how those two interact. Whether that should live in testSuspectMasking.py or some other file, I'm not sure, but I feel like it's an important integration test. It would call isrTask.run(), but maybe that suggests that the stuff inside the "for amp in ccd:" should live in a "do_amp()" method, which can then be tested separately?

@r-owen
Copy link
Contributor Author

r-owen commented May 20, 2016

I would like to leave that for DM-6161 if at all possible. We don't presently have any unit test for IsrTask and we really need one.

@parejkoj
Copy link
Contributor

Ok: glad there's a ticket about it. Should I (or you?) add my note above about the possible refactor to that ticket?

@r-owen
Copy link
Contributor Author

r-owen commented May 20, 2016

I don't understand about the refactoring. Perhaps you should add the note or explain it to me in person.

@r-owen r-owen merged commit 3e40857 into master May 23, 2016
@ktlim ktlim deleted the tickets/DM-6147 branch August 25, 2018 06:44
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants