JME Offline DQM: adding trigger efficiency for scouting jets#50188
JME Offline DQM: adding trigger efficiency for scouting jets#50188cmsbuild merged 14 commits intocms-sw:masterfrom
Conversation
…trigger efficiency
…xis for Scouting jets
…n (applying also JetID,JECs,MuonID muon isol)
|
cms-bot internal usage |
|
+code-checks Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-50188/48143 |
|
A new Pull Request was created by @etzovara for master. It involves the following packages:
@Moanwar, @cmsbuild, @ctarricone, @gabrielmscampos, @jfernan2, @mandrenguyen, @nothingface0, @rseidita, @srimanob can you please review it and eventually sign? Thanks. cms-bot commands are listed here |
|
please test |
|
-1 Failed Tests: RelVals RelVals-INPUT Failed RelValsExpand to see more relval errors ...Failed RelVals-INPUT |
…equence analogous to 'jetmetScoutingMonitorHLT' but w/o JECs
…jetmetScoutingNoJECsMonitorHLT' modules to run only with scouting DQM (the latter is to avoid crash with RelVals)
… also into online scouting DQM
…odules w/o JECs to avoid crash with RelVals
|
+hlt |
|
+dqm |
|
@cms-sw/reconstruction-l2 your signature is expected here. |
Noted from reconstruction-l2. I will check it asap and get back to you |
|
@mmusich yes, I would like to do backport. Can I already proceed with it? |
|
+1 |
|
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) |
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. |
|
+1 |
is the backport available? |
I'm proceeding with it right after the meeting |
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-2300cd CMSSW_16_1_X_2026-02-15-2300/srccmsenvgit cms-initgit cms-addpkg DQMOffline/HLTScouting DQMOffline/Trigger DQMOffline/Configuration DQMOffline/JetMET PhysicsTools/SelectorUtils DQM/HLTEvFscram bscram build code-checksscram 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(orcmsDriver.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.pyIf 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???).