-
Notifications
You must be signed in to change notification settings - Fork 3
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
SiPM dsp parameters #22
Comments
Sure, why not. What do we use |
sometimes there are "noise trains" in the traces that we can tag with |
Hm, we'll have to see how to make this performant. Variance would be easy, but for FWHM we have to build per-waveform histograms, right? |
So the |
that's how the build the histogram in pygama: https://github.com/legend-exp/dspeed/blob/main/src/dspeed/processors/histogram.py. Maybe we can do something similar. I agree that |
We should be able to use |
@rosannadeckert will check after reprocessing:
|
Now we have the following parameters:
blfc
,timestamp
,eventID_fadc
,e_fc
,trig_pos
,trig_max
,trig_pos_DC
,trig_max_DC
. Can we add the following parameters:tp_max
,tp_min
,wf_max
,wf_min
(finds max and min of waveform with corresponding time points)tp_max_lar
,tp_min_lar
,wf_max_lar
,wf_min_lar
(finds max and min of waveform with corresponding time points in a LAr scintillation window around 48 us, i.e. from 47 us to 53 us)wf_fwhm
(FWHM of waveform projected on y axis)is_valid_hit
(for each trig_pos, True or False if there was a crosstalk (DC) event close)Let me know what you think.
The text was updated successfully, but these errors were encountered: