[Primexd] Random trigger skims

[Alexander Somov]

Hi,

The fraction of accidental hits in the CCAL is relatively small
so the impact of accidentals on the efficiency of Compton events
is not significant, at least for the event selection I used.

The difference in efficiency was well below 1% (on the level of sensitivity of
the MC sample I used) when the beam trip time was excluded  (for some
runs with the typical fraction of the beam off time )

At any rate, when Peter is done with his method, we can produce new hddm files
for random triggers. The easiest way would be to accept or reject random triggers
in between SYNC events, where we read out TS scalers (I don't know how exactly
Peter is implementing this).

Cheers,
             Sasha



________________________________
From: Primexd <primexd-bounces at jlab.org> on behalf of Alexander Austregesilo <aaustreg at jlab.org>
Sent: Thursday, January 21, 2021 5:25 PM
To: Igal Jaegle <ijaegle at jlab.org>
Cc: primexd at jlab.org <primexd at jlab.org>; Peter Pauli (PGR) <p.pauli.1 at research.gla.ac.uk>
Subject: [Primexd] Random trigger skims

Hi Igal,

We have a plugin called randomtrigger_skim to filter out the random
triggers from any evio input and convert them into the hddm format that
can be mixed into the simulation by mcsmear. To be more realistic, we
only accept random triggers that fall into a time period were the beam
was actually on. The plugin takes this beam fiducial map into account,
but it has to be generated beforehand. Peter Pauli (cc) was just working
on an improved scheme for this extraction, maybe he can help you also
for the PrimEx data.

Once the fiducial map is ready, you just have to run the plugin over all
evio files. Afterwards, we can concatenate the hddm skims from
individual evio files so that we have one file per run.

Before you have the fiducial map, you can also include the option
`RANDSKIM:USEBEAM 0` into your config file to simply write out all
random triggers. This serves already as a good approximation.

Let me know if you have any questions,

Alex

_______________________________________________
Primexd mailing list
Primexd at jlab.org
https://mailman.jlab.org/mailman/listinfo/primexd
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://mailman.jlab.org/pipermail/primexd/attachments/20210121/a99a0891/attachment.html>