From this note, one can see that due to the lower coincidence requirement of S1 peak-classification in pax v6.10.1 (compared to v6.8.0), the S1SingleScatterCut will cut more events in pax v6.10.1. In order to be able to select those events where an alternate S1 is only detected due to the lowered coincidence requirement, I propose to add alt_s1_tight_coincidence to the Extended minitree.
For the S1SingleScatterCut I made this note: https://xe1t-wiki.lngs.infn.it/doku.php?id=xenon:xenon1t:analysis:sciencerun2:s1singlescattercut
From this note, one can see that due to the lower coincidence requirement of S1 peak-classification in pax v6.10.1 (compared to v6.8.0), the S1SingleScatterCut will cut more events in pax v6.10.1. In order to be able to select those events where an alternate S1 is only detected due to the lowered coincidence requirement, I propose to add
alt_s1_tight_coincidenceto theExtendedminitree.