Skip to content

JME Offline DQM: adding trigger efficiency for scouting jets#50188

Merged
cmsbuild merged 14 commits intocms-sw:masterfrom
etzovara:JetMETScoutDQM_1601X_ScoutTriggEff
Mar 11, 2026
Merged

JME Offline DQM: adding trigger efficiency for scouting jets#50188
cmsbuild merged 14 commits intocms-sw:masterfrom
etzovara:JetMETScoutDQM_1601X_ScoutTriggEff

Conversation

@etzovara
Copy link
Copy Markdown
Contributor

@etzovara etzovara commented Feb 19, 2026

PR description:

This PR summarises changes in the cmssw/DQMOffline/Trigger/ framework in order to include trigger efficiency calculations for scouting jets for offline monitoring. The relevant modules run only with online and offline scouting DQM with scouting datasets, to avoid crash due to missing scouting objects (specifically rho) from other datasets. Also, modules w/o JECs have been created in order to avoid similar crash in RelVals. (Issues thoroughly described in #49377 and #49358).

Relevant reports about the development and validation of this work can be found in:

cc: @silviodonato @patinkaew

PR validation:

This PR has been prepared starting from:

cmsrel CMSSW_16_1_X_2026-02-15-2300
cd CMSSW_16_1_X_2026-02-15-2300/src
cmsenv
git cms-init
git cms-addpkg DQMOffline/HLTScouting DQMOffline/Trigger DQMOffline/Configuration DQMOffline/JetMET PhysicsTools/SelectorUtils DQM/HLTEvF
scram b
scram build code-checks
scram build code-format

[1]: input: ScoutingPFMonitor/AOD/PromptReco-v1/ dataset (specifically testing with files from era 2025G, run 398827)
[2]: cmsDriver.py step2 -s DQM:jetmetScoutingMonitorHLT--conditions 150X_dataRun3_Prompt_v1 --datatier DQMIO -n -1 --eventcontent DQM --geometry DB:Extended --era Run3 --filein /store/data/Run2025G/ScoutingPFMonitor/AOD/PromptReco-v1/000/398/827/00000/1b30ead2-bc1f-42c3-87ca-dba7b395d525.root --fileout file:stepDQM.root --python_filename DQM_cfg.py --data --scenario pp --no_exec (or cmsDriver.py step2 -s DQM:jetmetScoutingNoJECsMonitorHLT--conditions 150X_dataRun3_Prompt_v1 --datatier DQMIO -n -1 --eventcontent DQM --geometry DB:Extended --era Run3 --filein /store/data/Run2025G/ScoutingPFMonitor/AOD/PromptReco-v1/000/398/827/00000/1b30ead2-bc1f-42c3-87ca-dba7b395d525.root --fileout file:stepDQM.root --python_filename DQM_cfg.py --data --scenario pp --no_exec)
[3]: cmsRun DQM_cfg.py
[4]: cmsDriver.py step3 -s HARVESTING:hltOfflineDQMClient --harvesting AtRunEnd --filein file:stepDQM.root --python_filename harvesting_cfg.py --conditions 150X_dataRun3_Prompt_v1 --data --filetype DQM --scenario pp --era Run3 --geometry DB:Extended -n -1 --no_exec
[5]: cmsRun harvesting_cfg.py

If this PR is a backport please specify the original PR and why you need to backport that PR. If this PR will be backported please specify to which release cycle the backport is meant for:

This PR is intended for the master branch.
Since, it is for monitoring of 2025 and on data it should be backported to CMSSW_16_0_X (maybe also to CMSSW_15_0_X???).

@cmsbuild
Copy link
Copy Markdown
Contributor

cmsbuild commented Feb 19, 2026

cms-bot internal usage

@cmsbuild
Copy link
Copy Markdown
Contributor

@cmsbuild
Copy link
Copy Markdown
Contributor

A new Pull Request was created by @etzovara for master.

It involves the following packages:

  • DQMOffline/Trigger (dqm)
  • PhysicsTools/SelectorUtils (reconstruction)

@Moanwar, @cmsbuild, @ctarricone, @gabrielmscampos, @jfernan2, @mandrenguyen, @nothingface0, @rseidita, @srimanob can you please review it and eventually sign? Thanks.
@Fedespring, @HuguesBrun, @cericeci, @jhgoh, @missirol, @mmusich, @mtosi, @rociovilar, @trocino this is something you requested to watch as well.
@ftenchini, @mandrenguyen, @sextonkennedy you are the release manager for this.

cms-bot commands are listed here

@gabrielmscampos
Copy link
Copy Markdown
Member

please test

@cmsbuild
Copy link
Copy Markdown
Contributor

-1

Failed Tests: RelVals RelVals-INPUT
Size: This PR adds an extra 20KB to repository
Summary: https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-df860b/51437/summary.html
COMMIT: 77cb014
CMSSW: CMSSW_16_1_X_2026-02-19-1100/el8_amd64_gcc13
User test area: For local testing, you can use /cvmfs/cms-ci.cern.ch/week1/cms-sw/cmssw/50188/51437/install.sh to create a dev area with all the needed externals and cmssw changes.

Failed RelVals

----- Begin Fatal Exception 19-Feb-2026 15:53:04 CET-----------------------
An exception of category 'ProductNotFound' occurred while
   [0] Processing  Event run: 346512 lumi: 250 event: 243042266 stream: 0
   [1] Running path 'dqmoffline_7_step'
   [2] Prefetching for module JetMonitor/'L1SingleJet200_Prommonitoring'
   [3] Prefetching for module ChainedJetCorrectorProducer/'ak4PFScoutL1FastL2L3ResidualCorrector'
   [4] Calling method for module L1FastjetCorrectorProducer/'ak4PFScoutL1FastjetCorrector'
Exception Message:
Principal::getByToken: Found zero products matching all criteria
Looking for type: double
Looking for module label: hltScoutingPFPacker
Looking for productInstanceName: rho

   Additional Info:
      [a] If you wish to continue processing events after a ProductNotFound exception,
add "TryToContinue = cms.untracked.vstring('ProductNotFound')" to the "options" PSet in the configuration.

----- End Fatal Exception -------------------------------------------------
----- Begin Fatal Exception 19-Feb-2026 16:08:07 CET-----------------------
An exception of category 'ProductNotFound' occurred while
   [0] Processing  Event run: 165121 lumi: 62 event: 23609118 stream: 0
   [1] Running path 'dqmoffline_11_step'
   [2] Prefetching for module JetMonitor/'L1SingleJet200_Prommonitoring'
   [3] Prefetching for module ChainedJetCorrectorProducer/'ak4PFScoutL1FastL2L3ResidualCorrector'
   [4] Calling method for module L1FastjetCorrectorProducer/'ak4PFScoutL1FastjetCorrector'
Exception Message:
Principal::getByToken: Found zero products matching all criteria
Looking for type: double
Looking for module label: hltScoutingPFPacker
Looking for productInstanceName: rho

   Additional Info:
      [a] If you wish to continue processing events after a ProductNotFound exception,
add "TryToContinue = cms.untracked.vstring('ProductNotFound')" to the "options" PSet in the configuration.

----- End Fatal Exception -------------------------------------------------
----- Begin Fatal Exception 19-Feb-2026 16:08:43 CET-----------------------
An exception of category 'ProductNotFound' occurred while
   [0] Processing  Event run: 165121 lumi: 62 event: 23609118 stream: 0
   [1] Running path 'dqmoffline_10_step'
   [2] Prefetching for module JetMonitor/'L1SingleJet200_Prommonitoring'
   [3] Prefetching for module ChainedJetCorrectorProducer/'ak4PFScoutL1FastL2L3ResidualCorrector'
   [4] Calling method for module L1FastjetCorrectorProducer/'ak4PFScoutL1FastjetCorrector'
Exception Message:
Principal::getByToken: Found zero products matching all criteria
Looking for type: double
Looking for module label: hltScoutingPFPacker
Looking for productInstanceName: rho

   Additional Info:
      [a] If you wish to continue processing events after a ProductNotFound exception,
add "TryToContinue = cms.untracked.vstring('ProductNotFound')" to the "options" PSet in the configuration.

----- End Fatal Exception -------------------------------------------------
Expand to see more relval errors ...

Failed RelVals-INPUT

  • 136.7801136.7801_RunHLTPhy2017B_AOD/step2_RunHLTPhy2017B_AOD.log
  • 136.7803136.7803_RunHLTPhy2017B_RAWAOD/step2_RunHLTPhy2017B_RAWAOD.log
  • 1003.01003.0_RunMinBias2012A/step2_RunMinBias2012A.log
Expand to see more relval errors ...

…equence analogous to 'jetmetScoutingMonitorHLT' but w/o JECs
…jetmetScoutingNoJECsMonitorHLT' modules to run only with scouting DQM (the latter is to avoid crash with RelVals)
@mmusich
Copy link
Copy Markdown
Contributor

mmusich commented Mar 2, 2026

+hlt

@gabrielmscampos
Copy link
Copy Markdown
Member

+dqm

@mmusich
Copy link
Copy Markdown
Contributor

mmusich commented Mar 9, 2026

@cms-sw/reconstruction-l2 your signature is expected here.
@etzovara do you plan a backport?

@Moanwar
Copy link
Copy Markdown
Contributor

Moanwar commented Mar 10, 2026

@cms-sw/reconstruction-l2 your signature is expected here. @etzovara do you plan a backport?

Noted from reconstruction-l2. I will check it asap and get back to you

@etzovara
Copy link
Copy Markdown
Contributor Author

@mmusich yes, I would like to do backport. Can I already proceed with it?

@patinkaew
Copy link
Copy Markdown
Contributor

sorry for answering instead, @mmusich. hope you don't mind.

@etzovara, given that all the tests pass, I think you can already open a backport PR so we can start the test for backport to 16_0_X. So please proceed with the backport :)

@Moanwar
Copy link
Copy Markdown
Contributor

Moanwar commented Mar 10, 2026

+1

@cmsbuild
Copy link
Copy Markdown
Contributor

This pull request is fully signed and it will be integrated in one of the next master IBs (tests are also fine). This pull request will now be reviewed by the release team before it's merged. @ftenchini, @sextonkennedy, @mandrenguyen (and backports should be raised in the release meeting by the corresponding L2)

@etzovara
Copy link
Copy Markdown
Contributor Author

sorry for answering instead, @mmusich. hope you don't mind.

@etzovara, given that all the tests pass, I think you can already open a backport PR so we can start the test for backport to 16_0_X. So please proceed with the backport :)

I thought I should do a backport to 16_1_X. Shall I also do it to 16_0_X?

@patinkaew
Copy link
Copy Markdown
Contributor

I thought I should do a backport to 16_1_X. Shall I also do it to 16_0_X?

Master branch is at 16_1_X, so when this PR will be merged to 16_1_X.
Please open a backport to 16_0_X (data-taking) :).

@ftenchini
Copy link
Copy Markdown

+1

@mmusich
Copy link
Copy Markdown
Contributor

mmusich commented Mar 20, 2026

Please open a backport to 16_0_X (data-taking) :).

is the backport available?

@etzovara
Copy link
Copy Markdown
Contributor Author

Please open a backport to 16_0_X (data-taking) :).

is the backport available?

I'm proceeding with it right after the meeting

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

9 participants