1 / 43

CMS Global Trigger Control and Monitoring

CMS Global Trigger Control and Monitoring. Alexander Winkler Anton Taurok Barbara Neuherz Bernhard Arnold Christian Hartl Claudia-Elisabeth Wulz Herbert Bergauer Herbert Rohringer Ivan Mikulec Josef Strauss Kurt Kastner Manfred Jeitler Markus Eichberger Michael Padrta Philipp Glaser

craigi
Download Presentation

CMS Global Trigger Control and Monitoring

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. CMS Global TriggerControl and Monitoring Alexander Winkler Anton Taurok Barbara Neuherz Bernhard Arnold Christian Hartl Claudia-Elisabeth Wulz Herbert Bergauer Herbert Rohringer Ivan Mikulec Josef Strauss Kurt Kastner Manfred Jeitler Markus Eichberger Michael Padrta Philipp Glaser Philipp Wagner Thomas Schreiner Thomas Themel Vasile Mihai Ghete

  2. Outline • Global Trigger (GT) in the Context of CMS • GT Software Environment & Architecture • GT Database • GT Configuration • GT Monitoring • GT Online Operation

  3. Outline : Next: • Global Trigger (GT) in the Context of CMS • GT Software Environment & Architecture • GT Database • GT Configuration • GT Monitoring • GT Online Operation

  4. CMS @ LHC:High Luminosity : Need Event Filtering recapitulation • CMS designed for high luminosity 1034 cm-1s-1 • proton bunches collide every 25 ns • bunches contain ~1015 protons • collision energy √s = 2 x 7 TeV • need to discern • huge background • small fraction ofphysics of interest

  5. CMS @ LHC:Two Step Filter: L1 and HLT recapitulation • Level 1 Trigger • hardware (FPGAs / ASICs) • pipelined, 40 MHz • reduce event ratefrom ~1GHz to 100 kHz • Higher Level Trigger • software (computer farm) • reduce event ratefrom 100 kHz to 100 Hz

  6. GTL Global Trigger Logic FDL Final Decision Logic CMS Global Trigger:Final Level 1 Filter Logic recapitulation • menu of trigger algorithms • parallel calculation of >100 algorithms • complex combinations of simple conditions • based on CMS trigger objects • muons (momentum + coord.) • electrons and jets (energy + coord.) • energy sums and missing energy • only selected algorithms contribute • trigger candidate = logic OR

  7. TCS Trigger Control System GTFE Global Trigger Front End CMS Global Trigger:Trigger Decision Distribution recapitulation • Does every trigger candidate pass? No… • Trigger Control System decides: • every beam crossing (40 MHz) • candidate triggers too close? • any CMS system not ready? • After a Level 1 Accept? • all systems send data to DAQ (data acquisition) • Global Trigger also sends: • muon & calorimeter data; decision info DEAD-TIME

  8. Outline: Next: • Global Trigger (GT) in the Context of CMS • GT Software Environment & Architecture • GT Database • GT Configuration • GT Monitoring • GT Online Operation

  9. ? OK Global Trigger Online Software:Main Tasks: Configuration & Monitoring architecture • Why "online"? • it's for data taking • hardware configuration • put hardware chips into well defined state • e.g. trigger menu parameters • configuration data from CMS database • hardware monitoring • system parameters (e.g. detector input status) • physics parameters (trigger rates & deadtime)

  10. Global Trigger Online Software:GT Cell (Trigger Supervisor Application) architecture • GT Cell is a web application • C++ web service (XDAQ = CMS standard) • node in L1 "Trigger Supervisor" application tree • GT Cell is running as a Linux service 24/7 … on a machine in "service cavern" (CMS network) • PCI link to hardware (CAEN VME interface) • configuration & monitoring service • netw. communication with other L1 applications • netw. access to CMS database

  11. Global Trigger Online Software:GT Cell in Distributed Control System architecture Detector Applications Tracker, HCAL, ECAL, DT, RPC, CSC... CMSRun Control Data Acquisition, Filtering, Monitoring Applications DAQ, DQM, HLT… Detector Level 1 Trigger Applications Trigger Hardware Clock & Signal Distribution (TTC) Global Trigger Global Muon Trigger Cathode Strip Chamber Track Finder Global TriggerGlobal Muon Trigger… L1 Trigger Function Manager Central Trigger Cell Drift Tube Track Finder Resistive Plate Chamber Trigger Global Calorimeter Trigger Regional Calorimeter Trigger

  12. Global Trigger Online Software:GT/GMT Software Architecture architecture T. Nöbauer I. Mikulec M. Magrans Ph. Wagner G. Kasieczka Ch. Hartl Th. Themel B. Arnold H. Sakulin B. Neuherz J. Strauss B. Arnold M. Jeitler Ph. Glaser A. Winkler Ch. Hartl B. Arnold Th. Themel B. Arnold Ph. Wagner Trigger Menu Cell GT/GMT Test Cell GT Cell GMT Cell GT/GMT TestApplications Trigger Supervisor Framework commands, operations, control panels database access, cell communication GT Libraries access toGT module functions XDAQ Framework lightweight C++ web applications generic access to hardware and database inter-application network messaging CMS Database Scientific Linux CERN operating system used by CMS CMS Private Computer Network

  13. Outline: Next: • Global Trigger (GT) in the Context of CMS • GT Software Environment & Architecture • GT Database • GT Configuration • GT Monitoring • GT Online Operation

  14. Global Trigger Database:Bookkeeping for Hardware Setups database complete hardware setups stored in database this allows for: • deterministic hardware configuration: • full Level 1 trigger configuration defined in advance • bookkeeping: • which setup used in which CMS run? • synchronisation of online and offline software: • emulation software setup must match hardware setup • debugging: • reproduce hardware conditions to debug problems

  15. Global Trigger Database:Hardware Setup: What must be stored? database • Trigger Logic parameters • selection of trigger algorithms from menu • which algorithms allowed to cause trigger? • physics parameters of trigger conditions • e.g. energy or momentum thresholds • down-scaling of trigger algorithms • consider, say, every 100th trigger candidate only • Hardware Timing • alignment of trigger inputs • readout logic delays This is a glimpse. The completehardware setup must be defined in the database.

  16. Global Trigger Database:Hardware Setup Data Organization database • structured information for all GT modules • decoded items (human-interpretable names) GT key TSC TSP L1T Menu Key

  17. Global Trigger Database:Frequently Changing: "Run Settings" database • fine-tuned setup: modifiable ad hoc on shift • "GT Run Settings" Database

  18. Global Trigger Database:"GT Run Settings" Database Update database • GT Run Settings GUI: • update "current Run Settings" in the database • i.e. those which are to be used in the next run 1 trigger sources mix 2a selection of algorithms from Level 1 Menu 2b down-scaling of algorithm pre-decisions 2c 3

  19. Global Trigger Database:"GT Run Settings": Selection of Algos database

  20. Global Trigger Database: Level 1 Trigger Menu Versions database • trigger menu implemented in firmware • Global Trigger Logic condition chips: • main characteristics: firmware version • threshold definition: register content (set by software) • Level 1 trigger menu versions bookkeeping • crucial to analysis of CMS data • strict versioning enforced in database • difference between two versions? • only implementation differs? e.g. trigger objects rescaling • versions physically different?new firmware?threshold change?

  21. Global Trigger Database:Level 1 Trigger Menu Data Organization database L1T Menu DBpopulated by Trigger Menu Editor

  22. Outline: Next: • Global Trigger (GT) in the Context of CMS • GT Software Environment & Architecture • GT Database • GT Configuration • GT Monitoring • GT Online Operation

  23. halted configure configured enable stop enabled stop' suspend enable' suspended Global Trigger Configuration:Configure and Start the Run… configuration data taking with cosmic muons (Global Runs)… CMS systems coordinated by Run Control: • configure • GT: hardware setup • GT: periodic orbit signal (BC0)to CMS systems • enable • GT: start signal to CMS systems • GT: trigger sources ON(physics, random, calibration) • stop • GT: trigger sources OFF • GT: stop signal to CMS systems

  24. Global Trigger Configuration:What Data to Send after Level 1 Accept? configuration • Level 1 Accept to the detector: • GT sends data to Data Acquisition: • input data from Global Muon and Calorimeter Trigger • decision word: which algorithms caused the L1A? • crucial for Level 1 "seeding" of Higher Level Trigger • Global Trigger readout configuration • what data is sent, what not? • send how big a window around the time of L1A? • 3·25 ns or 5·25 ns

  25. Global Trigger Configuration:No Changes While Running configuration physics data require stable trigger setup • no trigger configuration changes while running • exception 1:pre-scaling of trigger algorithms: • luminosity drops while running trigger rates decreasedecrease pre-scaling (in steps) to compensate • using pre-defined pre-scaling sets (set index 0, 1, 2, …) • no information lost: event data contain set index • exception 2:random trigger rate (if "randoms on") • no information lost: event data show dedicated ID

  26. cold-reset halted configure repartition configured stop enable change prescaling enabled stop' enable' suspend suspended Global Trigger Configuration:Operation Transitions in More Detail configuration additional transitions: (launched by Run Control) • cold-reset(halted-halted) • reload firmware into chipsfrom PROMs (necessary when LHC clock changes) • repartition(configured-configured) • define which detector partitions(there are 32) should be serviced by the Trigger Control system • change prescaling(enabled-enabled) • to compensate for decreasing luminosity

  27. cold-reset cold-reset halted halted 0 7 configure configure repartition repartition configured configured enable enable stop stop change prescaling change prescaling enabled enabled stop' stop' enable' enable' suspend suspend suspended suspended Global Trigger Configuration:Service Eight Detector Partition Groups configuration Up to eight runs can be serviced by GT in parallel/independently. … e.g.:calorimeter systems(ECAL, HCAL,RCT, GCT) e.g.:muon systems(DT, DTTF,CSC, CSCTF)

  28. Global Trigger Configuration:From Run Control to Global Trigger Crate configuration • Communication Flow: • Run Control defines:which detector parts are read out? • Global Trigger reacts in repartition transition • assign detector partition to due GT partition (0…7) • enable detector partition to receive triggers and signals • listen and react to detector partition's status information Level1 Trigger Online Software CMS Run Control Level 1 TriggerFunction Manager Central Cell Global Trigger Cell Global Trigger Hardware Run Control SoftwareFramework (Java) Trigger Supervisor / XDAQ Framework (C++)

  29. Global Trigger Configuration:HardwareFunction C++ Class configuration • translation database – hardware: • class HardwareFunction defines mapping: • in central place (documentation!) • "automatic" configuration • database field names are HardwareFunction names • configure by call to HardwareFunction(itemName)::set(value) database field: TCS.p0.PHYSICS_TRIGGER_EN (true / false) Trigger Control System, partition 0:physics triggers enabled? hardware register bits: TCS.PTC0_CMD_REG, bit 12 (1 or 0) register bit for disabling of physics triggers for partition 0. C++ classHardwareFunction

  30. Global Trigger Configuration:Database & Hardware Configuration Editor configuration • To browse through a given Global Trigger setup in the CMS database • what's in the GT key? • To compare with the current hardware configuration • change hardware settings ad hoc for testing • online documentation of database items(and correspondence to hardware) • To create a new Global Trigger setup • make new GT key (modify existing one)

  31. Global Trigger Configuration:Database & Hardware Configuration Editor configuration • Step 1: Select GT setup from database • or key from any other Level 1 Trigger subsystem works for all Level 1Trigger subsystems 1 list of available GT setup keys 2 3 click to enter navigator

  32. Global Trigger Configuration:Database & Hardware Configuration Editor configuration • Step 2: Navigate through GT setup in DB • modify configuration (in editor, not yet in database) 1 4 make editable,enter name click to store modifications in database (enter preview) 2 tree navigation online documention of database items: "what hardware register bits does it correspond to?" sub-node linknavigation 3 orange:editor item modified red:hardware value differs modify item

  33. Global Trigger Configuration:Database & Hardware Configuration Editor configuration • Step 3: Preview & insert new setup ("key") in database 2 add setup in database 1 double-check: is that what you want to add in the database?

  34. Outline: Next: • Global Trigger (GT) in the Context of CMS • GT Software Environment & Architecture • GT Database • GT Configuration • GT Monitoring • GT Online Operation

  35. Global Trigger Monitoring:Hardware, Trigger, Configuration, Inputs monitoring • what's the trigger setup? • current trigger sources and selected algorithms • what's the configuration status? • configured? which key? running? • how is the trigger performance? • trigger rates? which algorithms contribute most? • deadtime? what are the reasons? • what's the detector input and GT's status? • status of GT boards and readout? detector inputs?

  36. Global Trigger Monitoring:Monitoring Data Flow monitoring CMS Level 1 Trigger GT Cell Page L1 Page WBM Page L1 Page server Web Based Monitoring (web server) Linux File System Global Trigger GT Cell service Trigger Function Manager Monitoring Collector CMS Database "SCAL" Application CMS private network

  37. Global Trigger Monitoring:Output Trigger Rate History monitoring • GT output trigger rate (from event number) • rate = Δ(number of L1As) / Δt • live update every 5 s (L1 Page) high rate test: 90 kHz(mainly artificial"random" triggers) Cosmics Run @ Zero Tesla (CRUZET)

  38. Global Trigger Monitoring:Trigger Rates and Deadtime monitoring GT CellTrigger MonitorPanel time since start of run (in luminosity segments, ~93 s) runnumber instantaneoustrigger (L1A) rate generated triggers (L1As) rates of individual trigger candidates rate history of generated trigger candidatesrate history of lost trigger candidates rate history of physics L1Asrate history of random L1Asrate history of test L1Asrate history of calibration L1As history of generated deadtime (in %)- due to trigger rules- due to calibration cycles- due to detector/DAQ backpressure luminosity segment (x 93 s): 164 163 162 …

  39. Global Trigger Monitoring:Detector Input Status and GT Status monitoring GT CellDetector & GTStatus MonitorPanel Monitoring Panel to spot quickly problems in GT or detectorwhile taking data. 2 CSC partitions: WARNING ECAL partitions: BUSY 1 HCAL partition: READY2 HCAL partitions: OUT OF SYNCH 2 TRK partitions: ERROR RPC partition:not in readout (not yellow)status is ignored GT boards and readout: READY Combined Input Status to TCS = ERROR(here: because of ERROR in CSC system) Output Status of TCS partition 0 = IDLE(partition 0 not running)

  40. Global Trigger Monitoring:Trigger Sources, Key, Enabled Algos monitoring GT CellConfiguration Panel GT (TCS partition 0) is configured physics triggers enabled (no random or calibration triggers) "algorithms" L1_SingleJet6 and L1_SingleJet10 are enabled(will forward trigger candidates to the Trigger Control System)

  41. Outline: Next: • Global Trigger (GT) in the Context of CMS • GT Software Environment & Architecture • GT Database • GT Configuration • GT Monitoring • GT Online Operation

  42. Global Trigger Online Operation:Trigger Shifter Tasks operation • before each CMS run: • GT basic configuration defined by GT key • as set in Level 1 Trigger Key GUI • GT ad hoc settings defined by GT Run Settings • as set in GT Run Settings GUI • while CMS is taking data: • monitoring of rates, deadtime, detector status • Resync or HardReset in case of detector problem • change of random trigger rate (high rate tests) • change of algorithm decision prescaling

  43. CMS Global TriggerControl and Monitoring Thank you! more: Global Trigger official web page: http://wwwhephy.oeaw.ac.at/p3w/electronic1/GlobalTrigger/GlobalTriggerCrate.htm collection of wiki articles: https://twiki.cern.ch/twiki/bin/view/CMS/GlobalTrigger

More Related