Difference between revisions of "GlueX TOF Meeting, March 28, 2018"

From GlueXWiki
Jump to: navigation, search
(Created page with "GlueX Time-of-Flight Meeting<br> Wednesday, March 28, 2018<br> 10:00 am EDT<br> JLab: CEBAF Center, Room F226 <br> BlueJeans Meeting number is [http://bluejeans.com/350531998...")
 
(minutes)
 
(One intermediate revision by the same user not shown)
Line 26: Line 26:
 
* ''' JLab: ''' Thomas Britton, Eugene Chudakov, Mark Ito (chair), Simon Taylor, Beni Zihlmann
 
* ''' JLab: ''' Thomas Britton, Eugene Chudakov, Mark Ito (chair), Simon Taylor, Beni Zihlmann
  
There is a [https://bluejeans.com/s/5iWhS/ recording of this meeting] on the BlueJeans site. Use your JLab credentials.
+
There is a [https://bluejeans.com/s/zCEdu/ recording of this meeting] on the BlueJeans site. Use your JLab credentials.
  
=== Review of minutes from the January 31 meeting ===
+
=== Changing the Hit Factory ===
  
We went over the [[GlueX TOF Meeting, January 31, 2018#Minutes|minutes]] without significant comment.
+
Beni has changed the TOF hit reconstruction code to use the FADC integral for the time-walk correction in the case that the amplitude is set to zero. Recall that this can happen when the voltage is above threshold at the beginning of the FADC read-out window. The ratio used is a hard-wired 0.2 (amplitude/integral). He analyzed a file both before and after this change and sees an increase in TOF efficiency. See [https://logbooks.jlab.org/entry/3547610 logbook entry 3547610] for plots that demonstrate the improvement. It can be greater than 10% in certain regions of the detector.
  
=== Calibration Status ===
+
The timing resolution appears to be a bit worse with the change, but a quantitative assessment is still in progress. Part of this may come from an apparent shift in the timing calibration constants. This is not expected and not understood.
  
As reported last time, Beni has done a preliminary calibration of 2018 data using early runs and has found timing constants very close to those obtained in Sprint 2017. A complete calibration of all of the Spring 2018 data will have to to done at some point, but is not the highest priority now (the run is officially still in progress).
+
=== Review of minutes from the March 14 meeting ===
  
=== Amplified Base Prototype ===
+
We went over the [[GlueX TOF Meeting, March 14, 2018#Minutes|minutes]].
  
Beni has been studying data take this year with the amplifier-on-board PMT base mounted on a spare TOF counter in the Hall.
+
==== High Rates and Missed Pulses ====
  
==== Resolution ====
+
There was further discussion of the presentation Beni made at the last meeting on losses at high rates.
  
He sees that the resolution of the test paddle (one end with the amplifier-on-board the other end standard) is about 20% worse than reference paddle 21 from the TOF proper. This is one of the counters with the highest rate.
+
* There were "missing channels" where FADC read-out was completely apparently absent from the event for channels were a pulse was expected. This was a bug. Those pulses are indeed there in the data.
 +
* The FADC read-out thresholds have been raised for the TOF from 110 counts to 160. This should improve efficiency. The level was chosen to be a bit below that of the discriminatory threshold (thus on the TDC side, note that the signal split is 50-50).
 +
* The feature of the firmware where "peak=0" is reported is allegedly fundamental in the algorithm and not easy to change.
 +
* We need to explore schemes where full waveform read-out is done, either selectively, or for every event, because of lost information at high rates.
 +
* Beni found out that there is an intrinsic dead-time in the discriminator of 20 to 25 ns, independent of input pulse width. This was chosen to match the dead-time of the F1-TDC. Since we are using CAEN TDCs in the TOF, this limits our double pulse separation capability. As a result, a discriminator width of 20 ns is used universally in GlueX.
  
==== Going Back to Basics ====
+
==== Amplifier-in-the-Base Tests ====
  
He showed several [https://logbooks.jlab.org/files/2018/03/3544404/outputfile.pdf plots of recent raw waveform data] from [https://logbooks.jlab.org/entry/3544404 Logbook Entry 3544404]. Each page potentially shows four waveforms: the two ends of the test paddle and the two ends of the reference paddle. A missing waveform indicates that there was no waveform data for that end.
+
We need to study how to deal with the significant baseline shift incurred by the AC coupling of the amplifier-in-the-base scheme.
  
His conclusions (exclamations marks his):
+
=== PMT testing ===
  
# Algorithm is not adequate (due to high rates)!
+
In order to look the apparently poor quantum efficiency he was seeing for some PMTs with an LED light source, Sasha set up a test with an Americium source. With this set all PMTs give roughly similar and acceptable efficiency. The cause of the problem with the LED set-up is still under investigation.
# Pulse_Peak zero as error flag causes TOF walk correction to fail!
+
  
From the discussion:
+
Beni asked about gains. The new tubes have gains in the range of 4 to 6&times;10<sup>6</sup>.
  
* The pulses from the amplifier-on-board channel show a significant baseline shift of about 20 ADC counts.
+
=== Action Item Recap ===
* The results of the firmware summary data is also read-out along with the waveform data making comparison possible.
+
* If the first few samples in the window are above baseline, the the algorithm gets confused, often reporting a leading edge at sample 1.
+
* Also, in this case the peak amplitude is reported as 0 (peak=0). Since the current walk algorithm works on the peak amplitude, the hit, including TDC information, is discarded (no walk correction possible). This alone may account for the low efficiency of the TOF in the high rate counters, an effect that Beni identified months ago.
+
* The algorithm is capable of identifying two or more pulses in the raw read-out window, though some of the results disagree what you can see by eye.
+
* The minimum time difference for double pulse separation by the algorithm is much less than that you can see by eye, including cases where the first pulse returns nearly to baseline.
+
  
Bottom line is a large efficiency hit (30-50%) for high rate counters at nominal photon flux due to the way the firmware treats the raw data. In the limit of zero rate, it seems to do fine, so the TOF rates are exposing the problem.
+
* Add items to the list of tests to perform with the remaining run time during Spring 2018:
 
+
*# Test the effect of the raised FADC read-out threshold.
Amelioration strategies:
+
*# Look with a scope at the discriminator input for the amplifier-in-the-base channel.
 
+
* Initiate process of shipping tested PMTs back to JLab from FSU.
* Fall back to using the integral for the time-walk correction in cases where the amplitude is reported as 0.
+
* Read out the waveform data and analyze timing and amplitude offline for regular data taking:
+
*# with channel no sparsification (all channels every event)
+
*# with channel sparsification (all channels above threshold)
+
*# for selected channels, event-by-event (channels which look problematic for the algorithm e. g. peak=0)
+
* Change to firmware to not use amplitude=0 as a flag for pedestal sensing problems.
+
* More sophisticated peak finding algorithm in the firmware.
+

Latest revision as of 14:54, 1 April 2018

GlueX Time-of-Flight Meeting
Wednesday, March 28, 2018
10:00 am EDT
JLab: CEBAF Center, Room F226
BlueJeans Meeting number is 350 531 998

Agenda

  1. Announcements
  2. Review of minutes from the March 14 meeting
  3. Calibration Status
  4. ADC thresholds (Beni)
  5. Amplified Base Prototype (Beni)
  6. PMT testing
  7. NIM Paper (Paul)
  8. Action Item Recap

Slides

Talks can be deposited in the directory /group/halld/www/halldweb/html/talks/2018 on the JLab CUE. This directory is accessible from the web at https://halldweb.jlab.org/talks/2018/ .

Minutes

Present:

  • FSU: Sasha Ostrovidov
  • JLab: Thomas Britton, Eugene Chudakov, Mark Ito (chair), Simon Taylor, Beni Zihlmann

There is a recording of this meeting on the BlueJeans site. Use your JLab credentials.

Changing the Hit Factory

Beni has changed the TOF hit reconstruction code to use the FADC integral for the time-walk correction in the case that the amplitude is set to zero. Recall that this can happen when the voltage is above threshold at the beginning of the FADC read-out window. The ratio used is a hard-wired 0.2 (amplitude/integral). He analyzed a file both before and after this change and sees an increase in TOF efficiency. See logbook entry 3547610 for plots that demonstrate the improvement. It can be greater than 10% in certain regions of the detector.

The timing resolution appears to be a bit worse with the change, but a quantitative assessment is still in progress. Part of this may come from an apparent shift in the timing calibration constants. This is not expected and not understood.

Review of minutes from the March 14 meeting

We went over the minutes.

High Rates and Missed Pulses

There was further discussion of the presentation Beni made at the last meeting on losses at high rates.

  • There were "missing channels" where FADC read-out was completely apparently absent from the event for channels were a pulse was expected. This was a bug. Those pulses are indeed there in the data.
  • The FADC read-out thresholds have been raised for the TOF from 110 counts to 160. This should improve efficiency. The level was chosen to be a bit below that of the discriminatory threshold (thus on the TDC side, note that the signal split is 50-50).
  • The feature of the firmware where "peak=0" is reported is allegedly fundamental in the algorithm and not easy to change.
  • We need to explore schemes where full waveform read-out is done, either selectively, or for every event, because of lost information at high rates.
  • Beni found out that there is an intrinsic dead-time in the discriminator of 20 to 25 ns, independent of input pulse width. This was chosen to match the dead-time of the F1-TDC. Since we are using CAEN TDCs in the TOF, this limits our double pulse separation capability. As a result, a discriminator width of 20 ns is used universally in GlueX.

Amplifier-in-the-Base Tests

We need to study how to deal with the significant baseline shift incurred by the AC coupling of the amplifier-in-the-base scheme.

PMT testing

In order to look the apparently poor quantum efficiency he was seeing for some PMTs with an LED light source, Sasha set up a test with an Americium source. With this set all PMTs give roughly similar and acceptable efficiency. The cause of the problem with the LED set-up is still under investigation.

Beni asked about gains. The new tubes have gains in the range of 4 to 6×106.

Action Item Recap

  • Add items to the list of tests to perform with the remaining run time during Spring 2018:
    1. Test the effect of the raised FADC read-out threshold.
    2. Look with a scope at the discriminator input for the amplifier-in-the-base channel.
  • Initiate process of shipping tested PMTs back to JLab from FSU.