High Intensity Running
Contents
[hide]Overview
This page gathers information related to high intensity (5 x 107 γ/s - 50 MHz in 8.4-9.0 GeV) GlueX running.
Reference Material
- L3 mini-review Slides (7/22/2016 )
- Level-3 Trigger Meetings
- Constraints from VME and Network Interfaces
- Flux: evaluation of the photon flux for Spring 2016 - 10Mhz (8.4-9.0 GeV) with the old "50 µm" diamond, PERP mode, 5mm collimator, beam 130µA
Planning
Task Force Meetings
- Sep. 15, 2016 : High Luminosity Test Plan Meeting 9/15/2016
- Aug. 26, 2016 : Event Sizes (David)
- Aug. 18, 2016 : Event Sizes (David)
Near-term Questions
Here is a place to gather some questions that need to be answered in order to properly plan for high intensity running.
- L1 trigger
- What is the L1 trigger rate expected for the 50 MHz beam, extrapolating the Spring 2016 conditions: the FCAL+BCAL trigger? other triggers? The accidentals should be considered.
- What is a reasonable ratio of various trigger types (PS to Physics, etc ...) at high intensity?
- PS = 1kHz
- FCAL-BCAL = XXX
- other = 5% of BCAL/FCAL assuming same event length
- What is the relative drop of the trigger efficiency for a twice more stringent FCAL+BCAL trigger, which would leave 50% of the events of the 2016 Spring run? What is event size for these?
- What is the L1 trigger rate expected for the 50 MHz beam, extrapolating the Spring 2016 conditions: the FCAL+BCAL trigger? other triggers? The accidentals should be considered.
- DAQ
- How do the event sizes scale with the beam intensity (for the triggers used)?
- What are the expected data rates for each crate?
- How do the data rates scale with beam intensity?
- Can we reduce the data read from each crate by dropping headers or reformatting? (e.g. fADC125 Trigger Times)
- Can we reduce the data read from each crate by reducing readout windows?
- FDC/CDC = NO
- TOF=YES (factor of 10 for TDC, factor of 4 for fADC)
- TAGGER=YES (factor of 8=50ns) up to 20 hits per event (each crate)
- PS=N/A
- Do the tagger data rates really drop below the FDC when the windows are reduced?
- estimate says YES
- What is the real limit on the VME data transfer speed considering the bus clocks and the duty cycles provided by various modules?
- What crates (FDC?) would limit the DAQ capabilities at the VME transfer level?
- What crates would limit the DAQ capabilities at the Ethernet level? What gain a 10 Gb interface would provide?
- How do the event sizes scale with the beam intensity (for the triggers used)?
- L3
- What would be the largest reduction factor at "high intensity" (long events), if no time limit is considered?
- How many nodes are needed for a reduction factors of 4 at a 100 kHz event rate?
TOF
rates for PMTs of selected paddles, paddle 1 to 19 are regular width/length paddles, paddle 20 and 21 are narrow width long paddles and paddle 22 is a short single ended paddle. The rates are in Hz as a function of beam current in nA. The data are from runs 11634 to 11637 where luminosity scans were done from 40 to 140nA. The collimator was set to 5mm diameter and the radiator is 3x10-4 with LH target full.
- TOF Rates with 20um Diamond 3.4mm diameter collimator PARA and PERP
- TOF Rates with 50um Diamond 5.0mm diameter collimator PARA and PERP
- TOF Rates with 20um Diamond 3.4mm diameter collimator PARA high intensity run11359-11363 (200-400 nA),:
SC/FCAL/BCAL/CDC
Various rates as a function of beam current. Run 11566 (I=80nA) and runs 11359-11363 (200-500 nA), with the coherent beam in PARA orientation and the collimator with 5mm diameter.
The start counter and BCAL rates are given as averages over the entire detector, while the FCAL and CDC rates are given for selected detector elements. The FCAL rates are given for specific blocks, while the CDC rates are averages over rings.