Difference between revisions of "High Intensity Running"
From GlueXWiki
(Created page with " = Overview = This page gathers information related to high intensity (5 x 10<sup>7</sup> γ/s) GlueX running. == Reference Material == * Media:20160722_L3status.pdf|L...") |
(→Reference Material) |
||
Line 7: | Line 7: | ||
* [[Level-3 Trigger Meetings]] | * [[Level-3 Trigger Meetings]] | ||
* [[Media:2007-08-29_VME_DAQ_Rates.pdf|Constraints from VME and Network Interfaces]] | * [[Media:2007-08-29_VME_DAQ_Rates.pdf|Constraints from VME and Network Interfaces]] | ||
− | + | * [https://logbooks.jlab.org/entry/3414529 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 == | == Planning == |
Revision as of 10:21, 29 July 2016
Overview
This page gathers information related to high intensity (5 x 107 γ/s) GlueX running.
Reference Material
- L3 min-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
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.
- What is the L1 trigger rate expected for 5 x 107 γ/s
- What are the expected data rates for each crate?
- How do the rates scale with beam intensity?
- What fraction of events will be reconstructable/usable?
- 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?
- Do the tagger data rates really drop below the FDC when the windows are reduced?