[Halld-pid] Time-of-Flight Meeting Minutes, September 23, 2014
Mark M. Ito
marki at jlab.org
Wed Sep 24 15:44:47 EDT 2014
Folks,
Find the minutes below and at
https://halldweb1.jlab.org/wiki/index.php/GlueX_TOF_Meeting,_September_23,_2014#Minutes
-- Mark
_____________________________________________
GlueX TOF Meeting, September 23, 2014Minutes
Present:
* *FSU*: Hussein Al Ghoul, Sasha Ostrovidov, Aristeidis Tsaris
* *JLab*: Mark Ito, Beni Zihlmann
Review of Previous Meetings
We went over minutes from September 2
<https://halldweb1.jlab.org/wiki/index.php/GlueX_TOF_Meeting,_September_2,_2014>
and from September 9
<https://halldweb1.jlab.org/wiki/index.php/GlueX_TOF_Meeting,_September_9,_2014>.
* Sasha reports that TDC inefficiency is still and issue. There is a
factor of
two in the occupancy among certain channels.
* Aristeidis continues work on the event display. He is now working on
the TOF library, adjusting constants in the code, for example the
time window for matching FADC and TDC hits. For the viewer, he needs
a bit more information that that provided the TOF point object and
is looking at how to get it.
* FSU has been monitoring the rates in the TOF continuously. The high
voltage has been on for about a month and a half now. There were two
noisy channels at the beginning, but they have quieted down for
unknown reasons.
Collaboration Meeting
Aristeidis will give the presentation at the meeting. Sasha and Hussein
will also make the trip.
Hot Check-Out
We reviewed the list
<https://accweb.acc.jlab.org/hco/checklists?groupId=55> for the TOF. No
comments were offered.
Shift-Takers' Instructions
We reviewed the instructions
<https://hdops.jlab.org/wiki/index.php/Time-of-Flight_System_Shift>,
which are still pretty basic. Sasha commented that we still need
instructions on how to write the online monitoring code.
Commissioning Plan
We looked at the commissioning plan
<https://hdops.jlab.org/wiki/index.php/Time-of-Flight_System_Commissioning>
for the TOF that Sasha put together last month. It is rather complete.
No comments were offered.
Calibration
Sasha took another 2 million events a couple of weeks ago and
transferred them to FSU. Data taking was at one point interrupted by the
power outage in the Hall. Good data came from 6-8 hours of running and
came to 150 GB. Using this data he has been developing the calibration
procedure further.
*First Step*: Looking at each plane separately he fits straight lines to
hit counters, getting the hit position with end-to-end time differences.
He uses these fits to adjust the end-to-end timing offset and the speed
of light in the counter and iterates.
*Second Step*: Here he obtains module-to-module mean time offsets. He
has tried two approaches.
1. Events with two counters in each plane. A line is fit to the
trajectory, mean time offsets are obtained and the process iterated.
For some counters he sees participation in very few such tracks (as
low as 100).
2. Events with one counter in each plane. This gives mean time offsets
from counters in different planes by definition, but given all such
pairs time offsets can be calculated for all counters in all planes.
Here he is running into the ambiguity between cosmics which go
back-to-front and those going front-to-back. This is introducing an
ambiguity of about 100 ps.
Sasha thinks that with beam, a lot of these problems will disappear;
calibration will be relatively easy with particles from a target.
--
Mark M. Ito, Jefferson Lab, marki at jlab.org, (757)269-5295
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://mailman.jlab.org/pipermail/halld-pid/attachments/20140924/69a43f38/attachment-0002.html>
More information about the Halld-pid
mailing list