<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=us-ascii">
<style type="text/css" style="display:none;"> P {margin-top:0;margin-bottom:0;} </style>
</head>
<body dir="ltr">
<div style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
Hello all,</div>
<div style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
I updated THcHallCSpectrometer.cxx so that the "tr" branch will now have</div>
<div style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
all the info about that goes into the pruning. You need to use this branch:</div>
<div style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
<a href="https://github.com/JeffersonLab/hcana/tree/update-april2020">https://github.com/JeffersonLab/hcana/tree/update-april2020</a><br>
</div>
<div style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
<br>
</div>
<div style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
<div style="margin: 0px; font-size: 12pt; font-family: Calibri, Arial, Helvetica, sans-serif; color: black; background-color: rgb(255, 255, 255)">
Peter and I have slightly different meanings of track efficiency. For me, the tracking efficiency</div>
<div style="margin: 0px; font-size: 12pt; font-family: Calibri, Arial, Helvetica, sans-serif; color: black; background-color: rgb(255, 255, 255)">
does not involved cuts on quantities that involve track information. I agree that the pruning</div>
<div style="margin: 0px; font-size: 12pt; font-family: Calibri, Arial, Helvetica, sans-serif; color: black; background-color: rgb(255, 255, 255)">
is helping with track selection so when there are more the two possible tracks</div>
<div style="margin: 0px; font-size: 12pt; font-family: Calibri, Arial, Helvetica, sans-serif; color: black; background-color: rgb(255, 255, 255)">
it will pick the better one when compared to the chi-square only test. So I would</div>
<div style="margin: 0px; font-size: 12pt; font-family: Calibri, Arial, Helvetica, sans-serif; color: black; background-color: rgb(255, 255, 255)">
definitely use pruning method.</div>
<div style="margin: 0px; font-size: 12pt; font-family: Calibri, Arial, Helvetica, sans-serif; color: black; background-color: rgb(255, 255, 255)">
Now I also agree that eliminating events which are bad reconstruction is a good idea</div>
<div style="margin: 0px; font-size: 12pt; font-family: Calibri, Arial, Helvetica, sans-serif; color: black; background-color: rgb(255, 255, 255)">
and then correcting for these rejected events in needed. I would call that a good track</div>
<div style="margin: 0px; font-size: 12pt; font-family: Calibri, Arial, Helvetica, sans-serif; color: black; background-color: rgb(255, 255, 255)">
reconstruction efficiency. I make the distinction since traditionally in Hall C, the track efficiency</div>
<div style="margin: 0px; font-size: 12pt; font-family: Calibri, Arial, Helvetica, sans-serif; color: black; background-color: rgb(255, 255, 255)">
uses the goodscinhit with some PID based on non-track information.</div>
<br>
</div>
<div style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
<br>
</div>
<div style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
If you are planning to use this branch, then you need to set the</div>
<div style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
default pedestals. Also the new code shifts each detector AdcTdcDiffTime by an </div>
<div style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
<span style="color: rgb(0, 0, 0); font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 12pt;">new hodoscope offset that is the difference between the</span></div>
<div style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
<span style="color: rgb(0, 0, 0); font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 12pt;">hodo average adc and tdc times ( in addition to the start time). The "easiest"</span></div>
<div style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
<span style="color: rgb(0, 0, 0); font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 12pt;">is to change the hhodo_adc_tdc_offset</span></div>
<div style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
probalby by -45 for all planes to get the HMS Hodoscope ADCTDC diff time to peak at zero.</div>
<div style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
It does not have to be exactly zero.</div>
<div style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
But you need to check if this is true. You also should check SHMS HOdo ADCTDC diff time</div>
<div style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
but that is usually close to zero. You will need to change the Hodo ADCTDC diff time windows,</div>
<div style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
though wiht the new code you are not so sensitive to the hodo windows being wrong.</div>
<div style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
<br>
</div>
<div style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
With this change the ADCTDC diff time windows for the</div>
<div style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
other detectors should work unless you set them very tight.</div>
<div style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
<br>
</div>
<div style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
Cheers,</div>
<div style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
Mark</div>
<div id="appendonsend"></div>
<hr style="display:inline-block;width:98%" tabindex="-1">
<div id="divRplyFwdMsg" dir="ltr"><font face="Calibri, sans-serif" style="font-size:11pt" color="#000000"><b>From:</b> Mark Jones <jones@jlab.org><br>
<b>Sent:</b> Saturday, May 23, 2020 1:28 PM<br>
<b>To:</b> Peter Bosted <bosted@jlab.org>; Dipangkar Dutta <ddutta07@gmail.com><br>
<b>Cc:</b> hallc_sidis_analysis@jlab.org <hallc_sidis_analysis@jlab.org><br>
<b>Subject:</b> Re: TRacking parameters and efficiency</font>
<div> </div>
</div>
<style type="text/css" style="display:none">
<!--
p
{margin-top:0;
margin-bottom:0}
-->
</style>
<div dir="ltr">
<div style="font-family:Calibri,Arial,Helvetica,sans-serif; font-size:12pt; color:rgb(0,0,0)">
I quickly wrote a document about track selection in HCANA. If there are mistakes or nonsensical</div>
<div style="font-family:Calibri,Arial,Helvetica,sans-serif; font-size:12pt; color:rgb(0,0,0)">
statements, then let me know. If there needs to be more explanation then</div>
<div style="font-family:Calibri,Arial,Helvetica,sans-serif; font-size:12pt; color:rgb(0,0,0)">
let me know.</div>
<div style="font-family:Calibri,Arial,Helvetica,sans-serif; font-size:12pt; color:rgb(0,0,0)">
<br>
</div>
<div style="font-family:Calibri,Arial,Helvetica,sans-serif; font-size:12pt; color:rgb(0,0,0)">
I will work on a document for the tracking itself.</div>
<div style="font-family:Calibri,Arial,Helvetica,sans-serif; font-size:12pt; color:rgb(0,0,0)">
<br>
</div>
<div style="font-family:Calibri,Arial,Helvetica,sans-serif; font-size:12pt; color:rgb(0,0,0)">
Since I keep getting asked about this, I will state that the track selection or</div>
<div style="font-family:Calibri,Arial,Helvetica,sans-serif; font-size:12pt; color:rgb(0,0,0)">
pruning does NOT effect the tracking efficiency. It may only change which</div>
<div style="font-family:Calibri,Arial,Helvetica,sans-serif; font-size:12pt; color:rgb(0,0,0)">
track (when there are2 or more possible tracks) is picked as the golden track.</div>
<div style="font-family:Calibri,Arial,Helvetica,sans-serif; font-size:12pt; color:rgb(0,0,0)">
<br>
</div>
<div style="font-family:Calibri,Arial,Helvetica,sans-serif; font-size:12pt; color:rgb(0,0,0)">
Cheers,</div>
<div style="font-family:Calibri,Arial,Helvetica,sans-serif; font-size:12pt; color:rgb(0,0,0)">
Mark</div>
<div id="x_appendonsend"></div>
<hr tabindex="-1" style="display:inline-block; width:98%">
<div id="x_divRplyFwdMsg" dir="ltr"><font face="Calibri, sans-serif" color="#000000" style="font-size:11pt"><b>From:</b> Peter Bosted <bosted@jlab.org><br>
<b>Sent:</b> Friday, May 22, 2020 4:07 PM<br>
<b>To:</b> Dipangkar Dutta <ddutta07@gmail.com><br>
<b>Cc:</b> hallc_sidis_analysis@jlab.org <hallc_sidis_analysis@jlab.org>; Mark Jones <jones@jlab.org><br>
<b>Subject:</b> TRacking parameters and efficiency</font>
<div> </div>
</div>
<div class="x_BodyFragment"><font size="2"><span style="font-size:11pt">
<div class="x_PlainText">Hi Hem, Jia, et al.,<br>
Most everything related to tracking is in for<br>
example<br>
/group/c-sidis/bosted/hallc_replay/PARAM19/SHMS/GEN/ptracking.param<br>
(for spring19. I think I have same for PARAM_FALL19/...)<br>
and similary there is /htracking.<br>
As you can see, this file is where you can turn on<br>
the pruning software, and set the pruning parameters.<br>
Perhaps Mark Jones has a writeup that he can send us that<br>
explains how it works and what the variables are?<br>
Near the bottom of this file are the range of<br>
scinitllator paddlee numbers to be used in defining<br>
the goodscinhit variable, I think. I adjusted the limits<br>
a little bit from what we had online. The idea is that<br>
if paddles within these ranges go off, and all four<br>
planes fire, geometrically there should be a track. These<br>
limits are needed because the hodoscope array is slightly<br>
bigger than the drift chambers (on purpose).<br>
I don't use the def-file cuts to obtain tracking efficiency. Instead, I <br>
definie it myself in the code<br>
/group/c-sidis/bosted/hallc_replay/PeterB.C<br>
Yous can see that for HMS, I require all kinds of good<br>
things in the SHMS, plus goodscinhit, plus another variable<br>
that I define that ensures that we had a good start time.<br>
Then I have three counters, one for just a track, then with<br>
a cut on hdelta, then with a cut on hbeta, then with a cut<br>
of ytar. I used the tightest cut for my actual efficiency,<br>
but the other ones are useful too.<br>
There is a place in the code where tracking efficiency<br>
is obtained as a function of raw cointime (also defined<br>
in my code). I didn't see any obvious dependance on this,<br>
quantity.<br>
The output of PeterB.C is a "skimmed" set of events<br>
that will be processed by another code to get cross<br>
sections, etc. This is because it takes too long to<br>
loop through 2510 root files each time I want a new<br>
result. There is also a little report file that includes<br>
that tracking efficiency and the reftime multiplicity<br>
efficiency. Also some estimate of hodoscope efficiency<br>
that is done differently than in hcana and put in the<br>
REPORT FILES.<br>
My "skimmed" files are in plain text format which<br>
I like because I can see everything in emacs, but most<br>
analyzers make "skimmed" root files. Basically, just<br>
keep the variables you really need and put cuts on<br>
things like cointime, HMS cer and cal, perhaps aerogel,<br>
and of course a good track. In the ideal world, you<br>
should be able to process the "skimmed" files for the<br>
entire set of experiments in an hour or less. The way<br>
I work, this code actually produces another file for each<br>
run, which are the number of counts in bins of<br>
z, pt, phi*. I keep track of the number of reals and<br>
accientals separately, and have three definitions. The<br>
third one has the tightest cuts, but is meant to have<br>
a more reliable pi-/pi+ ratio but reducing the kaon<br>
contamination to a negligible level (for example, with<br>
ceraero>4 npe). The same file also contains the number<br>
of counts and total weight (times normfac) from SIMC<br>
for each bin. I have seven sets of SIMC values:<br>
SIDIS pi with radiation<br>
SIDIS pi with no radiative tail<br>
exclusive pion<br>
SIDIS from endcaps<br>
diffractive rho<br>
SIDIS K with rad<br>
SIDIS K no rad<br>
These come from the events files produced by SIMC,<br>
which I store in the same plain test format as the<br>
real data.<br>
I have other codes that process these "count files"<br>
to obtain all the physics results, make plots, and fit<br>
for physics parameters.<br>
Everyone does things differently, but that is my<br>
method. I plan combine runs at identical kinematics and<br>
target together at some point to reduce the number of<br>
bins that only have a few counts, because for those<br>
bins the error bars is not Gaussian and it can be a<br>
bit tricky to combine runs together at the cross section<br>
level.<br>
Anyway, this might be more than you wanted to know,<br>
but feel to ask more questions about tracking efficiency.<br>
As I say, this is probably one of the most tricky parts<br>
of the analysis to understand, because it is closely<br>
tied up with other cuts and definitions. The best<br>
thing to do is study the runs taken with different beam<br>
current and make sure that your final yield does<br>
not depend on beam current. For example, runs 5368-3478.<br>
These runs had aerogel tray SP11 by the way.<br>
After months and months of work, I'm more or less<br>
satisfied now. Make sure you're using Mark's new<br>
version of hcana, his new matrix elements for HMS, and<br>
new matrix elements for SIMC.<br>
Feel free to ask more questions!<br>
Peter<br>
<br>
<br>
Prof. Peter Bosted<br>
email: bosted@jlab.org<br>
phone: (808) 315-1297 (cell)<br>
P.O. Box 6254, Ocean View, HI 96737<br>
<br>
On Thu, 21 May 2020, Dipangkar Dutta wrote:<br>
<br>
> Hi All,<br>
> We will have the regular CSV analysis meeting tomorrow<br>
> (Friday) at 1:00 PM EDT<br>
> <br>
> The Meeting URL is<br>
> <a href="https://bluejeans.com/341030850">https://bluejeans.com/341030850</a><br>
> <br>
> Please plan on showing a few slides on your work and<br>
> please upload the<br>
> slides to the SIDIS elog at:<br>
> <a href="https://hallcweb.jlab.org/elogs/SIDIS+Pt+and+CSV+Exper">https://hallcweb.jlab.org/elogs/SIDIS+Pt+and+CSV+Exper</a><br>
> iments+Analysis<br>
> <br>
> <br>
> Cheers<br>
> Dipangkar<br>
> <br>
> <br>
><br>
</div>
</span></font></div>
</div>
</body>
</html>