1 / 7

Progress on L1Cal at Nevis

Progress on L1Cal at Nevis. Outline RoI Pathologies Communications Paths Latency. H. Evans for the Nevis group. Local Maxima Finding. Et Grid Input. RoI Output (3x3). Local Max Finding uses RoI Grid. Naming LM Algo’s (Declustering) min separation of LMs  data required RoI’s used.

lsolorzano
Download Presentation

Progress on L1Cal at Nevis

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Progress on L1Cal at Nevis Outline • RoI Pathologies • Communications Paths • Latency H. Evans for the Nevis group Run2b L1Cal Meeting: 30-May-02

  2. Local Maxima Finding Et Grid Input RoI Output (3x3) Local Max Finding uses RoI Grid • Naming LM Algo’s (Declustering) • min separation of LMs •  data required • RoI’s used Run2b L1Cal Meeting: 30-May-02

  3. The RoI Definition Matters Declust = 3x3 Declust = 5x5 RoI = 3x3 RoI = 2x2 Conclusion: 2x2 RoI size better matched to asymmetric declustering (but still not perfect) Run2b L1Cal Meeting: 30-May-02

  4. Different RoIs the in MC? • Warning: study still preliminary • Similar behavior (but less pronounced) in WH and tt • General Conclusions • 2x2 RoI more robust than 3x3 to cluster position shifts • 2x2 RoI performance at least as good as 3x3 in MC Single Jet Trigger Two Jet Trigger Eff RoI – Decluster 2x2 – 3x32x2 – 5x53x3 – 5x53x3 – 3x3 Et > 25 GeVother pts in steps of 1 GeV Et > 20 GeV Bgrd Rate [Hz] J. Mitrevski Run2b L1Cal Meeting: 30-May-02

  5. Links in the TAB and GAB Run2b L1Cal Meeting: 30-May-02

  6. ADF to TAB assuming Channel Link serializers/deserializers need to finalize timing/integrity bits c.f. Denis’ presentation Serial Command Link GAB fans out timing/control choose sub-set of signals required for TAB final decision on ADF timing source Trigger Output to Framework hardware required first pass set of And-Or terms L2/L3 Data define data for L2, optimize timing Cal-Track Match for each phi-slice send 2 8-bit words EM: highest cluster Et & count of no. of clust’s in slice Jet: highest cluster Et & count of no. of clust’s in slice optimize the no. of bits allocated to Et/count Downloading/Monitoring define what is necessary L1Cal Communications Run2b L1Cal Meeting: 30-May-02

  7. Latency Run2b L1Cal Meeting: 30-May-02

More Related