<html>
<head>
<meta http-equiv="content-type" content="text/html; charset=utf-8">
</head>
<body text="#000000" bgcolor="#FFFFFF">
Folks,<br>
<br>
Please find the minutes below and at<br>
<br>
<a class="moz-txt-link-freetext" href="https://halldweb1.jlab.org/wiki/index.php/GlueX_TOF_Meeting,_October_21,_2014#Minutes">https://halldweb1.jlab.org/wiki/index.php/GlueX_TOF_Meeting,_October_21,_2014#Minutes</a>
.<br>
<br>
-- Mark<br>
<br>
_______________________________<br>
<br>
<h1>GlueX TOF Meeting, October 21, 2014 <span class="mw-headline"
id="Minutes">Minutes</span></h1>
<div id="bodyContent">
<p>Present:
</p>
<ul>
<li> <b>FSU</b>: Hussein Al Ghoul, Sasha Ostrovidov
</li>
<li> <b>JLab</b>: Mark Ito, Aristeidis Tsaris, Beni Zihlmann
</li>
</ul>
<h2> <span class="mw-headline" id="Work_in_the_Hall">Work in the
Hall</span></h2>
<p>Aristeidis brought us up-to-date with recent TOF work.
</p>
<ul>
<li> He conducted a cross-training session on October 13 for
would-be TOF experts along with the start counter training
conducted by Eric Pooser.
</li>
<li> There were two inefficient modules in the monitoring
histograms last week. See the vertical band on page one of <a
href="http://hadron.physics.fsu.edu/%7Earisteidis/fix.pdf"
class="external text" rel="nofollow">his plots</a>. He
traced this to a double swap, both the high voltage and the
signal cables from neighboring PMTs had been exchanged.
</li>
<li> Two channels showed a negative overshoot in the ADCs. See
page two for the waveform. This was fixed by swapping out the
cables from the splitter to the ADCs for new ones for both
channels.
</li>
<li> He has checked in the initial set of online monitoring
histograms for the TOF.
</li>
<li> He is working with Simon Taylor to incorporate a TOF
display into hdview2. This version is like the "simple viewer"
developed at FSU.
</li>
</ul>
<h2> <span class="mw-headline" id="The_Mode_7_Blues">The Mode 7
Blues</span></h2>
<ul>
<li> Data taken over the weekend (24 million events) in mode 7
has problems with the ADCs
<ul>
<li> Mode 7 does not have waveform data, instead it reports
pedestal, pulse integral, and leading-edge time.
</li>
</ul>
</li>
<li> The read-out threshold was set at 10 counts, when the
pedestal value was 200. Only pulse integral data was non-zero
as expected for this (mis-)configuration.
</li>
<li> Aristeidis tried a value of 200 counts for the threshold
and some of the channels were fixed.
</li>
<li> He will try 210 and see if they all come around.
</li>
<li> Beni suggests a 5 sigma threshold. Sasha reports that the
pedestal width is about 1 to 2 counts.
</li>
<li> We discussed an appropriate value of the number of samples
before threshold crossing (NSB) and the number after threshold
crossing (NSA) that are kept in the pulse integral. We decided
that NSB = 10 and NSA = 45 were good values. There is another
pair of NSB/NSA parameters for the trigger. We were not sure
how they are used.
</li>
<li> Aristeidis noted that the stand-alone TOF trigger could not
be run from Sergey Furletov's general DAQ GUI, only by using
the system that Sascha Somov set-up for us. We thought it
would be nice if we could run both ways.
</li>
<li> The standalone trigger was broken recently. Sascha S. fixed
it; we don't know how.
</li>
</ul>
</div>
<br>
<pre class="moz-signature" cols="72">--
Mark M. Ito, Jefferson Lab, <a class="moz-txt-link-abbreviated" href="mailto:marki@jlab.org">marki@jlab.org</a>, (757)269-5295</pre>
</body>
</html>