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-40128: Fix brighter-fatter loading errors #279
Conversation
* Move calibration date searches to runQuantum with the rest of the header provenance. * Handle inputs that change name during the header provenance (only brighter-fatter kernels currently). * Retain header validation checks in the run method.
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.
Looks fine. Feel free to ignore the nitpicky suggestions.
python/lsst/ip/isr/isrTask.py
Outdated
|
||
if brighterFatterKernel is None: | ||
# This was requested by the config, but none were found. | ||
raise RuntimeError("No brighter-fatter kernel was supplied.") | ||
|
||
if brighterFatterKernel is not None and not isinstance(brighterFatterKernel, numpy.ndarray): |
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.
Can't this just be elif not isinstance(brighterFatterKernel, numpy.ndarray)
now?
|
||
# These inputs change name during this step. These should | ||
# have matching entries in the additionalInputDates dict. | ||
additionalInputs = [] |
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.
Not that it matters much but couldn't you just set this to list(inputs.keys())
to start with and append to/extend it?
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 would certainly work the same, but I think it would require some variable name and comment rewrites. I think in the long term, this can eventually go away if all cameras switch to IsrCalib
style brighter-fatter kernels.
Simplify header provenance code and fix BF errors: