This issue summarizes the suggestion for camera and pointing calibration API discussed in the ctapipe-dev call (5.4.2024) and aims to divide the implementation of the camera and pointing calibration API into sub-tasks, which will be addressed in dedicated PRs.
[x] Processing (non-gainselected) calibration data using the process-tool. #2529 by @Hckjs
[x] Add an image extractor for the variance of the waveforms. #2543 @ctoennis
[x] Add API for the statistical calculation of pixel-wise values over a given time interval (mean, median, variance, std …), i.e. StatisticsAggregator. Different aggregators can be based on numpy/scipy; astropy sigma clipping #2554 @TjarkMiener
[x] Adjust StatisticsAggregator for star tracking purposes @ctoennis
[ ] Add API for the CalibrationCalculator, which holds different subcomponents for the calculation of camera coefficients, e.g. FFactor method. #2609 @TjarkMiener
[ ] Add a pointing correction subcomponent of CalibrationCalculator @ctoennis
[ ] Implementation of orchestrating tools and workflows (probably in calibpipe directly) @TjarkMiener @ctoennis
Related issues: #1041 #1147 #1836 #1037 #2439
Please comment in case something is missing or we should follow a different path forward @Hckjs @FrancaCassol @mexanick. Discussion on specific sub-tasks can be moved to a dedicated issue.
This issue summarizes the suggestion for camera and pointing calibration API discussed in the ctapipe-dev call (5.4.2024) and aims to divide the implementation of the camera and pointing calibration API into sub-tasks, which will be addressed in dedicated PRs.
process-tool. #2529 by @HckjsStatisticsAggregator. Different aggregators can be based on numpy/scipy; astropy sigma clipping #2554 @TjarkMienerStatisticsAggregatorfor star tracking purposes @ctoennisCalibrationCalculator, which holds different subcomponents for the calculation of camera coefficients, e.g. FFactor method. #2609 @TjarkMienerCalibrationCalculator@ctoenniscalibpipedirectly) @TjarkMiener @ctoennisRelated issues: #1041 #1147 #1836 #1037 #2439
Please comment in case something is missing or we should follow a different path forward @Hckjs @FrancaCassol @mexanick. Discussion on specific sub-tasks can be moved to a dedicated issue.