-
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
Use akCs4PFJets for candidate-based tagInfos for HI workflows #31674
Conversation
The code-checks are being triggered in jenkins. |
+code-checks Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-31674/18802
|
A new Pull Request was created by @mandrenguyen (Matthew Nguyen) for master. It involves the following packages: DQMOffline/RecoB @perrotta, @andrius-k, @kmaeshima, @ErnestaP, @cmsbuild, @jfernan2, @fioriNTU, @slava77, @jpata, @santocch can you please review it and eventually sign? Thanks. cms-bot commands are listed here |
@cmsbuild please test workflow 158.1, 158.2, 158.3, 159.1, 159.3, 159.4, 300.0, 301.0, 302.0, 130.0, 311.0, 312.0 |
The tests are being triggered in jenkins.
|
-1 Tested at: 8474eb7 CMSSW: CMSSW_11_2_X_2020-10-05-1200 I found follow errors while testing this PR Failed tests: UnitTests
I found errors in the following unit tests: ---> test TestDQMOfflineConfiguration100 had ERRORS |
Comparison job queued. |
looks unrelated to this PR
has the same issue. |
Comparison is ready @slava77 comparisons for the following workflows were not done due to missing matrix map:
Comparison Summary:
|
so, this is not really a bigfix, it's a feature change for AOD default b-tagging. I'm still assuming that we stay in 11_X for HI miniAOD. |
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.
it looks like a limited bugfix would be to modify patJetsBDHadron in Validation/RecoB/python/BDHadronTrackValidation_cff.py
Updates in soft lepton taginfos are apparently not related to the crashes.
Are the updates made here going to produce usable results or is it likely that everything will need to be reconfigured in a significant way?
|
||
from Configuration.Eras.Modifier_pp_on_AA_2018_cff import pp_on_AA_2018 | ||
from Configuration.Eras.Modifier_pp_on_PbPb_run3_cff import pp_on_PbPb_run3 | ||
(pp_on_AA_2018 | pp_on_PbPb_run3).toModify(pfImpactParameterTagInfos, jets = "akCs4PFJets") |
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.
is this enough to correctly run pfImpactParameterTagInfos
for HI?
(similar question applies to the rest).
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.
No, it was not sufficient to modify pfImpactParamterTagInfos. The soft lepton tag infos had to use the consistent jet collection to avoid crashes. I first modified the input to pfImpactParamterTagInfos, but the code was still crashing until I updated the other tag infos. All of the modifications made are necessary to avoid crashes.
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.
I didn't mean the soft lepton taggers.
My question was if the switch of the jet for pfImpactParameterTagInfos
expected to provide performance of pfImpactParameterTagInfos
acceptable for physics in HI or if more significant changes are needed.
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.
The difference between impactParamterTagInfos and pfImpactParameterTagInfos is basically technical. There should not be any significant difference in performance. I verified this some time ago. We will check this again before actually calculating b-tag discriminators based on the candidate tagInfos. At the moment, they are not really used for anything in the HI workflow besides this validation package, AFAIK.
Comparison is ready Comparison Summary:
|
merge |
It seems there is still a problem in an HIon workflow (HLT validation tests suite):
|
Hi @Martin-Grunewald |
Yes, it runs some more steps after reco: In a recent developer area:
|
This error was not picked up in the standard relval wf 159 because the validation is limited to VALIDATION:@standardValidationNoHLT+@miniAODValidation |
I think that eventually the goal should be to cleanup the DQM/Validation for the HI setup. |
+1 |
right, the creation of all modules is short-circuited |
+1 |
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 be automatically merged. |
PR description:
Update candidate based tagInfos to use HI jet collection (akCs4PFJets) in HI workflows.
This fixes an issue created in #30898, which is causing crashes in several HI workflows ( #31670 ).
The issue is that the b-tagging validation clones the 'patJets', but changes from the track-based tagInfos that we use to the candidate-based ones used nowadays in pp.
The solution is to update the candidate-based tagInfos to use akCs4PFJets, which was anyway on the to-do list for Run 3, when we plan update to those in the HI b-tagging sequence. This issue was spotted running wfs like 158.1.
There was also a trivial change to the name of the cleaned heavy ion genJet module, which had a conflict (affected wf 150, for example).
PR validation:
Tested on wf 150, 158.1 and 158.01. Please test on the other wfs identified in #31670
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: