-
Notifications
You must be signed in to change notification settings - Fork 20
Improvement of the gain calibration + Bugfix of charge extraction #214
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
Improvement of the gain calibration + Bugfix of charge extraction #214
Conversation
…lt in SPE combined algo -better management of SPE res used for PS method
…ned was pointing the last slice
… even if selected_gain_channel is none, the expected sample axis is wafevorms.shape[-1]. Then if we provide (n_events,n_pix,n_sample) the output is (n_events, n_pix)
…tainers I/O methods + unit test fix
improve behavior if event_per_slice > n_events iin data
Codecov Report❌ Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## main #214 +/- ##
==========================================
+ Coverage 53.36% 53.78% +0.41%
==========================================
Files 76 76
Lines 6234 6264 +30
==========================================
+ Hits 3327 3369 +42
+ Misses 2907 2895 -12 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
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.
Thanks a lot, @guillaumegrolleron ! It looks all good to me. I just note that the dimensions of the ChargesContainer (charges and peaks) changed from 4 to 3. I guess it can create misbehaving side effects. Are we good about that ?
Hi @jlenain, |
|
Hum, just reading the modified code, at https://github.com/cta-observatory/nectarchain/pull/214/files#diff-312de2737781494f8f84079d289befcf6226569609a674d088050dee94082f52R604. We have |
|
Testing the script
|
Before return an array of shape |
Thanks! It is fixed |
Argh, I should think a bit more before writing comments on GitHub, it all makes sense, thanks a lot ! |
|
Hi @guillaumegrolleron ! I tested again several scipts using this PR and everything seem to run fine, thanks a lot again ! |
Hi @jlenain, Thank you for the review! |
…a-observatory#214) * change defaut value of n and pp from HHV the free fit * user script to produce ICRC2025 results * Bug fix FF SPE combined * add gain err to photostat method -> propagation of SPE resolution error * follows photostat error * logging improbemeltb * fix name bug in charge makers * -change pp and n to be taken from config file instead of SPE HHV result in SPE combined algo -better management of SPE res used for PS method * bugfix : wrong position of the yeild within a loop -> generator returned was pointing the last slice * typo * bugfix : when extracting charge and peak time with ctapipe extractor, even if selected_gain_channel is none, the expected sample axis is wafevorms.shape[-1]. Then if we provide (n_events,n_pix,n_sample) the output is (n_events, n_pix) * imrove unit test to detect the issue related to charge extraction * imporove debugging of scripts * formatting * fix pedestal makers and component according to last update of the containers I/O methods + unit test fix * linter * fix unit test of charge and waveforms makers improve behavior if event_per_slice > n_events iin data * fix gain pstat strict arguments --------- Co-authored-by: Guillaume Grolleron <[email protected]>
Small improvement of the gain calibration pipeline regarding the last results presented at ICRC2025
The SPE fit parameters in yaml file are currently the most valid.
It most concerns photo-statistic code, where errors on gain are now estimated, and the possibility to use SPE resolution computed from a different SPE fit approach is now properly managed.
Bugfix: ChargesContainers.from_hdf5 -> when loading sliced, only the last one was returned
Bugfix: charge extraction through ctapipe extractor -> wrong output shape (see #215)
This should fix issues raised by @tibaldo, and @hashkar