Add ring veto at the records level

[JoranAngevaare]

Similar to the high energy veto, we might also cut out a ROI where we have most PMTs firing at the edge of the TPC. These records are going to be fiducialized later anyway, we could save a lot of storage if we already cut at the low level.

[AlexElykov]

This is indeed a nice idea. Just for reference here is a similar concept that Lukas tried to implement for XENON1T in hardware, using the hardware HEV. The DAQ was never cabled for it, so we don't know if it ever worked.

However, he made this small study, which I recovered from the dead Bern wiki, and written a bit about it in his thesis veto chapter (it's also in the same link below):
https://xe1t-wiki.lngs.infn.it/doku.php?id=xenon:xenon1t:alexelykov:lukas_ring_veto

They were afraid of multi-scatter events leaking into the NR band, so I guess in software we also need to be careful not to produce extra "backgrounds". Although, in software it also should be much easier to track the issued vetoes and to make a quality cut based on that.

[WenzDaniel]

I also like the idea. I think in software it is much easier to establish such a veto as we can first keep everything and build the veto based on events. (This only makes sense if you would like to just reduce the amount of data. Obviously it will not help with processing in that case.)

[AlexElykov]

I guess it might be possible to do it even earlier in the chain (similarly to the software HEV).
Maybe @tunnell will be interested in this topic.