-
Notifications
You must be signed in to change notification settings - Fork 4.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[14_1_X] Update the PbPb skims for 2024 data taking #46458
Conversation
A new Pull Request was created by @flodamas for CMSSW_14_1_X. It involves the following packages:
@AdrianoDee, @cmsbuild, @kskovpen, @miquork, @sunilUIET can you please review it and eventually sign? Thanks. cms-bot commands are listed here
|
cms-bot internal usage |
backport of #46447 |
@cms-sw/pdmv-l2, could you please test it? |
please test |
+1 Size: This PR adds an extra 12KB to repository Comparison SummarySummary:
|
041c459
to
6aef98c
Compare
Pull request #46458 was updated. @AdrianoDee, @cmsbuild, @kskovpen, @miquork, @sunilUIET can you please check and sign again. |
Pull request #46458 was updated. @AdrianoDee, @cmsbuild, @kskovpen, @miquork, @sunilUIET can you please check and sign again. |
please test |
+1 Size: This PR adds an extra 12KB to repository Comparison SummarySummary:
|
urgent |
Pull request #46458 was updated. @AdrianoDee, @cmsbuild, @DickyChant, @miquork can you please check and sign again. |
please test |
+1 Size: This PR adds an extra 16KB to repository The following merge commits were also included on top of IB + this PR after doing git cms-merge-topic: You can see more details here: Comparison SummarySummary:
|
+pdmv |
This pull request is fully signed and it will be integrated in one of the next CMSSW_14_1_X IBs (tests are also fine) and once validation in the development release cycle CMSSW_14_2_X is complete. This pull request will now be reviewed by the release team before it's merged. @sextonkennedy, @rappoccio, @antoniovilela, @mandrenguyen (and backports should be raised in the release meeting by the corresponding L2) |
+1 |
cut = cms.string('(mass > 60) && (charge=0)'), | ||
decay = cms.string("tightMuonsForPbPbZMuSkim looseIsoMuonsForPbPbZMuSkim") | ||
cut = cms.string('(mass > 60)'), | ||
decay = cms.string("tightMuonsForPbPbZMuSkim looseMuonsForPbPbZMuSkim") |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@flodamas it appears that this change made the Tier0 replay with CMSSW_14_1_4_patch4
fail with the following error:
2024-11-01 22:25:10,703:CRITICAL:CMSSW:Error message: An exception of category 'ProductNotFound' occurred while
[0] Processing Event run: 374951 lumi: 31 event: 43921116 stream: 2
[1] Running path 'ZMuSkimPathPbPb'
[2] Calling method for module CandViewShallowCloneCombiner/'dimuonsForPbPbZMuSkim'
Exception Message:
Principal::getByToken: Found zero products matching all criteria
Looking for a container with elements of type: reco::Candidate
Looking for module label: looseMuonsForPbPbZMuSkim
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.
looseMuonsForPbPbZMuSkim
produces a skimmed reco::TrackCollection
while CandViewShallowCloneCombiner
necessitates of a collection of reco::Candidate
-s in input.
Shouldn't this be ConcretelooseMuonsForPbPbZMuSkim
instead?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
PR description:
Backport of #46447