[G12] Fwd: ECin/ECout not used with clasEvent::IsLepton() ??

[Johann Goetz]

---------- Forwarded message ---------
From: Michael Paolone <mpaolone at jlab.org>
Date: Fri, Jul 3, 2015 at 5:40 PM
Subject: Re: ECin/ECout not used with clasEvent::IsLepton() ??
To: Johann Goetz <theodore.goetz at gmail.com>


Hey Johann,

The answer is simple.  There are more and more restrictive cuts you can
always do to try to clean up a lepton signal, but the general CC, TOF, and
ECtot are the most robust.  After that you can make further cuts on Ecin
and/or ECout at your discretion.  The g7 lepton cuts were the standard
isLepton(), plus a >45 MeC ECin cut (see Rakhsha's analysis note here:
https://www.jlab.org/Hall-B/secure/nuclear/g7-analysis/) and that's it.

There are additional 2D isLepton_EC cuts in clasEvent to help clean up the
signal, but the ECtot does "most" of the work already.

Short answer:  IsLepton() in g12 was made to be a balanced between good
lepton selection without being aggressively restrictive.  Like any other
PID, it is up to the individual analyses to show the validity of their
particle selection, and make additional cuts as needed.

-Michael

> Hi Mike, Take a look at this issue:
>
> https://github.com/JeffersonLab/clasdoc-g12-procedures/issues/69
>
> Eugene et al. writes:
>
> The note refers to the g7 lepton id scheme in explaining the chosen cuts:
> in g7 however, not only cuts on the total calorimeter energy but also cuts
> on the inner and outer energy were used: why were these not considered
> necessary in the present analysis?
>
> MK, Lei and I just looked at clasEvent::IsLepton() and it only uses Etot.
> Can you explain this so we can answer this question from the committee?
> Thanks,
> Johann.
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://mailman.jlab.org/pipermail/g12/attachments/20150706/8a9ea5be/attachment.html>