-
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
Bad PF candidate filter for 2018 PbPb data #31668
Bad PF candidate filter for 2018 PbPb data #31668
Conversation
The code-checks are being triggered in jenkins. |
+code-checks Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-31668/18790
|
A new Pull Request was created by @mandrenguyen (Matthew Nguyen) for master. It involves the following packages: PhysicsTools/PatAlgos @perrotta, @jpata, @cmsbuild, @santocch, @slava77 can you please review it and eventually sign? Thanks. cms-bot commands are listed here |
please test |
The tests are being triggered in jenkins.
|
-1 Tested at: 03d87db CMSSW: CMSSW_11_2_X_2020-10-05-1200 I found follow errors while testing this PR Failed tests: ClangBuild
I found compilation warning while trying to compile with clang. Command used:
See details on the summary page. |
Comparison not run due to Build errors/Fireworks only changes/No short matrix requested (RelVals and Igprof tests were also skipped) |
Comparison job queued. |
Comparison is ready The workflows 158.01 have different files in step1_dasquery.log than the ones found in the baseline. You may want to check and retrigger the tests if necessary. You can check it in the "files" directory in the results of the comparisons Comparison Summary:
|
},hiDefaults2018_ppReco,step3Up2015Defaults]) | ||
steps['REMINIAODHI2018PPRECOMB']=merge([{'-s':'PAT,VALIDATION:@miniAODValidation,DQM:@miniAODDQM', | ||
'--datatier':'MINIAODSIM,DQMIO', | ||
'--eventcontent':'MINIAODSIM,DQM', | ||
'-n':100, | ||
'--era':'Run2_2018_pp_on_AA', | ||
'--procModifiers':'genJetSubEvent', | ||
'--procModifiers':'genJetSubEvent,run2_miniAOD_pp_on_AA_103X', |
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.
@mandrenguyen , please check: is this additional procModifier ("run2_miniAOD_pp_on_AA_103X") really intended for REMINIAODHI2018PPRECOMB
?
(I noticed it because, if I am not wrong, this showed up after the rebase, but it was not there before)
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.
Yes, this procModifier is the one that enables the cleaning of bad PF candidates (the point of this PR). It should be enabled for the (re)miniAOD workflows, but not for the overall pp_on_AA eras. The "MB" version of the reMiniAOD relval workflow was introduced in #31698, the PR that conflicted with this one, and which caused a rebase to be needed. I'm not 100% sure of the sequence of events that led to this being introduced in the rebase, but I confirm that it is the intended behavior.
+1
|
+upgrade |
merge |
@mandrenguyen this PR seems to generate some problems. See #31894 |
+1 |
PR description:
Removes badly reconstructed PF charged hadrons and muons from list of PF candidates stored in the 2018 PbPb AOD. The filtered list is fed into the jet reconstruction (akCs4PFJets), as well as the packed PF candidate collection. The filtered out particles are stored in the following collection, which is stored in miniAOD
patPackedCandidates_packedPFCandidatesCleaned__PAT
The slimmedMuons use both the kept and discarded packed candidates, as input.
Discarded charged hadrons will end up in both packedPFCandidatesCleaned and lostTracks, but the cost of this double storage is small, as bad particles are rare.
Details of the studies used to tune the selection cuts for bad particles may be found here:
https://twiki.cern.ch/twiki/pub/CMS/HiHighPt2019/JetReco_MAN_291710.pdf
https://twiki.cern.ch/twiki/pub/CMS/HiJetReco2019/JetReco_MAN_191010.pdf
PR validation:
Tested with 140.5611
if this PR is a backport please specify the original PR and why you need to backport that PR:
Before submitting your pull requests, make sure you followed this checklist: