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
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.
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. Add calibration calculators #2609@TjarkMiener
Add a pointing correction subcomponent of CalibrationCalculator@ctoennis
Implementation of orchestrating tools and workflows (probably in calibpipe directly) @TjarkMiener@ctoennis
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.
The text was updated successfully, but these errors were encountered:
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
. Change R1- and DL0-waveforms shape to (n_channels, n_pixels, n_samples) #2529 by @HckjsStatisticsAggregator
. Different aggregators can be based on numpy/scipy; astropy sigma clipping Add StatisticsAggregator API #2554 @TjarkMienerStatisticsAggregator
for star tracking purposes @ctoennisCalibrationCalculator
, which holds different subcomponents for the calculation of camera coefficients, e.g. FFactor method. Add calibration calculators #2609 @TjarkMienerCalibrationCalculator
@ctoenniscalibpipe
directly) @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.
The text was updated successfully, but these errors were encountered: