-
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
Mask more old b-taggers for run3_common #40464
Merged
Merged
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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.
Just a suggestion, not a strict requirement (coming from BTV Reco):
To apply these changes to all the Computers which might be called somewhere, these modifications could be extended to also touch
positiveSoftPFMuonComputer
,negativeSoftPFMuonComputer
,positiveSoftPFElectronComputer
,positiveSoftPFElectronComputer
in the exact same way. All six producers here use the same PSet, so they could be changed now as well in one go to also setuseCondDB = cms.bool(False)
, even if these additional four producers are not responsible for any errors in the tests currently.Otherwise the changes look fine.
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.
Hi @AnnikaStein thanks for the suggestion!
Sure I can extend the change to the other producers, but I have one question:
all of them are using the same PSets (
softPF[Muon|Electron]Common
), so wouldn't it be easier to modify directly the "Common" PSets? Or that's too risky because the Common ones might be imported somewhere else?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.
Hi @francescobrivio
I totally agree it would be easier. My initial concern was exactly what you mentioned, with the risk that it might be imported somewhere else. But actually, using the cmssdt lxr and github search, I only found some place in HLT for Phase-2, where this PSet is defined as well, but I found no place where it gets directly imported. From that point of view, it should be safe to follow up with changing the PSet itself in another PR.
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.
hi @AnnikaStein given that from that on it's less of an AlCaDB business, I'm wondering if you could submit the PR? (If yes, please also tag us, just that we can follow it was done)
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.
Hi @tvami
Ok, will do!
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.
Thanks!