You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Brought up in a discussion with @aleberti in this issue here: #2331
We added the InvalidPixelHandler as last step of CameraCalibrator when doing the dl0 → dl1 step.
That prevents applying it on input data that does not contain DL0 (e.g. DL1 images loaded with the HDF5EventSource or a custom source as is the case for the MAGIC plugin).
I think we could move the InvalidPixelHandler application from the CameraCalibrator to the ImageProcessor to enable applying it also on DL1 input.
Brought up in a discussion with @aleberti in this issue here: #2331
We added the
InvalidPixelHandler
as last step ofCameraCalibrator
when doing the dl0 → dl1 step.That prevents applying it on input data that does not contain DL0 (e.g. DL1 images loaded with the
HDF5EventSource
or a custom source as is the case for the MAGIC plugin).I think we could move the
InvalidPixelHandler
application from theCameraCalibrator
to theImageProcessor
to enable applying it also on DL1 input.@kosack what do you think?
The text was updated successfully, but these errors were encountered: