DQMOffline_Trigger_cff Namespace Reference

Variables
tuple	dqmEnvHLT = DQMServices.Components.DQMEnvironment_cfi.dqmEnv.clone()
tuple	dqmInfoHLTMon
tuple	hltFiltersDQM
tuple	OfflineHLTMonitoring
tuple	OfflineHLTMonitoringPA
tuple	offlineHLTSource
	old sequence, it should be dropped asa we are confident it is no longer used More...
tuple	offlineHLTSource4ExpressPD
	SEQUENCES TO BE RUN #### Express : not really needed HLTMonitor : special collections allow to monitor tracks, strip and pixel clusters, b-tagging discriminator, etc –> OfflineHLTMonitoring Physics PDs : monitoring vs offline collection (typically, turnON) More...
tuple	offlineHLTSource4HLTMonitorPD
	DQM step on HLTMonitor ADD here only sequences/modules which rely on HLT collections which are stored in the HLTMonitoring stream and are not available in the standard RAW format. More...
tuple	offlineHLTSource4physicsPD
	DQM step on physics PDs transient collections produced by the RECO step are allowed ;) More...
tuple	offlineHLTSource4relval
	DQM step on relval. More...
tuple	offlineHLTSource4specialPhysicsPD
	DQM step on special physics PDs (HI, FSQ and LowLumi, etc) transient collections produced by the RECO step are allowed ;) More...
tuple	offlineHLTSourceOnAOD
	on AOD (w/o the need of the RECO step on-the-fly) ADD here sequences/modules which rely ONLY on collections stored in the AOD format More...
tuple	offlineHLTSourceOnAODextra
	offline DQM to be run on AOD (w/o the need of the RECO step on-the-fly) only in the VALIDATION of the HLT menu based on data it is needed in order to have the DQM code in the release, w/o the issue of crashing the tier0 as the new modules in the sequence offlineHLTSourceOnAODextra are tested, these have to be migrated in the main offlineHLTSourceOnAOD sequence More...
tuple	offlineHLTSourceOnMiniAOD
	SEQUENCES TO BE RUN depending on the input DATAFORMAT on MiniAOD ADD here sequences/modules which rely ONLY on collections stored in the MiniAOD format. More...
tuple	offlineHLTSourceWithRECO
	w/ the RECO step on-the-fly (to be added to offlineHLTSourceOnAOD which should run anyhow) More...
tuple	offlineValidationHLTSource
tuple	offlineValidationHLTSourceOnAOD
	offline DQM to be run on AOD (w/o the need of the RECO step on-the-fly) in the VALIDATION of the HLT menu based on data it is needed in order to have the DQM code in the release, w/o the issue of crashing the tier0 as the new modules in the sequence offlineHLTSourceOnAODextra are tested these have to be migrated in the main offlineHLTSourceOnAOD sequence More...
tuple	triggerOfflineDQMSource
	sequence run (called by main DQM sequences in DQMOffline/Configuration/python/DQMOffline_cff.py) on all PDs, but HLTMonitor one More...

Variable Documentation

tuple DQMOffline_Trigger_cff.dqmEnvHLT = DQMServices.Components.DQMEnvironment_cfi.dqmEnv.clone()

Definition at line 99 of file DQMOffline_Trigger_cff.py.

tuple DQMOffline_Trigger_cff.dqmInfoHLTMon

Initial value:

= DQMEDAnalyzer('DQMEventInfo',
    subSystemFolder = cms.untracked.string('HLT')
)

Definition at line 103 of file DQMOffline_Trigger_cff.py.

tuple DQMOffline_Trigger_cff.hltFiltersDQM

Initial value:

= hltFiltersDQMonitor.clone(
  folderName = 'HLT/Filters',
  efficPlotNamePrefix = 'effic_',
  triggerResults = 'TriggerResults::HLT',
  triggerSummaryAOD = 'hltTriggerSummaryAOD::HLT',
  triggerSummaryRAW = 'hltTriggerSummaryRAW::HLT',
)

Definition at line 8 of file DQMOffline_Trigger_cff.py.

tuple DQMOffline_Trigger_cff.OfflineHLTMonitoring

Initial value:

= cms.Sequence(
    offlineHLTSource4HLTMonitorPD
)

Definition at line 199 of file DQMOffline_Trigger_cff.py.

tuple DQMOffline_Trigger_cff.OfflineHLTMonitoringPA

Initial value:

= cms.Sequence(
    dqmInfoHLTMon *
    trackingMonitorHLT *
    PAtrackingMonitorHLT  
)

Definition at line 204 of file DQMOffline_Trigger_cff.py.

tuple DQMOffline_Trigger_cff.offlineHLTSource

Initial value:

= cms.Sequence(
    offlineHLTSource4physicsPD
)

old sequence, it should be dropped asa we are confident it is no longer used

Definition at line 248 of file DQMOffline_Trigger_cff.py.

tuple DQMOffline_Trigger_cff.offlineHLTSource4ExpressPD

Initial value:

= cms.Sequence(
)

SEQUENCES TO BE RUN #### Express : not really needed HLTMonitor : special collections allow to monitor tracks, strip and pixel clusters, b-tagging discriminator, etc –> OfflineHLTMonitoring Physics PDs : monitoring vs offline collection (typically, turnON)

DQM step on Express

Definition at line 178 of file DQMOffline_Trigger_cff.py.

tuple DQMOffline_Trigger_cff.offlineHLTSource4HLTMonitorPD

Initial value:

= cms.Sequence(
    dqmInfoHLTMon *
    lumiMonitorHLTsequence *          # lumi
    sistripMonitorHLTsequence *       # strip
    sipixelMonitorHLTsequence *       # pixel
    BTVHLTOfflineSource *             # BTV
    bTagHLTTrackMonitoringSequence *  # BTV relative track efficeicies
    trackingMonitorHLT *              # tracking
    trackingMonitorHLTDisplacedJet*   # EXO : DisplacedJet Tracking 
    egmTrackingMonitorHLT *           # EGM tracking
    hltToOfflineTrackValidatorSequence *  # Relative Online to Offline performace
    vertexingMonitorHLT               # vertexing
)

DQM step on HLTMonitor ADD here only sequences/modules which rely on HLT collections which are stored in the HLTMonitoring stream and are not available in the standard RAW format.

Definition at line 184 of file DQMOffline_Trigger_cff.py.

tuple DQMOffline_Trigger_cff.offlineHLTSource4physicsPD

Initial value:

= cms.Sequence(
      offlineHLTSourceOnAOD
    * offlineHLTSourceWithRECO
)

DQM step on physics PDs transient collections produced by the RECO step are allowed ;)

Definition at line 212 of file DQMOffline_Trigger_cff.py.

tuple DQMOffline_Trigger_cff.offlineHLTSource4relval

Initial value:

= cms.Sequence(
      offlineHLTSourceOnAOD
    * offlineHLTSourceWithRECO
    * offlineHLTSource4HLTMonitorPD       ## special collections (tracking, strip, pixel, etc)
    * fsqHLTOfflineSourceSequence         ## FSQ
    * HILowLumiHLTOfflineSourceSequence   ## HI
    * offlineHLTSourceOnAODextra          ## EXTRA
)

DQM step on relval.

Definition at line 227 of file DQMOffline_Trigger_cff.py.

tuple DQMOffline_Trigger_cff.offlineHLTSource4specialPhysicsPD

Initial value:

= cms.Sequence(
      offlineHLTSourceOnAOD
    * offlineHLTSourceWithRECO
    * fsqHLTOfflineSourceSequence
    * HILowLumiHLTOfflineSourceSequence
)

DQM step on special physics PDs (HI, FSQ and LowLumi, etc) transient collections produced by the RECO step are allowed ;)

Definition at line 219 of file DQMOffline_Trigger_cff.py.

tuple DQMOffline_Trigger_cff.offlineHLTSourceOnAOD

Initial value:

= cms.Sequence(
      dqmEnvHLT
    * hltFiltersDQM
    * lumiMonitorHLTsequence
    * muonFullOfflineDQM
    * HLTTauDQMOffline
    * hltInclusiveVBFSource
    * higPhotonJetHLTOfflineSource # plots are filled, but I'm not sure who is really looking at them and what you can get from them ... good candidates to be moved in offlineHLTSourceOnAODextra
#    eventshapeDQMSequence * ## OBSOLETE !!!! (looks for HLT_HIQ2Top005_Centrality1030_v, HLT_HIQ2Bottom005_Centrality1030_v, etc)
#    HeavyIonUCCDQMSequence * ## OBSOLETE !!!! (looks for HLT_HIUCC100_v and HLT_HIUCC020_v)
#    hotlineDQMSequence * ## ORPHAN !!!!
    * egammaMonitorHLT 
    * exoticaMonitorHLT
    * susyMonitorHLT
    * b2gMonitorHLT
    * higgsMonitorHLT
    * smpMonitorHLT
    * topMonitorHLT
    * btagMonitorHLT 
    * bphMonitorHLT
    * hltObjectsMonitor # as online DQM, requested/suggested by TSG coordinators
    * jetmetMonitorHLT
)

on AOD (w/o the need of the RECO step on-the-fly) ADD here sequences/modules which rely ONLY on collections stored in the AOD format

Definition at line 115 of file DQMOffline_Trigger_cff.py.

tuple DQMOffline_Trigger_cff.offlineHLTSourceOnAODextra

Initial value:

= cms.Sequence(
### POG
      btvHLTDQMSourceExtra
    * egmHLTDQMSourceExtra # empty in 10_2_0
    * jmeHLTDQMSourceExtra 
    * muoHLTDQMSourceExtra # empty in 10_2_0
    * tauHLTDQMSourceExtra # empty in 10_2_0
    * trkHLTDQMSourceExtra # empty in 10_2_0
### PAG
    * b2gHLTDQMSourceExtra
    * bphHLTDQMSourceExtra # empty in 10_2_0
    * exoHLTDQMSourceExtra
    * higHLTDQMSourceExtra
    * smpHLTDQMSourceExtra # empty in 10_2_0
    * susHLTDQMSourceExtra
    * topHLTDQMSourceExtra
    * fsqHLTDQMSourceExtra # empty in 10_2_0
#    * hinHLTDQMSourceExtra
)

offline DQM to be run on AOD (w/o the need of the RECO step on-the-fly) only in the VALIDATION of the HLT menu based on data it is needed in order to have the DQM code in the release, w/o the issue of crashing the tier0 as the new modules in the sequence offlineHLTSourceOnAODextra are tested, these have to be migrated in the main offlineHLTSourceOnAOD sequence

Definition at line 152 of file DQMOffline_Trigger_cff.py.

tuple DQMOffline_Trigger_cff.offlineHLTSourceOnMiniAOD

Initial value:

= cms.Sequence(
)

SEQUENCES TO BE RUN depending on the input DATAFORMAT on MiniAOD ADD here sequences/modules which rely ONLY on collections stored in the MiniAOD format.

Definition at line 110 of file DQMOffline_Trigger_cff.py.

tuple DQMOffline_Trigger_cff.offlineHLTSourceWithRECO

Initial value:

= cms.Sequence(
      hltFiltersDQM
    * egHLTOffDQMSource       ## NEEDED in VALIDATION, not really in MONITORING
    * egHLTOffDQMSource_HEP17 ## NEEDED in VALIDATION, not really in MONITORING
    * jetMETHLTOfflineAnalyzer
    * b2gHLTDQMSourceWithRECO ## ak8PFJetsPuppiSoftDrop collection is not available in AOD, actually it is produced by the miniAOD step
)

w/ the RECO step on-the-fly (to be added to offlineHLTSourceOnAOD which should run anyhow)

Definition at line 140 of file DQMOffline_Trigger_cff.py.

tuple DQMOffline_Trigger_cff.offlineValidationHLTSource

Initial value:

= cms.Sequence(
      offlineHLTSource
    + offlineHLTSourceOnAODextra
)

Definition at line 259 of file DQMOffline_Trigger_cff.py.

tuple DQMOffline_Trigger_cff.offlineValidationHLTSourceOnAOD

Initial value:

= cms.Sequence(
      offlineHLTSourceOnAOD
    + offlineHLTSourceOnAODextra
)

offline DQM to be run on AOD (w/o the need of the RECO step on-the-fly) in the VALIDATION of the HLT menu based on data it is needed in order to have the DQM code in the release, w/o the issue of crashing the tier0 as the new modules in the sequence offlineHLTSourceOnAODextra are tested these have to be migrated in the main offlineHLTSourceOnAOD sequence

Definition at line 240 of file DQMOffline_Trigger_cff.py.

tuple DQMOffline_Trigger_cff.triggerOfflineDQMSource

Initial value:

= cms.Sequence(
    offlineHLTSource
)

sequence run (called by main DQM sequences in DQMOffline/Configuration/python/DQMOffline_cff.py) on all PDs, but HLTMonitor one

Definition at line 253 of file DQMOffline_Trigger_cff.py.