Information for Trigger Shifter

* This is the list of actions which you need to perform as Triger Online Shifter TriggerShiftHLTGuide *

* This is for a shifter who wants to know a little bit more with couple of nice histograms TriggerShiftHLTExtendedInformation *

General Introduction

The online HLT DQM goal is to monitor all HLT filtering steps during data taking directly at P5. The baseline is that the DQM code runs off the Storage Manager (SM) unless there is a good reason to do otherwise (in which case is important to understand the algorithm performances). In the new HLT data model what is persistet is:

  • triggerTriggerEventWithRefs but only for a fraction of (accepted) events (for expert debugging, monitoring together with the original physics collections).
  • for all events, triggerTriggerEvent which packs up the L3 object collections as "4-momentum vector plus physics id" and records flags for those L3 objects actually passing the L3 filter on a path.

Summary of HLT Monitoring Information

In the following table POGS and PAGS contacts should write information about their HLT monitoring plan. In short the relevant information that is needed are the "Monitorables" (what information they want to monitor, ex Et distribution of L2 electrons), what trigger path they intend to use for this monitoring (ex. prescaled path with no isolation) and the rate of events that they need (this comes from the fact that the available rate out of the SM is about 10 Hz). For a full list of HLT path names look here.

Group Monitorable(s) Trigger Path Does path exist? Needed Rate Notes
egamma* number of events passing cut n SingleElectronRelaxed yes 0.3 Hz -
egamma* distribution of eta of candidates passing cut n random** yes 0.3 Hz -
egamma* distribution of et of candidates passing cut n HLT2ElectronZCounter yes all*** -
JetMET - HLT_L1Jet15 yes 2Hz inclusive JetMET -
JetMET - HLT_DiJetAve15 yes 2Hz inclusive JetMET -
JetMET - HLT_L1MET20 yes 2Hz inclusive JetMET -
JetMET - single photon No 2Hz inclusive JetMET Path to be developed, must have lower threshold than for egamma
Muon* Filters distributions**** HLT_L1MuOpen yes - New name from TSG (Tulika). Studies on rates are in progress (B. Bloom).
Muon* Filters distributions**** HLT_L2Mu9 yes - New name from TSG (Tulika). Studies on rates are in progress (B. Bloom).
Muon* Filters distributions**** HLT_Mu5 yes - New name from TSG (Tulika). Studies on rates are in progress (B. Bloom).
Tau HLT1FakeJetsTau_noL2MET_noL25 yes tau-dqm-proposal.pdf: Tau Group Monitoring Proposal
Tau HLT1FakeJetsTau_noL2MET_noL25_noL3 yes tau-dqm-proposal.pdf: Tau Group Monitoring Proposal
Tau HLT2FakeJetsTau_noL25 yes tau-dqm-proposal.pdf: Tau Group Monitoring Proposal
*code currently runs off TriggerEventWIthRefs ** random means they are happy with any triggers, not necessarily e-gamma * as many as possible; rate estimate at 2E32 is 0.0 ** Muons plan to add monitoring of muon reconstruction in the FF in addition to monitoring of filters off the SM. *****Objects: TriggerEvent AOD, hltFakeJetsSingleTauL1SeedFilter, hltL2FakeJetsSingleTauJets, hltL2FakeJetsSingleTauIsolationProducer, hltL2FakeJetsSingleTauIsolationSelectorLooseL2Isolation hltConeIsolationL3FakeJetsSingleTauNoL25, hltIsolatedL3FakeJetsSingleTauNoL25.

Online HLT DQM Histograms/Shifter Information

Tau HLT Online DQM

Egamma HLT Online DQM

Muon HLT Online DQM

Software instructions


DQM Packages


Sources implemented are:
  • PathTimerService: See documentation in SWGuideHLTTimingSummary
  • HLTMuonDQMSource : See documentation in SWGuideMuonHLTOnlineDQM
  • HLTMon(old source): Monitors candidates from both Electron filters and Muon filters. Distributions of the quantities (pt, eta, phi, isolated deposit maps) from Electron and Muon filters are collected in the HLTMonhltMonE and HLTMonhltMonMu subdirectories, respectively. Histogram naming follows the convention <filtername><quantity> (e.g. hltEMuL1MuonFilterphi). For more information, see SWGuideMuonSWGuideHLTDQM.

NOTE: These histograms are often empty for the following reasons:

  • Presently, the appropriate data products are not stored in the event when being sent to the HLT.
  • Most cosmic triggers do not fire L1 bits that feed HLT (so no HLT algorithms are run).

HLT DQM source example

An example of HLT DQM source based on the new HLT data model and accessing triggerTriggerEventWithRefs can be found here:


To run the example do the following (input file has very few events and can be found in /castor/cern.ch/user/l/lorenzo/HLTFromDigiRaw.root):

scramv1 project CMSSW CMSSW_2_0_0_pre1

cd CMSSW_2_0_0_pre1/src

project CMSSW

eval `scramv1 runtime -csh`

cvs co DQM/HLTEvF

cd DQM/HLTEvF/test/

cmsRun hlt_dqm_fromfile.cfg

This is just an example (taken from Matthias Mozer) and is far from being a complete DQM source. POGS and PAGS contacts are supposed to implement all the monitoring needed to understand the data.


Clients implemented are:
  • HLTMuonDQMClient : Muon HLT candidates parameters and resolution : plotting client.



Trigger Cross Section Monitor, of TXMon for short, is an online consumer monitor scalar information in the event stream. TXMon receives trigger rates and values by subscribing to the Storage Manager.


TXMon Client collects subscribed information from TXMon, tabulates the data, and generates root histograms containing the data.


TXMon Fitter imports a collection of TXMon Client's root files and statistically plots 'Trigger Cross Section' as a function of 'Average Instantaneous Luminosity'. Fitter is ready for use but will require some initial soft coding to be entirely compatible with Client's output file name format. When Client is released source files will be moved from the 'test' folder to the 'src' folder.

To run TXMon Fitter, follow these excerpts from the 'readme.txt' file; files are included in package to test current release stability.

1. To Download TXMon Fitter Package:

source /uscmst1/prod/sw/cms/cshrc uaf
scramv1 project CMSSW CMSSW_1_8_0
cd CMSSW_1_8_0/src/
eval `scramv1 runtime -csh`
project CMSSW
cvs co DQM/TrigXMonitorFitter
cd DQM/TrigXMonitorFitter/test/

2. To Setup Workspace:

source ./FitSetup.sh

3a. Example of how to run fitAllTXMonUsingRuns.pl normally:

./fitAllTXMonUsingRuns.pl -f runnumbers.txt

3.b Example of how to run fitSingleTXMonUsingRuns.pl normally:

 ./fitSingleTXMonUsingRuns.pl L1_CEM4_PT4_PS250 240250

-- LorenzoAgostino - 06 Feb 2008 -- MonicaVazquezAcosta - 13 Feb 2008 -- RichardRuiz - 28 Apr 2008 -- LorenzoAgostino - 23 Jun 2008 -- LorenzoAgostino - 24 Jun 2008 -- LorenzoAgostino - 03 Jul 2008

Responsible: JasonSlaunwhite

Edit | Attach | Watch | Print version | History: r25 < r24 < r23 < r22 < r21 | Backlinks | Raw View | WYSIWYG | More topic actions
Topic revision: r25 - 2011-05-30 - MonicaVazquezAcosta
    • Cern Search Icon Cern Search
    • TWiki Search Icon TWiki Search
    • Google Search Icon Google Search

    CMSPublic All webs login

This site is powered by the TWiki collaboration platform Powered by PerlCopyright & 2008-2019 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding TWiki? Send feedback