1 / 7

CERN meeting report, and more … D. Breton

CERN meeting report, and more … D. Breton. ETD/online session - Frascati Meeting December 3 rd 2009. Outcome of the CERN meeting (1). The meeting took place beginning of November: Attendance was 14 people (all sub-systems represented, unfortunately except DCH)

cengebretson
Download Presentation

CERN meeting report, and more … D. Breton

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. CERN meeting report,and more …D. Breton ETD/online session - Frascati Meeting December 3rd 2009

  2. Outcome of the CERN meeting (1) • The meeting took place beginning of November: • Attendance was 14 people (all sub-systems represented, unfortunately except DCH) • It was very pleasant and useful • We spent one day going through the ETD architecture once again to convince ourselves our choices were coherent with our goals • No showstopper was raised! • We started discussing about the L1 trigger • New proposals emerged there and since, and we will discuss them in this session. • We finalized the chapters for the white paper (see farther). • We also realized that costing couln’t be performed without realistic numbers for all the different type of fast links, especially the readout links • we requested all the sub-detectors to give us estimations for these numbers before the meeting. • we had fruitful exchanges about these points since, and we have now a first good (?) estimation of these numbers. • We defined « Online » and discussed choices for Online technologies • Could LHC frameworks & packages be directly applicable? • Network protocols for event building and data transport

  3. Outcome of the CERN meeting (2) • Discussing about level 1 trigger, werealizedthatitsgranularityis of high importance for the quality of the selection • In BABAR, crystalsweresummed by 24 beforebeingused in the trigger algorithm, grouped in phi strips • Wethinkthata muchhigher (full?) granularity trigger isfeasiblewithtoday’stechnology (like on LHCb for instance). • To this end, wewouldneed all the calorimeter information to go to the EMT • => like on BABAR, the EMC front-end readoutcouldbeuntriggered • => but the latency buffer couldthenreside in the EMT itself, thuskeeping the sameoverall architecture and a reasonablenumber of ROMs • Drawback of this solution isthat the number of calorimeterreadout links (~ 600) wouldbesignificantlyhigherthan the total of all othersub-detectors (~140) => BABAR like! • Anyhow, we have to find a way to reduce the granularity • detectingoverlap & pileupat trigger level, Bhabha veto, etc. • Once finalized, all chapters of the white papergotnames in front of them and first contributions of all subsystemsalreadyarrived! • These exchanges are reallyhelpful for system understandingat all levels • Werefined the needs for the WBS costestimates (seefarther)

  4. ETD/online chapters for white paper (1) 4.9 System level introduction(DB + UM + SL) Global architecture (DB + UM + SL) Overall trigger strategy (SL + UM) Event Size Estimation and trigger rates (SL + UM) Dead time and buffer queue depth (SL) 4.10 Front-End Electronics (DB) 4.10.1 SVT Electronics (MV) 4.10.2 DCH Electronics (GF) 4.10.3 PID Electronics (DB) 4.10.3.1 Forward PID option 4.10.3.2 Barrel PID 4.10.4 EMC Electronics (VB) 4.10.4.1 Forward calorimeter 4.10.4.2 Barrel calorimeter 4.10.4.3 Backward option 4.10.5 IFR Electronics (ACR)

  5. ETD/online chapters for white paper (2) 4.11 Electronics, Trigger, DAQ (ETD) and Online (DB + UM + SL) 4.11.1 Introduction to ETD (DB) 4.11.2 ETD components (DB) Fast Control and Timing System (DB + DC + CB) Clock, Control & Data Links (AA + RG) Common Front-End Electronics (JM) Read Out Module (MB + UM) Experiment Control System (DC + SL) Low Level Hardware Trigger (DB + UM + SL) 4.11.3 Online (SL + GM) Software infrastructure Event building High Level Software Trigger Data logging Event data quality monitoring and display Other components 4.11.4 Conclusions (DB + UM + SL) Cost estimations consideration

  6. ETD elements for SuperB_costing EDIA [mm] M&S [k€]

  7. What we expect(ed) from this workshop • We will try to refine our estimations for the number of links => done. • the front-end dedicated ETD session (Wednesday at 9:00) will focus on this point. • all the types of links will be visited, including FCTS and ECS • be aware that these elements are deeply related to the system topology • We will go on discussing about level 1 trigger fundamentals in the second session (Thursday at 11:15) • We will wonder what could be an optimum number of readout links at the input of a ROM • We will try to have the first ETD cost estimation ready for the TB => done • Overall ETD cost without L1 trigger is ~1M€ (if 400 links => EMC) • Further discussions on Online (many informal) • Applicability of existing LHC software and frameworks to SuperB Online • Discussion of event building networking protocols and transports • Run Control and Experiment Control System • Review of data logging rates

More Related