Commissioning of the ATLAS Level1 Central Trigger S

Commissioning of the ATLAS Level-1 Central Trigger S. Ask 1), D. Berge 1), N. Ellis 1), P. Farthouat 1), P. Gallno 1), S. Haas 1), A. Krasznahorkay 1)2), T. Pauly 1), G. Schuler 1), R. Spiwoks 1), T. Wengler 3) CERN, Switzerland 2) University of Debrecen, Hungary 3) University of Manchester, UK 1) Thilo Pauly -- LECC 2006 Valencia -- 26 September 2006 1

Overview • Central Trigger installation status – Muon-to-Central-Trigger-Processor Interface (MUCTPI) – Central Trigger Processor (CTP) • Commissioning and integration – Trigger inputs: • Level-1 Calorimeter Trigger (L 1 Calo) • Barrel Muon Trigger (RPC) and MUCTPI – Central Trigger Processor – Trigger outputs: • Distribution of trigger, timing and controls signals, read-out – CTP-Links to sub-system partitions • Level-2 – Combined Cosmics with RPC, MDT (precision muon chambers), tile calorimeter (hadronic), Central Trigger • Results • Conclusions and outlook Thilo Pauly -- LECC 2006 Valencia -- 26 September 2006 2

ATLAS Level-1 Trigger System Calorimeter Detectors Muon Detectors Barrel Muon Trigger (RPC) Pre-processor Cluster Processor (e/γ and τ/h) Jet/Energy Processor Muon-CTP-Interface (MUCTPI) Common Merger Modules TTC Busy TTC Partition Central Trigger Processor (CTP) LTP End-cap Muon Trigger (TGC) . . . LTP TTC Busy Level-2 subject of this talk • Synchronous, pipelined processing at 40 MHz • Level-1 latency: 2000 ns (+ 500 ns safety) • Level-1 output rate: < 100 k. Hz • LTP = Local Trigger Processor (Standard sub-detector interface to the CPT) Detector Front-Ends/Read-out Thilo Pauly -- LECC 2006 Valencia -- 26 September 2006 • TTC = Timing, Trigger & Control • Busy = Tree of Busy Modules • ATLAS has about 40 TTC Partitions 3

MUCTPI at Point 1 • Demonstrator installed • MIOCT: • MICTP: Timing distribution and trigger (muon multiplicities) output to CTP MIROD: S-Link output to Level-2 and ROS MIBAK: custom active backplane for readout and multiplicity summation • • Installed at Point 1 – provides almost full functionality – missing some flexibility in overlap handling (see Stefan Haas) – Input module for octant. Current configuration allows 14 trigger sectors (out of 208) to be connected – Connected with 2 RPC prototype sector logic modules (see Riccardo Vari) Thilo Pauly -- LECC 2006 Valencia -- 26 September 2006 MICTP MIROD MIOCT 4

Central Trigger Processor at Point 1 • • Final modules installed 1 CTP_IN for 4 trigger input cables – 2 more to come CTP_MI: Machine interface (clock and orbit input) CTP_MON: Monitoring of trigger input per bunch crossing ID CTP_CORE: Trigger decision according to trigger menu 4 x CTP_OUT: Output to subdetectors NIM-to-LVDS converter module to connect individual trigger signals Two more CTP systems in laboratory for hardware test and software development Thilo Pauly -- LECC 2006 Valencia -- 26 September 2006 Installed at Point 1 5

Trigger Inputs - L 1 Calo • Integration test to CTP in July: – sent known pattern at 40 MHz from L 1 Calo Common Merger Module (final) to CTP_IN – receival of patterns in CTP_IN memory and comparison with known pattern – no errors found over 15 minutes – minor firmware bug discovered in treatment of parity – two faulty cables discovered Thilo Pauly -- LECC 2006 Valencia -- 26 September 2006 6

Trigger Inputs - RPC/MUCTPI • Barrel Muon Trigger (RPC) Sector 13: • Connection between two RPC prototype sector logic modules and MUCTPI: – link 0: towers 0+1 – link 1: tower 2 – link from MUCTPI to CTP�� • – Sector 13 is so far the only sector fully equipped with cables and services – Barrel Middle and Barrel Outer Chambers used, defining 6 trigger towers RPC 1 RPC 2 CTP: RPC 3 NIM OR link 0/link 1 Thilo Pauly -- LECC 2006 Valencia -- 26 September 2006 3 4 5 0 1 2 link 0 Sector 13 – one NIM trigger signal from sector 13 – CTP configured to trigger on: NIM signal link 1 7

Trigger inputs - RPC/MUCTPI • MUCTPI: CTP – phase measured of link 0 and link 1 clock – link from MUCTPI to CTP MUCTPI • CTP: – phase measured between MUCTPI input and clock – NIM signal delayed by 6 BC wrt MUCTPI signals • due to MUCTPI latency link 0 Thilo Pauly -- LECC 2006 Valencia -- 26 September 2006 3 4 Link 0 5 0 1 2 Sector 13 NIM signal link 1 8

Central Trigger Processor • Central trigger hardware well integrated with the ATLAS Run Control • Configuration from trigger database possible – Simple trigger menu for integration with muons: ATLAS Run Control • require at least one muon candidate from MUCTPI for any pt threshold • sector 13 NIM trigger • GPS-timestamp for each accepted event from General-Machine-Time receiver • Deadtime mechanism tested • Basic monitoring tools: Monitoring – deadtime – L 1 A counters in CTP and MUCTPI – Muon multiplicity counters in MUCTPI Thilo Pauly -- LECC 2006 Valencia -- 26 September 2006 9

Distribution of trigger, timing and controls signals, read-out • Signals: – Clock, Orbit, L 1 A, ECR (event counter reset) – BUSY (backpressure from readout) • CTP: – Clock and orbit are received from machine (RF 2 TTC, see Sophie Baron) or generated internally – ECR generated periodically with 0. 1 -1 Hz – Internal distribution in the CTP VME crate LTP • MUCTPI: – distribution directly via LEMO cables • other sub-systems: – differential link (10 -30 m) between CTP_OUTs and sub-system Local Trigger Processor (LTP) Thilo Pauly -- LECC 2006 Valencia -- 26 September 2006 TTC 10

CTP Links to Sub-System Partitions 1 Clock Orbit C T P 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 Thilo Pauly -- LECC 2006 Valencia -- 26 September 2006 Pixels Local Trigger Processor SCT Installed and tested TRT L 1 Calo LAr Barrel LAr EMEC LAr HEC LAr FCAL (to be combined with LAr HEC) Tile Long-Barrel Tile Ext-Barrel RPC MDT Barrel MDT End-Cap TGC-A TGC-C (to be combined with TGC-A) CSC Roman Pots 11

Readout of the Central Trigger • Final readout links (S-Link) to Readout systems (ROS, 2 PCs) MUCTPI CTP Readout Link • Connection tested in standalone mode: – consistency between the MUCTPI and CTP data – rate limited by temporary event building to about 25 k. Hz – backpressure mechanism functional Thilo Pauly -- LECC 2006 Valencia -- 26 September 2006 ROS control network temporary event builder File 12

Integration with Level-2 • see also: Yuri Ermoline • Test: Comparison of central level-1 trigger data from two different streams, after event building (in SFI): – trigger stream – readout stream • Read out both streams at 20 k. Hz – rate limited by backpressure from Level-2 – no errors found – minor problem with identifiers found and fixed Thilo Pauly -- LECC 2006 Valencia -- 26 September 2006 Underground MUCTPI CTP Ro. I Readout System Region-of. Interest Builder Level-2 Supervisor Dataflow Manager L 2 PU Event building L 2 Result Handler Surface 13

Combined Cosmics with RPC, MDT, Tilecal • Combined cosmics run with sector 13 in August – Temporary gas systems operational both for RPC and MDT • Combined partition: – Trigger: RPC, MUCTPI, CTP – Readout: RPC, MDT, Tilecal, L 1 Central • timing-in: guess & try Tile. Cal MDT RPC Trigger path Readout path CTP Mu. CTPI – about 500 k events recorded at 40 Hz Thilo Pauly -- LECC 2006 Valencia -- 26 September 2006 14

Results from combined cosmics: MUCTPI + CTP 50% NIM (0 candidates) 50% NIM+MUCTPI only NIM signal Sector logic candidates 3 4 5 0 1 2 link 0 Sector 13 NIM signal 40 Hz CTP NIM + Sector Logic M U C T P I NIM link 1 C T P Thilo Pauly -- LECC 2006 Valencia -- 26 September 2006 MUCTPI 15

Results from combined cosmics: CTP Time difference between consecutive events: Exponential, as expected from cosmics Thilo Pauly -- LECC 2006 Valencia -- 26 September 2006 20 BC (500 ns) of deadtime introduced 16

Results from combined cosmics: MUCTPI, CTP, and RPC OK. Some bugs in sector decoding found Thilo Pauly -- LECC 2006 Valencia -- 26 September 2006 17

Level-1 latency • • time RPC readout window: 1825 -2000 ns (70 -80 BCs) – from chamber hit to arrival of L 1 A – consistent with latency budget of 2000 ns (+500 ns safety) 4 BC Trigger input: – RPC(SL) --> MUCTPI: 3 BC – MUCTPI: 6 BC OK – RPC(NIM) --> CTP: 3 BC • delayed in CTP_IN by 6 BC to align with MUCTPI trigger inputs • • 4 BC Trigger decision: – CTP: 4 BC OK 6 BC 3 BC CTP MUCTPI RPC Sector Logic Trigger distribution: – CTP --> RPC: 4 BC Thilo Pauly -- LECC 2006 Valencia -- 26 September 2006 18

Combined cosmics: some results� Thilo Pauly -- LECC 2006 Valencia -- 26 September 2006 19

Conclusions • Level-1 Central Trigger (CTP and MUCTPI) is installed and functional at Point-1 with mainly final hardware • A complete trigger and read-out chain has been successfully operated in the cavern with cosmics – CTP triggered on signals from barrel muon trigger (sector 13) – Read out RPC, MDT, Tilecal, CTP and MUCTPI • First integration tests with Level-2 were successful • Integration and commissioning is in full swing – More trigger inputs soon – More detectors to be read-out – Need systematic strategy of treating a bigger system (timing-in, monitoring, configuration, . . . ) Thilo Pauly -- LECC 2006 Valencia -- 26 September 2006 20

Outlook: Looking forward to. . . receiving trigger signals from end-cap muon trigger and calorimeter trigger End-cap muon trigger L 1 Calorimeter Trigger . . . reading out more parts of ATLAS Integration and commissioning continues. . . Thilo Pauly -- LECC 2006 Valencia -- 26 September 2006 21

backup Thilo Pauly -- LECC 2006 Valencia -- 26 September 2006 22

ATLAS Trigger DAQ Trigger 40 MHz DAQ 40 MHz Level 1 Calo Mu. Tr. Ch Other detectors 2. 5 ms Det. R/O L 1 accept (100 k. Hz) 100 k. Hz O(500) PCs Ro. I ROIB L 2 ~3 k. Hz High Level Trigger Ro. I requests L 2 SV L 2 accept (~3. 5 k. Hz) ROD ROB ROB ROS O(150) PCs ~4 GB/s DFM EBN EB O(100) PCs SFI EFN ~ sec EF ROD Ro. I data (~2%) L 2 N L 2 P O(1900) PCs ~10 ms ROD 120 GB/s EFP ~ 200 Hz Thilo Pauly -- LECC 2006 Valencia -- 26 September 2006 EF accept (~0. 2 k. Hz) SFO Dataflow ~ 300 MB/s 23