Skip to Content.
Sympa Menu

sphenix-tpc-l - [Sphenix-tpc-l] TPC trigger latency

sphenix-tpc-l AT lists.bnl.gov

Subject: Sphenix-tpc-l mailing list

List archive

Chronological Thread  
  • From: Martin Purschke <purschke AT bnl.gov>
  • To: "sphenix-tpc-l AT lists.bnl.gov" <sphenix-tpc-l AT lists.bnl.gov>
  • Subject: [Sphenix-tpc-l] TPC trigger latency
  • Date: Fri, 20 Oct 2017 13:09:30 -0400

To the TPC aficionados -

I'm in the process of compiling the "trigger latency map", usually
expressed as the number of beam crossings we can let go by before we
need a trigger decision. For example, the INTT allows for 70 ticks (data
from 64 crossings stored, plus 6 crossings before the data from a given
crossing reaches the FEM).

I'm aware that a number of assumptions will have to be made for the
answer, especially the assumption that we will be able to correlate the
streaming data with triggered events. This is both a matter of technical
feasibility and of the "waveform overlap fraction" for close-by events,
namely, can we afford the duplication of waveform snippets where they
overlap in time? We believe that the answer to the former is a
tentative "yes" and to the second a "most likely". I recall a 6% data
duplication figure but might not remember it correctly.

JohnK and I started to discuss this and the assorted strategies. I would
ask you guys to toss that around some in the larger group so everyone is
on the same page. If you come up with an answer that is guaranteed to be
larger than about 70 ticks, you will not be constraint and can stop
calculating it more accurately.

Preferably I would like the answer before the end of next week, as we
want to get going polishing the CDR and this is the key number the LL1
triggers need.

Thanks a bunch,

Martin

--
Martin L. Purschke, Ph.D. ; purschke AT bnl.gov
; http://www.phenix.bnl.gov/~purschke
;
Brookhaven National Laboratory ; phone: +1-631-344-5244
Physics Department Bldg 510 C ; fax: +1-631-344-3253
Upton, NY 11973-5000 ; skype: mpurschke
-----------------------------------------------------------------------




Archive powered by MHonArc 2.6.24.

Top of Page