- 
                Notifications
    You must be signed in to change notification settings 
- Fork 20
Fix bug in ChargeDistributionFilter for pedestal maker #213
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
Fix bug in ChargeDistributionFilter for pedestal maker #213
Conversation
| Codecov Report❌ Patch coverage is  
 Additional details and impacted files@@           Coverage Diff           @@
##             main     #213   +/-   ##
=======================================
  Coverage   51.79%   51.79%           
=======================================
  Files          78       78           
  Lines        6505     6505           
=======================================
  Hits         3369     3369           
  Misses       3136     3136           ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
 | 
| Hi @tibaldo , Thanks a lot for that, it all makes sense ! | 
| Hi @tibaldo ! | 
| 
 Hi @tibaldo , Thanks ! | 
…libration files (cta-observatory#207) * Add script to obtain metadata of `ctapipe` and `nectarchain`. Taken from `lstcam_calib` with minor adaptations for `nectarchain`. * added group name as option to HDF5 readout, particularly useful for pedestal output files that use various groups to store data * first attempt for a Tool that writes a category A output file from NectarCAM containers * Add example script for the usage of the CalibrationWriterNectarCAM tool * ensure that filled arrays have the correct type (based on `lstcam_calib` example file) * do one-padding instead of zero-padding to expand arrays related to pixel status with missing pixels (so a missing pixel = True for those that are added, i.e. due that were not included due to hardware failure) * fixed hardware failing pixel status bug
…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]>
| Hi @jlenain : I merged the latest main branch and tested on my Mac, which worked fine. There are some CI errors though, do you have any ideas about the cause and how to solve them? | 
| 
 It is a circular import issue due to the import of  Could you please let me know which version you currently have for  | 
| I have ZODB 6.0.1 on MacOS Sequoia 15.6.1. | 
| 
 Thanks ! | 
| Hi @tibaldo , | 
| Thanks a bunch @jlenain, the PR is ready for merging I think | 
| Thanks a lot, @tibaldo ! | 
…ry#213) * Only fill charges container if waveforms are available * Cleanup commented stuff from some previous PR * Pin `persistent` (dependency for `ZODB`) version to fix CI --------- Co-authored-by: Jean-Philippe Lenain <[email protected]> # Conflicts: # src/nectarchain/makers/component/pedestal_component.py
…ry#213) * Only fill charges container if waveforms are available * Cleanup commented stuff from some previous PR * Pin `persistent` (dependency for `ZODB`) version to fix CI --------- Co-authored-by: Jean-Philippe Lenain <[email protected]> # Conflicts: # src/nectarchain/makers/component/pedestal_component.py
…ry#213) * Only fill charges container if waveforms are available * Cleanup commented stuff from some previous PR * Pin `persistent` (dependency for `ZODB`) version to fix CI --------- Co-authored-by: Jean-Philippe Lenain <[email protected]> # Conflicts: # src/nectarchain/makers/component/pedestal_component.py
While analyzing some data I had a crash. I found out this was due to the fact that a piece of code was misplaced. I moved the piece of code to create a charge container after the check that the waveforms are available. This avoids a crash in some special cases like the one I had encountered.