-
Notifications
You must be signed in to change notification settings - Fork 4.4k
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
Migrate module configurations in {JetMETCorrections,PhysicsTools} to use automatically generated cfi default/reference configurations #33307
Merged
Merged
Changes from all commits
Commits
Show all changes
2 commits
Select commit
Hold shift + click to select a range
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
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,10 +1,7 @@ | ||
import FWCore.ParameterSet.Config as cms | ||
|
||
mergedMuons = cms.EDProducer("PATMuonMerger", | ||
muons = cms.InputTag("slimmedMuons"), | ||
pfCandidates=cms.InputTag("packedPFCandidates"), | ||
otherTracks = cms.InputTag("lostTracks"), | ||
muonCut = cms.string("pt>15 && abs(eta)<2.4"), | ||
pfCandidatesCut = cms.string("pt>15 && abs(eta)<2.4"), | ||
lostTrackCut = cms.string("pt>15 && abs(eta)<2.4") | ||
import PhysicsTools.PatAlgos.mergedMuonsNoCuts_cfi as _mod | ||
mergedMuons = _mod.mergedMuonsNoCuts.clone( | ||
muonCut = "pt>15 && abs(eta)<2.4", | ||
pfCandidatesCut = "pt>15 && abs(eta)<2.4", | ||
lostTrackCut = "pt>15 && abs(eta)<2.4" | ||
) |
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.
I am not able to find a PFCandPtrProjector plugin anywhere in CMSSW, not even in 9_1_X (which is the release where this config was introduced with #18165)
@mmarionncern and @zdemirag: do you remember where that plugin was defined?
By the way, isn't this config already obsolete (and candidate for possible deletion)?
corMETFromMuonAndEG
is only called by PhysicsTools/PatAlgos/python/slimming/extraSlimmedMETs_MuEGFixMoriond2017.py, which according to the name is quite likely not needed any more. (Moreover,muCorrection=False
in there , and therefore thismuonRecoMitigation
wasn't actually ever accessed even from there...)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.
@kirschen @lathomas @ahinzmann (as mmarionncern original developer left the field)
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.
perhaps it's a more general XPOG question (as it was initially introduced via XPOG): do we still need to support the muon reco duplicate mitigation?
If not, it could be dropped.