diff options
| author | tlatorre <tlatorre@uchicago.edu> | 2019-09-27 18:38:58 -0500 |
|---|---|---|
| committer | tlatorre <tlatorre@uchicago.edu> | 2019-09-27 18:38:58 -0500 |
| commit | e41bc169e213bbb2fb1c132150736e3ad8760dd4 (patch) | |
| tree | 0d0054f5c92764e93a319248da556b3e73e4a079 /src/hdf5_utils.c | |
| parent | a2d5287830c7dab92e78294c3a6833464dc5e59d (diff) | |
| download | sddm-e41bc169e213bbb2fb1c132150736e3ad8760dd4.tar.gz sddm-e41bc169e213bbb2fb1c132150736e3ad8760dd4.tar.bz2 sddm-e41bc169e213bbb2fb1c132150736e3ad8760dd4.zip | |
update the flasher cut
This commit updates the flasher cut with the following changes:
- no longer require nhit to be less than 1000
- update charge criteria to be that the flasher channel must have a QHS or QHL
1000 counts above the next highest QHS or QHL value in the PC or a QLX value
80 counts above the next highest QLX value
- only check is_slot_early() for missing hits in the PC
These updates were inspired by looking at how to tag flashers in runs 20062 -
20370 which didn't fail the original cut. In particular, the following flashers
were previously not tagged:
Run GTID Comments
--- ---- --------
20062 818162 flasher with only 3 hits in PC
reconstructs at PSUP
ESUMH triggered
20083 120836 high charge missing (in next couple of events)
probably picked wrong flasher PMT ID
20089 454156 nhit > 1000
After this commit the last two are properly tagged.
Diffstat (limited to 'src/hdf5_utils.c')
0 files changed, 0 insertions, 0 deletions