<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body>
<div dir="ltr">Matt,
<div><br>
</div>
<div>Yes, these historical things slip in under the radar some times. I'll remove these cuts and produce some files to look at.</div>
<div><br>
</div>
<div>---Sean<br>
<br>
<div class="gmail_quote">
<div dir="ltr">On Sun, Nov 18, 2018 at 9:42 AM Shepherd, Matthew <<a href="mailto:mashephe@indiana.edu">mashephe@indiana.edu</a>> wrote:<br>
</div>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div style="word-wrap:break-word;line-break:after-white-space">
<div><br>
</div>
<div>Sean,</div>
<div><br>
</div>
<div>Yes, that 20 cm cut definitely shouldn't be there at the skim level. We can't calibrate the blocks if they don't enter the skim! I suppose this a relic from Adesh's code. At one point he was just looking for clean pi0's and such a cut was helpful to
reduce background. I hadn't realized that it had propagate all the way the to plugin that does skimming for gain calibration. Wish we would have discovered this earlier.</div>
<div><br>
</div>
<div>There is still some funny correlation with occupancy and clusters. Ilia's cluster seeds are a little higher than what we are using, but likely this is a second order effect and our biggest problem is just the cuts on the skim. </div>
<div><br>
</div>
<div>Matt</div>
<br>
<div><br>
<blockquote type="cite"></blockquote>
</div>
</div>
<div style="word-wrap:break-word;line-break:after-white-space">
<div>
<blockquote type="cite">
<div>On Nov 17, 2018, at 11:30 PM, Sean Dobbs <<a href="mailto:sdobbs@fsu.edu" target="_blank">sdobbs@fsu.edu</a>> wrote:</div>
<br class="m_7447412988594571207Apple-interchange-newline">
</blockquote>
</div>
</div>
<div style="word-wrap:break-word;line-break:after-white-space">
<div>
<blockquote type="cite">
<div>
<div>
<div dir="ltr">Hi all,
<div><br>
I took another look at the current definitions of the FCAL pi0 skim. They are:</div>
<div><br>
</div>
<div>- Pair together two FCAL showers which are not matched to tracks (given some track quality criteria) with E > 500 MeV, and r > 20 cm</div>
<div>- The difference between the shower times must be < 10 ns</div>
<div>- M(gg) < 300 MeV</div>
<div><br>
</div>
<div>I think the 20 cm radial cut would suppress the number of showers in the inner rings?</div>
<div><br>
</div>
<div>In either case, it would be good to know if the inner ring pi0 showers Ilya is seeing satisfy these criteria, or which ones are not satisfied.</div>
<div><br>
</div>
<div>Cheers,<br>
Sean</div>
<div><br>
<div class="gmail_quote">
<div dir="ltr">On Sat, Nov 17, 2018 at 10:48 PM Ilia Larin <<a href="mailto:ilarin@jlab.org" target="_blank">ilarin@jlab.org</a>> wrote:<br>
</div>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
Hi Colin,<br>
<br>
I checked that skim file.<br>
I see nothing at all in the most inner FCAL layer,<br>
and highly suppressed statistics for 2nd and 3rd FCAL inner layers.<br>
<br>
Ilya<br>
<br>
----- Original Message -----<br>
From: "Colin Gleason" <<a href="mailto:gleasonc609@gmail.com" target="_blank">gleasonc609@gmail.com</a>><br>
To: "Ilya Larin" <<a href="mailto:ilarin@jlab.org" target="_blank">ilarin@jlab.org</a>><br>
Sent: Friday, November 16, 2018 5:22:10 PM<br>
Subject: fcal pi0 skim<br>
<br>
Ilya,<br>
<br>
Here is the location of the pi0 skim:<br>
<br>
/cache/halld/RunPeriod-2018-08/calib/ver01/FCAL_pi0/Run050930/hd_rawdata_050930_000.pi0fcalskim.evio<br>
<br>
We only skim over 10% of the run due to computation limits, so there should<br>
be around 30 files in the directory. I think 1 run should be enough to see<br>
and compare pi0s. Iff we need more, we can use up to 10 files. If you run<br>
with -PNTHREADS=4, then it should take 1-2 minutes to run interactively.<br>
If you still see pi0s, then you can probably use these skims to save time.<br>
-- <br>
Colin Gleason<br>
Postdoctoral Fellow<br>
Indiana University<br>
Department of Physics<br>
_______________________________________________<br>
Primexd mailing list<br>
<a href="mailto:Primexd@jlab.org" target="_blank">Primexd@jlab.org</a><br>
<a href="https://urldefense.proofpoint.com/v2/url?u=https-3A__mailman.jlab.org_mailman_listinfo_primexd&d=DwICAg&c=HPMtquzZjKY31rtkyGRFnQ&r=bxTPW7N21WY8eJ2MkW85CQ&m=qPAEZ27hN9RU9XnzxcygnUrtVRIBVLgy9Z-ysLyvmn0&s=SvopsnSK8aOroUAgdtQ5VtYwuuIRCbwCP9dHcUn2rbo&e=" rel="noreferrer" target="_blank">https://urldefense.proofpoint.com/v2/url?u=https-3A__mailman.jlab.org_mailman_listinfo_primexd&d=DwICAg&c=HPMtquzZjKY31rtkyGRFnQ&r=bxTPW7N21WY8eJ2MkW85CQ&m=qPAEZ27hN9RU9XnzxcygnUrtVRIBVLgy9Z-ysLyvmn0&s=SvopsnSK8aOroUAgdtQ5VtYwuuIRCbwCP9dHcUn2rbo&e=</a><br>
</blockquote>
</div>
</div>
</div>
</div>
_______________________________________________<br>
Primexd mailing list<br>
<a href="mailto:Primexd@jlab.org" target="_blank">Primexd@jlab.org</a><br>
</div>
</blockquote>
</div>
</div>
<div style="word-wrap:break-word;line-break:after-white-space">
<div>
<blockquote type="cite">
<div><a href="https://mailman.jlab.org/mailman/listinfo/primexd" target="_blank">https://mailman.jlab.org/mailman/listinfo/primexd</a><br>
</div>
</blockquote>
</div>
<br>
</div>
</blockquote>
</div>
</div>
</div>
</body>
</html>