Muon skims for the 2025 light-ion runs

[flodamas]

PR description:

Implementation of two muon skims for the upcoming light-ion runs (pO / OO / NeNe) based on PAT muon objects. Some EDM collections are removed from the skimmed event contents to reduce the file sizes.

PR validation:

Unit tests passed successfully.

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:

Will be backported to 15_0_X for data taking.

[cmsbuild]

cms-bot internal usage

[cmsbuild]

+code-checks

Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-48386/45281

[cmsbuild]

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

It involves the following packages:

• Configuration/Skimming (pdmv)
• Configuration/StandardSequences (operations)

@AdrianoDee, @antoniovilela, @cmsbuild, @davidlange6, @DickyChant, @fabiocos, @mandrenguyen, @miquork, @rappoccio can you please review it and eventually sign? Thanks.
@GiacomoSguazzoni, @Martin-Grunewald, @VinInn, @VourMa, @denizsun, @dgulhan, @fabiocos, @felicepantaleo, @makortel, @missirol, @mmusich, @mtosi, @rovere, @salimcerci, @sameasy, @slomeo, @youyingli this is something you requested to watch as well.
@antoniovilela, @mandrenguyen, @rappoccio, @sextonkennedy you are the release manager for this.

cms-bot commands are listed here

[mandrenguyen]

please test
Although won't be picked up in any existing workflows.

[cmsbuild]

-1

Failed Tests: RelVals
Size: This PR adds an extra 28KB to repository
Summary: https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-bcc041/46876/summary.html
COMMIT: 1878717
CMSSW: CMSSW_15_1_X_2025-06-23-1100/el8_amd64_gcc12
User test area: For local testing, you can use /cvmfs/cms-ci.cern.ch/week1/cms-sw/cmssw/48386/46876/install.sh to create a dev area with all the needed externals and cmssw changes.

RelVals

• 1000.0

----- Begin Fatal Exception 23-Jun-2025 16:49:19 CEST-----------------------
An exception of category 'ProductNotFound' occurred while
   [0] Processing  Event run: 165121 lumi: 62 event: 23609118 stream: 0
   [1] Running path 'HighPtMuonIonSkimPath'
   [2] Calling method for module PATMuonRefSelector/'highPtMuonSelectorForMuonIon'
Exception Message:
Principal::getByToken: Found zero products matching all criteria
Looking for type: std::vector<pat::Muon>
Looking for module label: slimmedMuons
Looking for productInstanceName: 

   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 -------------------------------------------------

[flodamas]

Hi, do I understand correctly that the failing workflow is based on Run 1 data whereas miniAOD did not exist at that time?

Workflow 1000 runs all the skims (see step SKIMD), including the MuonPOG skim which is also based on PAT objects, but the latter does not seem to cause any error (skim output file produced but contains 0 event, see runTheMatrix results) probably because none of these RunMinBias2011A events pass the HLT filters.

Please let me know if this is the case so that we can find a solution to the failing test. Thanks!

[youyingli]

Maybe you can try to add the following code in here.

for s in autoSkim.keys():

    if 'ZeroBias' in s:
        steps['SKIM'+s.upper()+'RUN3_reHLT_2025'] = merge([{'-s':'RAW2DIGI,L1Reco,RECO,SKIM:%s,PAT,NANO,DQM:@rerecoZeroBias+@miniAODDQM+@nanoAODDQM'%(autoSkim[s])},steps['RECONANORUN3_reHLT_2025']])
    elif 'Cosmics' in s:
        steps['SKIM'+s.upper()+'RUN3_reHLT_2025'] = merge([{'--scenario':'cosmics', '-s':'RAW2DIGI,L1Reco,RECO,SKIM:%s,DQM'%(autoSkim[s]), '--datatier':'RECO,DQMIO', '--eventcontent':'RECO,DQM'},steps['RECONANORUN3_reHLT_2025']])
    else:
        steps['SKIM'+s.upper()+'RUN3_reHLT_2025'] = merge([{'-s':'RAW2DIGI,L1Reco,RECO,SKIM:%s,PAT,NANO,DQM:@standardDQM+@miniAODDQM+@nanoAODDQM'%(autoSkim[s])},steps['RECONANORUN3_reHLT_2025']])

Add the following code in here. This uses HIForward 2024 dataset to test including this SKIM.

workflows[143.921] = ['',['RunUPC2024', 'SKIMIONPHYSICS0RUN3_reHLT_2025', 'HARVESTDPROMPTR3']]

This could solve this issue. To test them offline, please use

runTheMatrix.py -w "standard" -l 143.921 and then update this PR.

[cmsbuild]

+code-checks

Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-48386/45296

[mandrenguyen]

urgent
Needed for upcoming "special runs"

[cmsbuild]

+1

Size: This PR adds an extra 96KB to repository
Summary: https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-bcc041/46922/summary.html
COMMIT: 06c85a6
CMSSW: CMSSW_15_1_X_2025-06-25-1100/el8_amd64_gcc12
User test area: For local testing, you can use /cvmfs/cms-ci.cern.ch/week1/cms-sw/cmssw/48386/46922/install.sh to create a dev area with all the needed externals and cmssw changes.

Comparison Summary

Summary:

• You potentially removed 19 lines from the logs
• Reco comparison results: 6 differences found in the comparisons
• DQMHistoTests: Total files compared: 50
• DQMHistoTests: Total histograms compared: 4065619
• DQMHistoTests: Total failures: 40
• DQMHistoTests: Total nulls: 0
• DQMHistoTests: Total successes: 4065559
• DQMHistoTests: Total skipped: 20
• DQMHistoTests: Total Missing objects: 0
• DQMHistoSizes: Histogram memory added: 0.0 KiB( 49 files compared)
• Checked 215 log files, 184 edm output root files, 50 DQM output files
• TriggerResults: no differences found

[mandrenguyen]

@cms-sw/upgrade-l2 @cms-sw/pdmv-l2 can you have a look please?

[Moanwar]

+Upgrade

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

[mandrenguyen]

+1

[mandrenguyen]

This PR seems to cause crashes in workflows 4.17 and 4.29, Run 1 workflows with prompt skims. see for example:
https://cmssdt.cern.ch/SDT/cgi-bin/logreader/el8_amd64_gcc12/CMSSW_15_1_X_2025-06-26-2300/pyRelValMatrixLogs/run/4.17_RunMinBias2011A/step5_RunMinBias2011A.log#/

[mmusich]

This PR seems to cause crashes in workflows 4.17 and 4.29, Run 1 workflows with prompt skims

I guess the same concept to should be applied also for these workflows:

cmssw/Configuration/PyReleaseValidation/python/relval_steps.py

Line 4419 in 1a09f40

steps['SKIMDreHLT'] = merge([ {'--conditions':'auto:run1_data_%s'%menu, '--hltProcess':'reHLT', '--filein':'file:step3.root'}, steps['SKIMD'] ])

steps['SKIMD'] => steps['SKIMDRun1']

[flodamas]

This PR seems to cause crashes in workflows 4.17 and 4.29, Run 1 workflows with prompt skims

I guess the same concept to should be applied also for these workflows:

cmssw/Configuration/PyReleaseValidation/python/relval_steps.py

Line 4419 in 1a09f40

steps['SKIMDreHLT'] = merge([ {'--conditions':'auto:run1_data_%s'%menu, '--hltProcess':'reHLT', '--filein':'file:step3.root'}, steps['SKIMD'] ])

steps['SKIMD'] => steps['SKIMDRun1']

Oops, sorry for that. I guess I have to make a new PR to fix the master branch.
But the backport to 15_0_X #48397 has not been merged yet and is the most urgent now, should I simply push a new commit there even if the two PRs will differ?

[mmusich]

should I simply push a new commit there even if the two PRs will differ?

yes, please.