<html>
<head>
<meta http-equiv="content-type" content="text/html; charset=utf-8">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<p>Folks,</p>
<p>Here are the minutes from two weeks ago, below and at
<a class="moz-txt-link-freetext" href="https://halldweb.jlab.org/wiki/index.php/GlueX_Start_Counter_Meeting,_October_20,_2016#Minutes">https://halldweb.jlab.org/wiki/index.php/GlueX_Start_Counter_Meeting,_October_20,_2016#Minutes</a>
.</p>
<p> -- Mark</p>
<p>____________________</p>
<p>
</p>
<div id="globalWrapper">
<div id="column-content">
<div id="content" class="mw-body" role="main">
<h2 id="firstHeading" class="firstHeading" lang="en"><span
dir="auto">GlueX Start Counter Meeting, October 20, 2016</span><span
class="mw-headline" id="Minutes">, Minutes</span></h2>
<div id="bodyContent" class="mw-body-content">
<div id="mw-content-text" dir="ltr" class="mw-content-ltr"
lang="en">
<p>Present:
</p>
<ul>
<li> <b>FIU</b>: Werner Boeglin, Mahmoud Kamel</li>
<li> <b>JLab</b>: Thomas Britton, Mark Ito (chair),
Paul Mattione, Eric Pooser, Simon Taylor</li>
</ul>
<p>There is a <a rel="nofollow" class="external text"
href="https://bluejeans.com/s/c7N2c/">recording of
this meeting</a> on the BlueJeans site.
</p>
<h3><span class="mw-headline" id="Announcements">Announcements</span></h3>
<ul>
<li> There will be no beam until after Thanksgiving.
[Added in press: beam is now due November 17.]</li>
<li> The target has not been pushed into the bore yet.</li>
</ul>
<h3><span class="mw-headline"
id="Possible_start_counter_hole.3F">Possible start
counter hole?</span></h3>
<p>Mahmoud noticed a "feature" of the start counter
geometry. He
discussed this with Sean and the discussion moved to an
[<a rel="nofollow" class="external free"
href="https://github.com/JeffersonLab/sim-recon/issues/594#issuecomment-254847156">https://github.com/JeffersonLab/sim-recon/issues/594#issuecomment-254847156</a>
issue on GitHub]. Please see GitHub for the details and
plots of the
effects. Paul and Mike Staib contributed studies and
Simon found and
fixed the root problem in the algorithm for determining
the
intersection of charged tracks with the start counter.
</p>
<h3><span class="mw-headline" id="Run_Readiness">Run
Readiness</span></h3>
<ul>
<li> The start counter has not been pushed into the bore
yet.</li>
<li> Sascha Somov told Mark that the problem preventing
read-out of the TDC crate a couple of weeks ago has
been solved. The download of new TI firmware in that
crate had been interrupted before completion and so
the TI was unsurprisingly non-functional. The full
complement of firmware has since been downloaded.</li>
<li> Sascha also mentioned he is seeing very occasional
corruption of TDC data from this crate. It appears on
a hour-ish timescale and does not affect subsequent
events in the run. The cause is unknown at present.</li>
</ul>
<h3><span class="mw-headline" id="Efficiency">Efficiency</span></h3>
<p>Yesterday, Paul sent Mahmoud a description of how he
pictures doing
the efficiency measurement. We had some significant
discussion, but
nearly all of it had to do with definition of terms
(what is a "hit")
and the cuts used in the efficiency tree that Paul
wrote. Paul did
note that there is a loose timing cut relating the track
to the start
counter and the information for the user to apply a
custom cut will be
present in a future version of the tree.
</p>
<h3><span class="mw-headline" id="NIM.2FTDR">NIM/TDR</span></h3>
<p>Eric has started on writing the NIM-article/TCR. In
parallel he will put together a contribution to the TDR.
He plans to use the ShareLaTex platform.
</p>
<h3><span class="mw-headline" id="Meeting_time_change">Meeting
time change</span></h3>
<p>We decided to move the meetings from 10 am to 11 am. We
will keep the same day, every two weeks on Thursday.
</p>
</div>
<br>
</div>
</div>
</div>
</div>
</body>
</html>