1 / 34

Trigger at CMS

Trigger at CMS. Warsaw 2 November 2011. O verview. Trigger architecture L1 Trigger High Level Trigger Muon trigger performance . CMS at LHC. CMS Detector. *. *Actually 3.8 T. http://press.web.cern.ch/press/PressReleases/Releases2011/PR22.11E.html. Luminosity at CMS in 2011.

didier
Download Presentation

Trigger at CMS

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. Trigger at CMS Warsaw 2 November 2011

  2. Overview • Trigger architecture • L1 Trigger • High Level Trigger • Muon trigger performance Karol Buńkowski, CERN, UW,

  3. CMS at LHC The CMS Level-1 Trigger @ SPG-ÖPG 2011, Lausanne

  4. CMS Detector * *Actually 3.8 T

  5. http://press.web.cern.ch/press/PressReleases/Releases2011/PR22.11E.htmlhttp://press.web.cern.ch/press/PressReleases/Releases2011/PR22.11E.html Karol Buńkowski, CERN, UW,

  6. Luminosity at CMS in 2011 • 2011: √s = 7 TeV • Peak Instantaneous Luminosity: 3.69 ×1033 cm-2 s-1 • 1380 bunches/beam (1331 colliding at CMS)minimum collisions spacing - 50 ns • Primary vertices – up to ~20 (mean ~10) Karol Buńkowski, CERN, UW,

  7. Why trigger is crucial at LHC? 40 millions of bunch crossing/s: ~20 p-p collisions each crossing and hundreds of secondary particles ~1 MB of compressed data/BX = 4  1013 Bytes (40 000 GB) / s Not possible to record! p-p collisions The background - Standard Model physic - must be rejected in the real time (without recording to the massive storage) The signal – Higgs or “new physic” particles - must be kept with efficiency close to 100% New particles are heavy  decays to the energetic objects which allow to distinguish them from the background events The rate of the selected events cannot exceed the data acquisition bandwidth Karol Buńkowski, UW

  8. Trigger system - principles The Trigger decides in the real time whether each event should be recorded to the massive storage (because is potentially interesting) or should be rejected (because most probably is background) • The Trigger is the first step of the physic analysis of the detector data: • Cuts (filters) which should allow to distinguish the signal (“new physic”) from the background (Standard Model) are applied. • But opposite to the offline analysis the events (class of events) rejected by the Trigger are definitely lost.If the events of “new physic” are not accepted by the Trigger we might never see them… • We don’t know exactly what we are looking for, therefore the Trigger must be universal: should accept the possibly wide variety of events (but keeping the rate within the limit) Karol Buńkowski, CERN, UW,

  9. The Trigger and DAtaAqusition system at CMS Level 1 Trigger • Dedicated electronics (ASICs, FPGAs) @ 40 MHz, only logic functions • Analyses every event (bunch crossing, BX) •  pipeline processing; latency 3.2 s, including ~2 s for data transmission between the detector and counting room, dead time freeoperation Output≤100 kHz Detector Coarsedata Readout buffers 128 events= 3.2 s keepreject DAQ: readouts the data for the selected events, the events are fragmented Event Builder - switching network. Gathers the data from one event into one HLT computer High Level Trigger (HLT) • Computer Farm: 1008 nodes, 9216 cores, 16 TB memory runs the software events selection algorithms • A few hundreds of Hz recorded on the magnetic tapes Karol Buńkowski, UW

  10. Level 1 Trigger architecture Calorimeter Trigger Muon Trigger DAQ RPC hits CSC hits DT hits ECAL Trigger Primitives HCAL Trigger Primitives Trigger subsystems: identify, measure and sort the trigger objects Link system Segment finder Segment finder RegionalCalorimeterTrigger Track finder Pattern Comparator Track finder 40 MHz pipeline 4+4 m 4 m 4 m MIP+ISO bits GlobalCalorimeterTrigger Global Muon Trigger muons e/, J, ET, HT, ETmiss Global Trigger Status L1A (trigger) TTC system TTS system 32 partitions Detectors Frontend Karol Buńkowski, UW

  11. L1 Trigger Custom Hardware RPC PaC (Warsaw) • Hundreds of boards • Thousands of: • ASICs • FPGAs • Copper Cables • Optical Fibers • (Wo)man hours CSCTF (Florida) RCT (Wisc.) DTTF (Vienna) GCT (Imperial) Global Muon Trigger & Global Trigger (Vienna)

  12. L1Global Trigger conditions and algorithms GT input - Trigger Objects: • From Global Muon Trigger • 4 best muons (with pT, position, sign, and quality information) • From Global Calorimeter Trigger - energy and coordinates of: • 4 forward and 4 central jets, • 4 -jets, • 4 isolated and 4 non-isolated e/, • total ET, missing ET, • HT (the scalar sum of the transverse energies of the jets above a threshold ), • threshold-dependent jet multiplicities • 64 technical trigger signals (from LHC beam counters, CMS beam scintillators, CMS subsystems) The GT first calculates the “conditions” : • For each quadruplet of “particlelike” (muons and jets) channels checks if: • pT or ET above threshold • quality above threshold • η or φ within window • absolute difference in η or/and φ between two particles is within a required range • Cuts on the total ET, missing ET and HT are applied Several conditions are then combined by a simple combinatorial logic (AND-OR-NOT) to form algorithms (128 are possible) The algorithms are combined by a final OR function to generate a ‘L1_Accept’ - signal that starts the Data Acquisition Karol Buńkowski, CERN, UW,

  13. L1 Trigger “menu” – example algorithms • Muon triggers: • L1_SingleMu14_Eta2p1 • pT >= 14 GeV • || < 2.1 • GMT quality > 3 (low quality unconfirmed CSC candidates are rejected) • L1_DoubleMu3: pT >= 3 GeV • Electron/gamma triggers: • L1_SingleEG15: ET>=15Gev • L1_DoubleEG_12_5: DoubleIsoEG_12GeV_5GeV OR DoubleNoIsoEG_12GeV_5GeV OR(SingleIsoEG_12GeV AND SingleNoIsoEG_5GeV) OR (SingleIsoEG_5GeV AND SingleNoIsoEG_12GeV) • Jet triggers • L1_DoubleJet44_Central:DoubleCenJet_44GeV OR DoubleTauJet_44GeV OR (SingleCenJet_44GeV AND SingleTauJet_44GeV) • Cross-triggers • L1_Mu12_EG5SingleMu_12GeV AND ( SingleIsoEG_5GeV OR SingleNoIsoEG_5GeV ) Usually new menu = new GT firmware (the thresholds are programmable registers, but conditions must be rebuilt in the firmware) Karol Buńkowski, CERN, UW,

  14. HLT system • CMS online filter farm(hardware) • 1008 nodes (system boards – computers):2 x 4 cores or 2 x 6 cores (2.66 GHz), 16 or 24 GB RAM • 9216 cores in total Each machine runs • The HLT software: • 1 master process • input/output • watchdog • re-spawns event processors • 7 event processes - HLT reconstruction and selection: • read the input data • run all the trigger algorithms – “paths” (443 in the latest proton menu) • take the final accept/reject decision • stream the data to the Storage Managers For processing one event each process has available an average up to 90 ms (For comparison, offline reconstruction takes ~5 s per event!) Karol Buńkowski, CERN, UW,

  15. HLT paths and menu The HLT decision is taken as the OR of many independent triggers or “paths” (>400). Each path runs independently from the others (in parallel in the same process - the software guarantees that the same reconstruction block is not run twice) • Most of the paths requires one selected Level 1 algorithm (as a seed) to start • Then step-by-step reconstruction is performed Reconstruction is seeded by the Level 1 object • First stage: only calorimeters and muon system information (fast code) • Second stage: reconstruction of full tracks in the tracker (slowest code) • Intermediate stage: use of partial tracker information try to reject the event as soon as possible The even is taken, if at least one path passed Karol Buńkowski, CERN, UW,

  16. Karol Buńkowski, CERN, UW,

  17. Data streams and datasets The HLT decision is used to steer splitting events into streams and datasets • online: • Stream A: bulk data (sample for physics analysis) • Alignment & Calibration (AlCa) streams • express (prompt feedback & calibrations) • offline: split the streams into 20 Primary Datasets:Jet, HT, MET, BTag, MultiJet, SingleMu, DoubleMu, MuOnia, MuEG, MuHad, SingleElectron, DoubleElectron, Photon, ElectronHad, PhotonHad, Tau, TauPlusX, Commissioning, Cosmics, MinBias Karol Buńkowski, CERN, UW,

  18. Prescaled triggers It is good idea to save some fraction of events which are not accepted by the standard “physic” cuts: • no cuts at all, except requirements for any collisions – minimum bias events • events triggered with lower thresholds These triggers are pre-scaled, i.e. only every n event with given trigger path fired is accepted. n is prescale factor. These triggers are utilized for: • fake rate measurements • efficiency measurements • trigger rate monitoring • trigger debugging/development • Collecting special data for detector calibration and performance evaluation Main types: • L1 pass-through's • L2 pass-through's • L3 low pT paths • Physics triggers with looser ID criteria • Physics triggers with looser isolation or without isolation As the luminosity was increasing, the trigger thresholds were increased as well. The lower threshold triggers were kept, however they were prescaled Karol Buńkowski, CERN, UW,

  19. Dynamic prescales The beam intensity decreases during a fill  the luminosity (number of interactions) decreases the rate of the events accepted by the Trigger decreases  the available bandwidth of the data acquisition is not used. Therefore the prescales (both at L1 and HLT) are decreased to keep approximately constant trigger rate. Karol Buńkowski, CERN, UW,

  20. How to cope with prescales? • If in a given analysis the events taken with the prescaled triggers are used, the prescales must be included in calculation of the cross-section (or rate) of the process under consideration: • The simplest approach is to take events triggered by only one trigger (HLT) path and weight each event with the prescale factor that was applied in given lumisection*. The prescales factors for each lumisection (as well as the luminosity) are available in the CMS database • If more than one HLT paths needs to be taken, the overlap of the path must be included *lumisection = 23.14 s Karol Buńkowski, CERN, UW,

  21. Trigger efficiency measurement(watch out for bias…) • How to find the denominator (it must include the events NOT triggered by given path)? In case of the L1 efficiency the additional problem is the filtering applied by the HLT – bias Possible approaches: • Take the events in which the required object(s) were reconstructed from the minimum bias dataset – the simplest approach, but very low statistic, especially for the more energetic objects • Take the events triggered by other paths not correlated with the investigated path, e.g. for calculation of the muon trigger efficiency take the events triggered by jet triggers, check if the muon trigger fired for the events with the reconstructed muons (might be biased), • Data driven methods (check for which efficiency the Monte Carlo fits best to the real data), • Use tag-and-probe method # events with trigger path fired Trigger path efficiency = # all events with the object(s) required by the trigger Karol Buńkowski, CERN, UW,

  22. Tag and probe method Use the Z or j/psi mass resonance to select lepton (electron or muon) pairs: • Tag: lepton passing very tight selectionwith very low fake rate (<<1%) • Probe: lepton passing softer selectionand pairing with Tag object in a waythat the invariant mass of tag and probe combination is consistent with the Z (j/psi) resonance • Efficiency = Npass/Nall Npass→ number of probes passing the selection criteria (e.g. muon or electron trigger fired) Nall→ total number of probes counted using the resonance Karol Buńkowski, CERN, UW,

  23. Muon trigger performance Karol Buńkowski, CERN, UW,

  24. Muon trigger objects L1 Muon Trigger3 muon detectors to |eta|<2.4 • Drift Tubes (barrel) and Cathode Strip Chambers (endcaps) • track segmentidentification • Track Finder • Resistive Plate Chambers • Pattern Matching • 4 candidates per subsystem toGlobal MuonTriggermergers, removes duplicates and sorts candidates, 4 top candidates to Global Trigger HLT MuonTrigger Karol Buńkowski, CERN, UW,

  25. Muon triggers thresholds ad rates the latest proton menu Lowest pTunprescaled triggers, rates at luminosity ~3e33cm-2 s-1 • L1 • L1_SingleMu14_eta2p1, rate ~6 kHz • L1_DoubleMu3p5, rate ~5 kHz • HLT • HLT_Mu40 (single), rate ~8.5 Hz • HLT_IsoMu24 (single), rate ~13 Hz • HLT_Mu13_Mu8 (double), rate ~5Hz • HLT_DoubleMu5_IsoMu5, rate ~0.1 Hz Very high cut on the single muon. High selection efficiency of (for example) W bosons require a muonthreshold around 20 GeV, and therefore cannot be achieved with the single muon trigger alone. Double muon and various cross triggers are required. Double muon trigger efficiency is about 90% Karol Buńkowski, CERN, UW,

  26. L1 Muon trigger efficiency CSC Track Finder efficiency Tag and probe, Z mass, |eta| < 2.4 Karol Buńkowski, CERN, UW,

  27. High Level Trigger Efficiency forMuon 30 GeV • Path HLT_Mu30 No isolation requirements on trigger • X-axis is offline muon PT • Efficiency is measured using the tag and probe technique with events selected offline with two muons forming a Z➞μμ candidate • Inefficiencies result mainly from L1 muon requirements • HLT efficiency in plateau is 95% in barrel and 90% in endcap • HLT / L1 efficiency is 99% in both MC and data Barrel Endcaps

  28. Trigger on HSCPs on L1 • Heavy Stable Charged Particles (HSCPs) take as much as 2 BX to exit the detector • Look for late signal in muontriggers • But preBPTX veto (the beam pick-up signals – technical trigger) during 50 ns bunch spacing vetoes these! • RPC Trigger can extend detector signal to 2 BX • Reduce RPC delay into GMT by 1 BX • preBPTX will veto early in-time muons • In-time muons still captured with collision BX • HSCPs aligned with collision BX • Create special HLT path to keep slow particles (the BXid will be +1 wrt to Tracker, for example). • HSCPs Triggering! HSCP In-time muon Extended hits Chamber hits extended hits Chamber hits layer 6 layer 6 layer 5 layer 5 layer 4 layer 4 layer 3 layer 3 layer 2 layer 2 BX BX layer 1 layer 1 Muon candidate Muon candidate BPTX BPTX Karol Buńkowski, CERN, UW,

  29. Bibliography • Andrea Bocci (CERN), The CMS High Level Trigger: operations and data taking experience, Parallel given at CHEP2010: International Conference on Computing in High Energy and Nuclear Physics 2010, 18-22 Oct 2010, Taipei (Taiwan) • Malgorzata Kazana (Soltan Inst. for Nucl. Studies), CMS trigger and data taking in 2010, Invited given at Epiphany 2011: Cracow Epiphany Conference on the First Year of the LHC, 10-12 Jan 2011, Institute of Nuclear Physics PAN , Kraków (Poland), • Joao Varela, Triggers for physics at instantaneous luminosity 1E33 in the CMS experiment, Invited given at RDMS CMS Conference: 15th Annual RDMS CMS Collaboration Conference, 22-28 May 2011, Kharkov, • Pamela Renee Klabbers (Univ. of Wisconsin), Operation and Performance of the CMS Level-1 Trigger during 7 TeV Collisions, Contributed given at TIPP 2011: Technology and Instrumentation in Particle Physics 2011, 9-14 Jun 2011, Chicago, IL (United States), • Christian Hartl (CERN), The CMS Level-1 Trigger, Contributed given at SPS-ÖPG11: Joint Annual Meeting of the Swiss Physical Society and the Austrian Physical Society, 15-17 Jun 2011, EPFL, Lausanne, Vaud (Switzerland), Karol Buńkowski, CERN, UW,

  30. Backup Karol Buńkowski, CERN, UW,

  31. e/g and Jet Algorithms 4x4 Tower sums from RCT to GCT Jet or t ET • 12x12 trig. tower ET sliding in 4x4 steps w/central 4x4 ET > others t: isolated narrow energy deposits • Energy spread outside t veto pattern sets veto • Jet  t if all 9 4x4 region t vetoes off GCT uses tower sums for ET,MET jets for HT, MHT Electron (Hit Tower + Max) • 2-tower ET + Hit tower H/E • Hit tower 2x5-crystal strips >90% of ET in 5x5 (Fine Grain) Isolated Electron (3x3 Tower) • Quiet neighbors: all towers pass Fine Grain & H/E • One “L” of 5 EM ET < Thr.

  32. Integratedmuonratesat generator levelfromdifferentsources. High luminosity L = 1034 cm-2s-1. Limited to || < 2.1 Karol Buńkowski, CERN, UW,

  33. For any considered “new physic” channel the Trigger configuration (L1 and HLT) must be found which: • Will be sufficiently efficient in selecting the interesting events, • The rate will not be grater than bandwidth given to you, • Is possible to implement in the L1 (only simple cuts and logic functions are possible) and HLT (the time needed to perform the algorithm is within the limit). Karol Buńkowski, CERN, UW,

More Related