[14_0_X] Monopole SKIM updates for Run 3

[ThOliveira23]

PR description:

Provide an update to the trigger paths to be employed in the MONOPOLE SKIM file for the Run 3. The additional inclusion of trigger paths associated with MET can be mentioned.
Additionally, the inclusion of the EXOMONOPOLE SKIM file to be executed in the MET and JetMET datasets for the Run 3.

PR validation:
The PR was validated through the the basic test procedure available in the CMSSW PR instructions

This PR is a backport of #45134 for the release 14_0_X.

[cmsbuild]

A new Pull Request was created by @ThOliveira23 for CMSSW_14_0_X.

It involves the following packages:

• Configuration/Skimming (pdmv)

@miquork, @AdrianoDee, @sunilUIET, @cmsbuild can you please review it and eventually sign? Thanks.
@youyingli, @missirol, @Martin-Grunewald, @fabiocos this is something you requested to watch as well.
@sextonkennedy, @rappoccio, @antoniovilela you are the release manager for this.

cms-bot commands are listed here

[cmsbuild]

cms-bot internal usage

[ThOliveira23]

FYI: @malbouis, @srimanob, @CarstenHensel

[AdrianoDee]

@ThOliveira23 which is the runTheMatrix wf using this skim (if any)?

[srimanob]

Should PR go to master first?

[ThOliveira23]

@ThOliveira23 which is the runTheMatrix wf using this skim (if any)?

Dear @AdrianoDee, I'm not sure if I understood the question.

[malbouis]

@ThOliveira23 which is the runTheMatrix wf using this skim (if any)?

Hi @AdrianoDee , for the DATA workflows, I think any workflow running the SKIM:EGamma* or SKIM:JetMET* datasets will run it due to the autoSkim matrix.

[AdrianoDee]

Dear @AdrianoDee, I'm not sure if I understood the question.

Yes sorry I was a bit obscure, I was "jargony" referring to the workflows we could use to test this setup in the release Helena kindly pointed to them. Anyway as @srimanob was mentioning, would be better if you can open the corresponding PR to master. And also make it clear in the title this PR is to 14_0_X (you can simply prepend [14_0_X] to it as in, e.g., #45115).

[youyingli]

Hi @ThOliveira23 , just make sure if the update is for full Run3 or just 2024. And from your skim config, you mention that the updating aims at 2024, but there is no MET dataset in 2024 as it's merged into JetMET.

On the other hand, I also roughly check your HLT Paths but it seems that HLT_PFMET170_HBHECleaned_v*, HLT_PFMET300_v* are only for 2016 data taking and HLT_PFMET250_HBHECleaned_v* and HLT_PFMET200_HBHE_BeamHaloCleaned_v* are only for 2017 and 2018 data taking. Could you please check if the paths are what you expect in 2024 (or full Run3 I could say)?

[ThOliveira23]

Hi @ThOliveira23 , just make sure if the update is for full Run3 or just 2024. And from your skim config, you mention that the updating aims at 2024, but there is no MET dataset in 2024 as it's merged into JetMET.

On the other hand, I also roughly check your HLT Paths but it seems that HLT_PFMET170_HBHECleaned_v*, HLT_PFMET300_v* are only for 2016 data taking and HLT_PFMET250_HBHECleaned_v* and HLT_PFMET200_HBHE_BeamHaloCleaned_v* are only for 2017 and 2018 data taking. Could you please check if the paths are what you expect in 2024 (or full Run3 I could say)?

Dear @youyingli, these updates are meant to cover all the Run 3, not only 2024. If I understood and implemented correctly, there is MET and JetMET for 2022 and only JetMET for 2023 (and 2024). In that sense, the idea is execute the Monopole SKIM in all the MET datasets of the Run 3.

Concerning the trigger paths: The expected trigger paths for the Run 3 HLT_PFMET200_BeamHaloCleaned_v* and the HLT_Photon200_v*. If the trigger paths concerning the Run 2 (2016 and 2017, 2018) aren't necessary, I think that they can be removed from the skim config file.

[cmsbuild]

Pull request #45128 was updated. @AdrianoDee, @miquork, @sunilUIET, @cmsbuild can you please check and sign again.

[srimanob]

@cmsbuild please test

[cmsbuild]

+1

Summary: https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-bcbfb5/39992/summary.html
COMMIT: b4ed0c6
CMSSW: CMSSW_14_0_X_2024-06-20-1100/el8_amd64_gcc12
User test area: For local testing, you can use /cvmfs/cms-ci.cern.ch/week0/cms-sw/cmssw/45128/39992/install.sh to create a dev area with all the needed externals and cmssw changes.

Comparison Summary

Summary:

• You potentially added 84 lines to the logs
• Reco comparison results: 56 differences found in the comparisons
• DQMHistoTests: Total files compared: 48
• DQMHistoTests: Total histograms compared: 3342458
• DQMHistoTests: Total failures: 6
• DQMHistoTests: Total nulls: 0
• DQMHistoTests: Total successes: 3342432
• DQMHistoTests: Total skipped: 20
• DQMHistoTests: Total Missing objects: 0
• DQMHistoSizes: Histogram memory added: 0.0 KiB( 47 files compared)
• Checked 202 log files, 165 edm output root files, 48 DQM output files
• TriggerResults: no differences found

[youyingli]

Hi @cms-sw/pdmv-l2, could you please sign this PR?

[sunilUIET]

+pdmv

[cmsbuild]

This pull request is fully signed and it will be integrated in one of the next CMSSW_14_0_X IBs (tests are also fine) and once validation in the development release cycle CMSSW_14_1_X is complete. This pull request will now be reviewed by the release team before it's merged. @sextonkennedy, @antoniovilela, @rappoccio (and backports should be raised in the release meeting by the corresponding L2)

[antoniovilela]

Please add a link to the master PR in the description, and indicate this is a backport.

[ThOliveira23]

The PR description was updated. The backport indication and the link of the PR for the master were added.

[antoniovilela]

+1