Adding Two Secondary Datasets for JME POG

[jordan-martins]

Hi,

This PR addresses the ongoing effort within JME POG to understand the highPt Jets tail highlighted by the dijet analysis. The idea is to provide two SDs from Muon (Z+jets) and EGamma (Photon+jets) PDs streamed by specific HLT paths.

In this PR we offer the following:

• PDWG_EGMJME_SD_cff.py: This file filters the HLT path for the EGamma PD
• PDWG_MUOJME_SD_cff.py: This file filters the HLT path for the Muon PD
• Skims_PDWG_cff.py: This is updated with the event content to be requested. We have set up RAW-RECO (not just RAW because we have experienced troubles with RAW as SD within T0; see ReseverDMu example)
• autoSkim.py: This is updated for two purposes:
  1- in the scope of this PR, 2022 has Muon and EGamma, and 2023 has EGamma[0,1] and Muon[0,1]
  2- given that a full ReRECO of 2022 and 2023 is on the horizon, 2022 PDs have been allowed (removed the #) so that PdmV can ask for the Skims as a whole for all the PDs.

There will be a backport to 13_3_X and 13_0_X.

Thanks,
PPD

[jordan-martins]

please test

[cmsbuild]

+code-checks

Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-43534/38116

• This PR adds an extra 24KB to repository

• Found files with invalid states:

  • Configuration/Skimming/python/PDWG_EGMJME_SD_cff.py.:
    • Added: 9e46944
    • Modified: d3e9e1d
    • Deleted: 7cc2d00

• There are other open Pull requests which might conflict with changes you have proposed:

  • File Configuration/Skimming/python/Skims_PDWG_cff.py modified in PR(s): Adding MinBias generator skims #43212

[cmsbuild]

A new Pull Request was created by @jordan-martins (Jordan Martins) for master.

It involves the following packages:

• Configuration/Skimming (pdmv)

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

cms-bot commands are listed here

[cmsbuild]

+1

Summary: https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-1ec2c8/36394/summary.html
COMMIT: 7cc2d00
CMSSW: CMSSW_14_0_X_2023-12-09-1100/el8_amd64_gcc12
User test area: For local testing, you can use /cvmfs/cms-ci.cern.ch/week0/cms-sw/cmssw/43534/36394/install.sh to create a dev area with all the needed externals and cmssw changes.

Comparison Summary

Summary:

• You potentially added 45 lines to the logs
• Reco comparison results: 24 differences found in the comparisons
• DQMHistoTests: Total files compared: 50
• DQMHistoTests: Total histograms compared: 3430794
• DQMHistoTests: Total failures: 1280
• DQMHistoTests: Total nulls: 0
• DQMHistoTests: Total successes: 3429492
• DQMHistoTests: Total skipped: 22
• DQMHistoTests: Total Missing objects: 0
• DQMHistoSizes: Histogram memory added: 0.0 KiB( 49 files compared)
• Checked 214 log files, 167 edm output root files, 50 DQM output files
• TriggerResults: no differences found

[youyingli]

Hi @jordan-martins , following the full ReReco 2022/2023 based on CMSSW_14_0_X, is it necessary to backport to 13_3_X and 13_0_X? Or will JME POG have special production under those cmssw versions?

On the other hand, the HLTs for some skims are different between 2022 and 2023. I will put both years' HLTs together for these skims to synchronize 2022 and 2023 full ReReco skim after this PR is merged.

[jordan-martins]

Hi @youyingli,

We will have a special production for the JETMET for 2022 and 2023 plus the Muon and EGamma 22FG PDs. For that, we will use the 130X. At some point, it was unclear if we wanted to move to 133X, mainly because of the nanov13 (yet to be concluded at 133X), hence why the backport for that as well, and not 132X or 131X.

Thanks for checking the HLTs skims, indeed, as you highlighted, we will do a full ReRECO of 2022 and 2023 in 140X that will require not only Skims but AlCa outputs to be available for those years based on the PDs (as some had naming changes :) ).

Is it clear?

Thanks,
PPD

[youyingli]

Hi @youyingli,

We will have a special production for the JETMET for 2022 and 2023 plus the Muon and EGamma 22FG PDs. For that, we will use the 130X. At some point, it was unclear if we wanted to move to 133X, mainly because of the nanov13 (yet to be concluded at 133X), hence why the backport for that as well, and not 132X or 131X.

Thanks for checking the HLTs skims, indeed, as you highlighted, we will do a full ReRECO of 2022 and 2023 in 140X that will require not only Skims but AlCa outputs to be available for those years based on the PDs (as some had naming changes :) ).

Is it clear?

Thanks, PPD

Thanks for the clarification. @sunilUIET, could you please sign it and its backports? Thanks!

[AdrianoDee]

+pdmv

[cmsbuild]

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. @antoniovilela, @rappoccio, @sextonkennedy (and backports should be raised in the release meeting by the corresponding L2)

[rappoccio]

+1