-
Notifications
You must be signed in to change notification settings - Fork 18
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 waveforms and charge extraction #60
Conversation
before trying to load cookies
loading all the data in memory -> to evoid ram excess usage -split computation of charge to finally merge
data fits.fz files
Codecov ReportPatch coverage has no change and project coverage change:
Additional details and impacted files@@ Coverage Diff @@
## master #60 +/- ##
=========================================
- Coverage 0.39% 0.38% -0.01%
=========================================
Files 30 30
Lines 3275 3350 +75
=========================================
Hits 13 13
- Misses 3262 3337 +75
☔ View full report in Codecov by Sentry. |
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 for these improvements, @guillaumegrolleron !
The small PR aims to improve the waveforms and charge extraction in the container module.
-The RAM needed to extract waveforms and charge was to much large for raw data with more than 50000 events. This PR solved this issue by using the
ChargeContainers
andWaveformsContainers
class. Indeed now it is possible to extract waveforms and compute charge treating the fits.fz files one by one. It is quite transparent from outside of the module.-The script
load_wfs_compute_charge.py
has been improved to take care of this modifications.-I aslo fixed a bug concerning the charge extraction, code was mixing the charge extracted and the peak index which was leading to inconsistent data
Basically now the memory usage stay hold back to 20 Gb when it reached 60 Gb before.