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-27598: Many images have few or no good pixels when running ptc.py #66
Conversation
config/ptcIsr.py
Outdated
config.isr.doNanMasking: True | ||
config.isr.doInterpolate: True |
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.
Colons instead of =
? Does that even run?
config/ptcIsr.py
Outdated
config.isr.doDefect = True | ||
config.isr.doNanMasking: True | ||
config.isr.doInterpolate: True | ||
config.isr.doSaturation=False |
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.
Spaces around operator
config/ptcIsr.py
Outdated
config.isr.doInterpolate: True | ||
config.isr.doSaturation=False | ||
config.isr.doSaturationInterpolation = False | ||
config.isr.growSaturationFootprintSize = 0 # We want the saturation spillover: it's good signal. |
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.
That comment feels like it's copied and pasted from a crosstalk config.
config.isr.doAssembleCcd = True | ||
config.isr.doBias = True | ||
config.isr.doVariance = True | ||
config.isr.doLinearize = True |
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.
I am not sure we want that on, do we? Isn't the most common use-case here that we'll be wanting the uncorrected values, and only turning it back on to check the models we've built, meaning the default should be False
? Or is there other thinking here?
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.
I agree with you; however, Chris points out that more of a linearity issue than PTC and opined that leaving it true here makes sense.
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.
Does running the linearity generation code have its own config, or does it share this one? I think I really need to catch up on how Gen3 configs and contracts and all that work now 😬
@czwa what are your thoughts on this?
@@ -0,0 +1,20 @@ | |||
# ISR for inputs of Photon Transfer Curve task |
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.
Comment on the whole config: what about Craig's suggestion of isr.edgeMaskLevel='AMP'
?
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.
And is the the default the same as his suggestion of isr.numEdgeSuspect=10
?
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.
I'll add these two as defaults.
2b104c5
to
6971aa3
Compare
No description provided.