1. Karol Buńkowski CERN, UW On behalf of the Warsaw CMS group PAC trigger in the high eta region based on the MPGD detectors – electronic system GEMs for CMS High Eta - Workshop II, 24 June 2011

2. 2 Three possibilities for the PAC trigger electronics upgrade Option 1 Use the current RPC PAC Trigger Boards for the high eta Option 2 Build new Trigger Boards for the high eta, but connect them to the current RPC PAC Trigger Crates Option 3 Build new RPC Trigger electronics for the entire detector Karol Buńkowski, CERN, UW, GEMs for CMS High Eta - Workshop II, 24 June 2011

3. 3 Current RPC PAC Trigger system Karol Buńkowski, CERN, UW, GEMs for CMS High Eta - Workshop II, 24 June 2011

4. 4 Counting roomDetector FEB RPC PAC muon trigger Trigger Board PAC Resistive Plate Chambers Up to 6 layers of detectors. 480 chambers in barrel, 504 in endcaps FEB Control & diagnostic Ghost Buster & Sorter RMB To the Global Muon Trigger Link Board Synchronization Unit & LMUX Optic Links 90 m @ 1.6 GHz 1104 fibers LVDS cables To Data Acquisition GB & Sor ter Data Concentrator Card 1232 Link Boards in 96 Boxes, Steered by Control Boards 84 Trigger Boards in 12 Trigger Crates Data transmission @ 320 MHz SYN CH. & LD MU X * Numbers of elements for the staged version of the system Karol Buńkowski, CERN, UW, GEMs for CMS High Eta - Workshop II, 24 June 2011

5. Marcin Konecki, University of Warsaw -5- Trigger Crate Processes data from the detector wedge 30  (logic sector) in . Contains 7 Trigger Boards (staged system |  | <1.6), has slots for 2 additional TBs for the high eta region |  | <2.1 Optical links from the detector are split and go to 2 or 4 TBs.

6. 6 Trigger Board Karol Buńkowski, CERN, UW, GEMs for CMS High Eta - Workshop II, 24 June 2011 Trigger Board process data from the 3 or four towers of one logic sector. -18 inputs of the optical links -4 PAC chips (one chip per logic sector of one trigger tower) – trigger algorithm ALTERA STRATIX II (30 or 60). Currently (independently of upscope) new PAC TB mezzanine is designed to host ALTERA CYCLONE. -Readout Mezzanine Board – data acquisition -Complex and expensive board

7. 7 Phi segmentation Karol Buńkowski, CERN, UW, GEMs for CMS High Eta - Workshop II, 24 June 2011

8. Marcin Konecki, University of Warsaw -8- Eta segmentation GEMs for CMS High Eta - Workshop II, 24 June 2011 GE1/1 (possibly doubled) GE2/1 RE3/1 RE4/1

9. 9 Pattern Comparator trigger algorithm Chamber hits are compared with predefined set of patters obtained from the simulations. Patterns correspond to muons tracks of defined p T. Projective geometry is favoured with strip size of 2  /1152 ≈ 0.3 deg Muon candidate is generated when : –Barrel: 3 out of 4 inner chamber layers are fired (to accept low p T muons not reaching the outer stations) 4 out of 6 (5) chamber layers are fired (high p T muons) –Endcap 3 out of 3 (4) chamber layers are fired and chamber hits fit to at least one pattern. The hits must be in the same BX Muon position measurment: –In  with granularity: ~0.2 (barrel) - ~0.12 (endcap). Eta unit is trigger tower, –In  with granularity 1/144 × 2  ( = 0.223 rad = 2.5  ). Phi unit is logical segment Karol Buńkowski, CERN, UW, GEMs for CMS High Eta - Workshop II, 24 June 2011

10. 10 Trigger system for the high eta – integration with the current RPC PAC trigger system Karol Buńkowski, CERN, UW, GEMs for CMS High Eta - Workshop II, 24 June 2011

11. 11 Versatile Link (a.k.a. G-Link system) The electronic system for the high eta MPGD system will be (most probably) based on the G-Link G-Link - new CERN project https://espace.cern.ch/project-versatile-link/public/default.aspx Radiation hard bi-directional optical link for use in the LHC upgrade program. The link targets data transmission between the on-detector and off-detector electronics serving simultaneously applications such as data acquisition, timing, trigger and experiment control: https://espace.cern.ch/project-versatile-link/public/default.aspx –GBT - radiation hard chipset http://cern.ch/proj-gbt https://indico.cern.ch/getFile.py/access?contribId=4&resId=0&materialId=slides&confId=132452 http://cern.ch/proj-gbthttps://indico.cern.ch/getFile.py/access?contribId=4&resId=0&materialId=slides&confId=132452 –GLIB - Gigabit Link Interface Board https://espace.cern.ch/project-GBLIB/public https://indico.cern.ch/getFile.py/access?contribId=5&resId=0&materialId=slides&confId=136793 https://espace.cern.ch/project-GBLIB/public

12. 12 GLIB - Gigabit Link Interface Board GEMs for CMS High Eta - Workshop II, 24 June 2011  Mid-size double-width Advanced Mezzanine Card (AMC)  Serves as an evaluation platform and an easy entry point for users of high speed optical links.  4 SFP+ transceiver modules  Virtex-6 FPGA with twenty 6.5Gbps transceivers.  I/O capability can be further enhanced with two FPGA Mezzanine Cards (FMC).  Gigabit Ethernet link to PC for bench-top operation.

13. 13 GLIBs in the  TCA crate Example of the experimental setup All-in-one system: Receiving of data from the detector Data acquisition Trigger Control of the on-detector electronics (DCS, equivalent of the FEC/CCU system used in the RPC system) TTC distribution to the on-detector electronics Karol Buńkowski, CERN, UW,

14. 14 MPGD-PAC architecture Option 1 Karol Buńkowski, CERN, UW, GEMs for CMS High Eta - Workshop II, 24 June 2011 Counting room Detector MPGD Link Board GLIB FPGA Custom AMC  TCA Crate To Final Sorter DAQ Trigger Board towers 13-16 Trigger Crate Sector n DAQDCSTTC @ 3.2 Gbps GBT Front-ends VFAT/GdSP @ 1.6 Gbps Trigger Crate Sector n-1 The optical links from the detector go to the GLIB boards in the dedicated  TCA crates (one optical link per chamber?). On the GLIBs the data are processed and converted into the format the same as RPC Link Board data (zero- suppression multiplexer, GOL-like serializer ). The custom mezzanine contains 1.6 Gbps optical transmitters (~LB like) On the GLIBs the data are processed and converted into the format the same as RPC Link Board data (zero- suppression multiplexer, GOL-like serializer ). The custom mezzanine contains 1.6 Gbps optical transmitters (~LB like) The trigger algorithm is performed in the PAC chips on the standard RPC TBs

15. 15 Optical links for one high eta Trigger Board (towers 13-16) Karol Buńkowski, CERN, UW, GE1/1 5 ×10  chambers Up to 10 optical links GE2/1 3 ×10  chambers RE3/1 5 ×10  chambers 2 optical links RE3/2 5 ×10  chambers 2 optical links RE4/1 5 ×10  chambers 2 optical links RE4/2 5 ×10  chambers 2 optical links In principle chamber data can be freely arranged in the links Fixed, as have to be compatible with the reset of the RPC system GEMs for CMS High Eta - Workshop II, 24 June 2011

16. 16 MPGD-PAC architecture Option 2 Karol Buńkowski, CERN, UW, GEMs for CMS High Eta - Workshop II, 24 June 2011 Counting room Detector MPGD Link Board GLIB New TB FPGA  TCA Crate To Final Sorter DAQ Interface Board towers 13-16 Trigger Board Trigger Crate Sector n From TC splitters (RE3 and RE4) DAQDCSTTC @ 3.2 Gbps GBT Front-ends VFAT/GdSP @ 3.2 Gbps The optical links from the detector go to the GLIB boards in the dedicated  TCA crates (one optical link per chamber?). New Trigger Boards (only for high eta) are placed in the  TCA. The chamber data from GLIBs are transmitted over the backplane and with optic links between the crates. Data from the TCs are also needed (RE3 and RE 4). Each new Trigger Board transmits 4 muon candidates to the old TC (60 bits/BX) New Trigger Boards (only for high eta) are placed in the  TCA. The chamber data from GLIBs are transmitted over the backplane and with optic links between the crates. Data from the TCs are also needed (RE3 and RE 4). Each new Trigger Board transmits 4 muon candidates to the old TC (60 bits/BX) In the Trigger Crate an interface board is placed which converts the optical signal into the format required by the TC Ghost Buster (8 × 320 Mbps LVDS) From other  TCA Crate

17. 17 MPGD-PAC architecture Option 2 - Motivation If the GE1/1 is doubled, and if we want to use the full granularity of the GEMs in the trigger, the input bandwidth of the current Trigger Board might not be sufficient to delivered the GE1/1 and GE2/1 data to the PACs –10 optical links @ 1.6 Gbps can be used for the GE1/1 and GE2/1, the real bandwidth of the link is 21 bits / BX due to on TB transmissions Karol Buńkowski, CERN, UW, GEMs for CMS High Eta - Workshop II, 24 June 2011

18. 18 Issue for Option 1 and 2 Link Boards for the RE3/1 and RE4/1 – will it be possible to produce them in ~5 years? Who will do it? Karol Buńkowski, CERN, UW, GEMs for CMS High Eta - Workshop II, 24 June 2011

19. 19 MPGD-PAC architecture Option 3 Karol Buńkowski, CERN, UW, GEMs for CMS High Eta - Workshop II, 24 June 2011 Counting room Detector RPC or MPGD Link Board GLIB New TB FPGA  TCA Crate To GMT Final Sorter DAQDCSTTC @ 3.2 Gbps GBT Front-ends VFAT/GdSP @ 3.2 Gbps For the RPCs the current Link Boards will have to be replaced by new boards with the GBT chipset New electronics for entire RPC/MPGD PAC trigger system based on the  TCA and GLIBs. The chamber data from GLIBs are transmitted over the backplane and with optic links between the crates (as trigger regions must overlap). From other  TCA Crate

20. 20 MPGD-PAC architecture Option 3 - motivations Karol Buńkowski, CERN, UW, GEMs for CMS High Eta - Workshop II, 24 June 2011 New electronics for entire RPC/MPGD PAC trigger system based on the  TCA crates, GLIBs and new Trigger Boards Motivations: In 2019 the Link Boards, Trigger Boards and Trigger Crates (VME) will be already over 10-12 years old. LHC upgrade to luminosity 2×10 34 Better trigger algorithms can be implemented into bigger PAC FPGAs, so the current TBs still can be used. But will it enough to assure required performance? LHC upgrade to luminosity > 5×10 34 The Link Boards might not be able to stand the higher radiation The current Muon Trigger (DT/CSC/RPC/GMT) will not work for the higher luminosity – the output single muon trigger rate higher then allowed a few tens of kHz for any p T cut  Tracking Trigger task force

21. 21 Data processing latency as for the RPC 2Time of flight (max) 1chambers + FEBs 5cables (max) LB 3synchronizer 2Coder (data compression) 2slave-master transmission 0data delay (minimal) 2multiplexer 2GOL 22fiber TB 2TLK 0Link input delay 7Opto 5Opto - PAC transmission 11PAC algorithm (8 BX for demultiplexing) 6PAC - TB Sorter transmission 2TB GBS algorithm 6TB Sorter - TC Sorter transmission TC Back 2TC GBS algorithm 5TC - HSB transmission HSB2Half GBS algorithm 2HSB - FSB transmission FSB1Final Sorter algorithm 92Total Current latency from interactio n point to the RPC PAC trigger output 11 BXs 18 BXs – total time available for detector, front-end, data transmission between boards and chips, data processing before introducing into the optical lins The timing of signals in PAC trigger logic is thight. Must be taken into account in MPGD readout design 41 BX 51 BX GEMs for CMS High Eta - Workshop II, 24 June 2011

22. 22 Performance of the original PAC trigger in the endcap region Karol Buńkowski, CERN, UW, Rate vs tower for pt Cut >140GeV, TDR geometry 4 stations, all towers (chamber eff=0.95 avg cl=1.5, no noise) In the region  > 1.6 the performance of the default PAC trigger (RPC geometry) is quit good. The most difficult region is the  = 1.24- 1.61 (towers 10-12)  = 1.61  = 1.24 Quality GEMs for CMS High Eta - Workshop II, 24 June 2011 Why no rate from the RPC in the endcaps at the moment? Because now only 3 station available, all required in the trigger  efficiency ~80%, but at the same time promotion of the low pt muons to high pt candidates is suppressed

23. 23 Dreams of PAC trigger person: The bending power degradates with increasing eta but is partially recovered when RE1/1 became active. Towers 10-12 are worst. An additional measurement could lead to important improvement. Due to fine granularity of MPGD and robust PAC design additional coincidences from double layer station may help Note the strip projective topology Tower 4Tower 11Tower 15

24. 24 Tracking Trigger Task Force CMS Upgrade Week, Tracking Trigger Task Force meeting, Wednesday 11 May 2011 https://indico.cern.ch/conferenceDisplay.py?confId=138450 There is now a consolidated expectation for Sustained Operation at Luminosity > 5.4 * 10 34 (nb. Luminosity Leveled) Baseline is 25ns => Pile-up ~ 100 However, 50ns provides more margin to meet luminosity target 50ns => Pile-up ~ 200 =>must make allowance also for this scenario Karol Buńkowski, CERN, UW, GEMs for CMS High Eta - Workshop II, 24 June 2011

25. 25 Muon trigger rates at Luminosity > 5.4×10 34 Extrapolation from current data to 5 x 10 34 cm –2 s –1 Muon Trigger Thresholds & Rates Naïve –Single:25 GeV / 100 kHz –Double:5 GeV / 33 kHz Realistic –Single:No control on threshold –Double:20 GeV / 10 kHz Muon rate vs threshold is flat at high p T –We assume this is partly fixed by EMU phase-1 upgrades From The Physics Case, Sridhara Dasu https://indico.cern.ch/getFile.py/access?contribId= 1&resId=0&materialId=slides&confId=13845 0 Karol Buńkowski, CERN, UW, GEMs for CMS High Eta - Workshop II, 24 June 2011 Muon L1 trigger rate L = 10 34 Standalone Muon trigger resolution insufficient Current muon trigger rate are at least a few times higher then on the plot

26. W. Smith, U. Wisconsin, Tracking Trigger Task Force Trigger Challenges & Opportunities - 26 CMS L1 Track Trigger for Muons Combine with L1  trigger as is now done at HLT: Attach tracker hits to improve P T assignment precision from 15% standalone muon measurement to 1.5% with the tracker Improves sign determination & provides vertex constraints Find pixel tracks within cone around muon track and compute sum P T as an isolation criterion Less sensitive to pile-up than calorimetric information if primary vertex of hard-scattering can be determined (~100 vertices total at SLHC!) To do this requires  information on muons finer than the current 0.05  2.5° No problem, since both are already available at 0.0125 and 0.015°

27. 27 RPC/MPGD in the tracking trigger??? When the luminosity 5×10 34 will be? Is it worth to consider this scenario in a view of the high eta system design? What will be a role of the RPC system in this scenario? What will be a role of the MPGD system in this scenario? Karol Buńkowski, CERN, UW, GEMs for CMS High Eta - Workshop II, 24 June 2011

28. 28 Backup Karol Buńkowski, CERN, UW, CMS Trigger Upgrades Meeting, 21 March 2011

29. 29 CMS magnetic field

30. 30 Relative performance Quality Rate

31. 31 RPC PAC trigger in the high  region original design Karol Buńkowski, CERN, UW, CMS High Eta MPGD – Workshop, 30 September 2010 RE1/1 10 , 128 strips RE2/1 20 , 256 strips 20  RE3/1, RE4/1 20 , 128 strips Strip width: 360  /1152= 0.3125  = 0.8 - 1.3 cm

32. CMS forward region – staged RPC system Station RE4 and eta < 1.6 (RE 1/1, RE2/1, RE3/1) de-scoped/postponed because: budget insufficient not certain RPC’s would survive 10 34 (high eta case)  wait for: operational experience possible alternate technology

33. 33 Link System (UXC) Link Boxes are placed on the detector balconies Link Board: 96 input channels (LVDS, asynchronous signals form Front End Boards) Data processing: -Synchronization of the input signals, -Compression (zero suppression) -Multiplexing of the compressed data from 3 LBs (two Slave LBs and Master LB) -Conversion to the optical signal 1.6 GHz (GOL chip on the Master LB), Control Board Crate controller based on the FEC/CCU system Karol Buńkowski, CERN, UW, CMS High Eta MPGD – Workshop, 30 September 2010

34. 34 LB data compression algorithm Is it possible to transmit more trigger strips then in the original design with use of the original design links? The 96-bit input data vector of a given clock period (BX) is divided into 12 partitions of 8 bits each. The non-empty partitions are selected and send one-by-one in the consecutive BXs. Each partition is supplied with the “partition number” and “partition delay” information. Complete optical link data frame - 21 bits (transmitted within 25 ns): –8 bits of the partition data, –4 bits of partition number, –3 bits of partition delay, –2 bits of LB number (added during data multiplexing on the Master LB) –1 bit – EOD (end-of-data) – set when there was to much frames and some were lost, –1 bit – “half partition” (unused), –2 bits - unused Effectively it is possible to code and transmit via one link: 64 partitions (with use of 6 bits) = 512 strips, or even 512 partitions (with use of 9 bits) = 4096 strips. Karol Buńkowski, CERN, UW, CMS High Eta MPGD – Workshop, 30 September 2010

35. 35 Link occupancy with the RPC LB cmopression schema The constraints of the LB data compression algorithm: - Only 8 frames can be transmitted from a given BX maximally. - On the average maximally one frame per BX can be transmitted The probability that a data are lost due to saturation depends only on the chamber occupancy (distribution of probability of having given number of hits in one BX) and the cluster size distribution, but not on the strips granularity (number of strips transmitted via one link). The realistic simulation of the chamber occupancy is needed, as well as results of the chamber performance. Simple Monte Carlo: Hit rate: 2 kHz/cm 2 (big safety margin), chamber surface (RE1/1) 4100 cm 2  chamber rate 8.2 MHz = 0.2 hit/BX  probability of having more than 4 hits in the same BX is 3x10 -6 (Poisson distribution)  The probability that the data are lost in given BX because the link is saturated is ~2x10 -5. Karol Buńkowski, CERN, UW, CMS High Eta MPGD – Workshop, 30 September 2010

36. 36 Optical links detector – Trigger Board Transmitter – standard LHC GOL –@ 1.6 Gbit/s, “Ethernet fast” mode –32 bits/BX (+8 bits/BX due to 8B/10B) Receiver: TLK2501 Opto – PAC & RMB transmission: –21 bits/BX (+3 for parity checking) 18 such links for the Trigger Board Karol Buńkowski, CERN, UW, GEMs for CMS High Eta - Workshop II, 24 June 2011

37. 37 Timing resolution Signals timing =  time of flight  signal formation in the detector  signal propagation along the strip   discrimination At least 99% of hits inside 25 ns Karol Buńkowski, CERN, UW, MPGD Upgrade Electronics Meeting 1, 7 April 2011

38. 38 Karol Buńkowski, CERN, UW, CMS Trigger Upgrades Meeting, 21 March 2011 Trigger TDR, 2000

39. 39 Karol Buńkowski, CERN, UW, GEMs for CMS High Eta - Workshop II, 24 June 2011

40. 40 Next slides Tracking Trigger Task Force, Wednesday 11 May 2011 The Physics Case, Sridhara Dasu https://indico.cern.ch/getFile.py/access?contrib Id=1&resId=0&materialId=slides&confId=138 450 Karol Buńkowski, CERN, UW, GEMs for CMS High Eta - Workshop II, 24 June 2011

41. Current Thresholds & Rates Extrapolation from data collected –For 2 x 10 33 cm –2 s –1 Electron / Photon Trigger –Single:30 GeV / 1.5 kHz –Double:10 GeV / 1.4 kHz Muon Trigger –Single:10 (25) GeV / 11 (4.1) kHz –Double:5 GeV / 1.3 kHz Sridhara Dasu (Wisconsin)41

42. Naïve 5 x 10 34 cm –2 s –1 Thresholds & Rates Extrapolation from data collected –For 5 x 10 34 cm –2 s –1 Electron / Photon Trigger –Single:30 GeV / 38 kHz –Double:10 GeV / 34 kHz Muon Trigger –Single:25 GeV / 100 kHz –Double:5 GeV / 33 kHz Certainly does not work without raising thresholds However, muon rate vs threshold is flat at high p T –We assume this is partly fixed by EMU phase-1 upgrades Sridhara Dasu (Wisconsin)42

43. EMU Phase 1 Upgrades Sridhara Dasu (Wisconsin)43 Phase-1 upgrade lowers the rate and provides some control but above 30 GeV it gets flat again with L1 muon resolution

44. Realistic 5 x 10 34 cm –2 s –1 Thresholds & Rates Extrapolation from data collected –For 5 x 10 34 cm –2 s –1 Electron / Photon Trigger –Single:> 50 GeV / 20 kHz –Double:30 GeV / 20 kHz Muon Trigger –Single:No control on threshold –Double:20 GeV / 10 kHz Double triggers could have additional contribution from PU, but is not included above Are these acceptable for physics of HL-SLHC? Sridhara Dasu (Wisconsin)44

45. W. Smith, U. Wisconsin, Tracking Trigger Task Force Trigger Challenges & Opportunities - 45 Key Principles of Trigger Upgrade Hold the Level 1 Accept Rate at 100kHz (plus side) Avoids as much as possible rebuilding front ends & readout (minus side) Puts more pressure on DAQ to deal with increased data size Employ full information from detectors in trigger Calorimeter granularity: 0.087 ✕ 0.087 in η ✕ Φ (presently 4x more coarse) CSC trigger: use all track segments (now take only top 2 or 3/sector) Rely on powerful modern FPGAs with huge processing & I/O capability to implement more sophisticated algorithms Diversity  uniformity in boards using programmability of new FPGAs Take advantage of FPGA capabilities to provide flexibility for new ideas Phase in use of state of the art telecom technology (micro-TCA) to support increased bandwidth requirements where feasible Replaces VME to ease obsolescence/maintenance in larger systems Also achieves some hardware standardization Usable in service cavern where there is no radiation Manage upgrade of a running experiment Evolve from maintenance & R&D into upgrade Test at Electronics Integration Center in Prevessin then at point 5 in parallel with existing running trigger system

46. W. Smith, U. Wisconsin, Tracking Trigger Task Force Trigger Challenges & Opportunities - 46 CMS Level-1 Trigger  5x10 34 Occupancy Degraded performance of algorithms Electrons: reduced rejection at fixed efficiency from isolation Muons: increased background rates from accidental coincidences Larger event size to be read out New Tracker: higher channel count & occupancy  large factor Reduces the max level-1 rate for fixed bandwidth readout. Trigger Rates Try to hold max L1 rate at 100 kHz by increasing readout bandwidth Avoid rebuilding front end electronics/readouts where possible Limits:  readout time  (< 10 µs) and data size (total now 1 MB) Use buffers for increased latency for processing, not post-L1A May need to increase L1 rate even with all improvements Greater burden on DAQ Implies raising E T thresholds on electrons, photons, muons, jets and use of multi-object triggers, unless we have new information  Tracker at L1 Need to compensate for larger interaction rate & degradation in algorithm performance due to occupancy

47. W. Smith, U. Wisconsin, Tracking Trigger Task Force Trigger Challenges & Opportunities - 47 Track Trigger Architecture “push” path: L1 tracking trigger data combined with calorimeter & muon trigger data regionally with finer granularity than presently employed. After regional correlation stage, physics objects made from tracking, calorimeter & muon regional trigger data transmitted to Global Trigger. “pull” path: L1 calorimeter & muon triggers produce a “Level-0” or L0 “pre-trigger” after latency of present L1 trigger, with request for tracking information. Occurs at a rate of about 1 MHz. Request only goes to regions of tracker where candidate was found. This reduces the data transmitted from the tracker to L1 trigger logic by 40 (40 MHz to 1 MHz) times the probability of a tracker region to be found with candidates, which could be less than 10%. Tracker then sends out information for these regions only & this data would be combined in L1 correlation logic, resulting in a L1A combining tracking, muon and calorimeter information. Only on-detector tracking trigger logic in a specific tracker region would see a L0 signal. “afterburner”path: L1 Track trigger info, along with rest of information provided to L1 is used at very first stage of HLT processing. Provides track information to the HLT algorithms very quickly without having to unpack and process large volume of tracker information through CPU-intensive algorithms. This helps limit the need for massive additional processor power in the HLT computer farm.