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
Please describe the use case that requires this feature.
For calculating the pedestal level (per sample), the charge median needs to be divided by the window width of the extractor. Since charge extraction and calculation of camera calibration coefficients are now separated, we'd need to propagate the information of the image extraction parameters in the metadata.
Describe the solution you'd like
Add the parameters of the image extractor in the metadata.
Describe alternatives you've considered
Use the same config file for the process-tool and camcalib-calculation-tool and read the parameters from the config.
Additional context
Maybe the information is already stored somewhere in the data format. If so, please point me there. Thanks!
The text was updated successfully, but these errors were encountered:
Use the same config file for the process-tool and camcalib-calculation-tool and read the parameters from the config.
That sounds error prone since you would have to ensure you sync the config files, so I agree this should be propagated in the table metadata or as a table like /configuration/process. This is also a more general problem: right now the pipeline configuration info only goes into the provenance log, which is not really intended to be read by another processing step, so it would be good to write it somewhere properly.
Please describe the use case that requires this feature.
For calculating the pedestal level (per sample), the charge median needs to be divided by the window width of the extractor. Since charge extraction and calculation of camera calibration coefficients are now separated, we'd need to propagate the information of the image extraction parameters in the metadata.
Describe the solution you'd like
Add the parameters of the image extractor in the metadata.
Describe alternatives you've considered
Use the same config file for the
process
-tool and camcalib-calculation-tool and read the parameters from the config.Additional context
Maybe the information is already stored somewhere in the data format. If so, please point me there. Thanks!
The text was updated successfully, but these errors were encountered: