-
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
drop type spec in CommonTools #32464
Conversation
+code-checks Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-32464/20371
|
A new Pull Request was created by @jeongeun (JeongEun Lee) for master. It involves the following packages: CommonTools/ParticleFlow @perrotta, @jpata, @cmsbuild, @santocch, @slava77 can you please review it and eventually sign? Thanks. cms-bot commands are listed here |
please test |
pfTausSelectionDiscriminator = hpsSelectionDiscriminator.clone( | ||
PFTauProducer = "pfTausCombiner" | ||
) | ||
pfTausProducerSansRefs = hpsPFTauProducerSansRefs.clone( |
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.
This is a duplicate of the explicit configuration three lines below (a duplicate that was already present in the original config).
The two configurations look different, the explicit one being probably the correct one: which is the one picked up by python?
@mbluj @swozniewski please check and suggest which one of the two instances of pfTausProducerSansRefs
to remove (or suggest otherwise, in case I misunderstood the usage of this duplication)
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.
In our understanding python takes most recent definition of an object, so here it is the explicit one.
The explicit definition indeed differs a bit from the first one which is a clone of Tau POG default (modulo different input). We guess that it was an intended choice to define it differently, so we suggest to keep only the explicit one. However, maybe owners of this configuration should bless the choice if it is possible to identify them (*)?
Technical suggestion: it could be nicer to have a clone definition with settings as the present in the explicit one? It can either use default Tau POG configuration to clone or one from default cfi (RecoTauTag.RecoTau.recoTauCleaner_cfi
) It will look more or less like this:
pfTausProducerSansRefs = hpsPFTauProducerSansRefs.clone(
src = "pfTausCombiner",
outputSelection = "",
verbosity = 0,
cleaners = [
cleaners.unitCharge,
cms.PSet(
name = cms.string("leadStripPtLt2_5"),
plugin = cms.string("RecoTauStringCleanerPlugin"),
tolerance = cleaners.tolerance_default,
selection = cms.string("signalPiZeroCandidates().size() = 0 | signalPiZeroCandidates()[0].pt > 2.5"),
selectionPassFunction = cms.string("0"),
selectionFailValue = cms.double(1e3)
),
cms.PSet(
name = cms.string("HPS_Select"),
plugin = cms.string("RecoTauDiscriminantCleanerPlugin"),
tolerance = cleaners.tolerance_default,
src = cms.InputTag("pfTausSelectionDiscriminator"),
),
cleaners.combinedIsolation
]
)
(*) Is this config a part of PF2PAT? So, it is owned by PFlow or XPOG?
please test |
+code-checks Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-32464/20386
|
+1 Summary: https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-49b471/11624/summary.html Comparison SummarySummary:
|
+1
|
merge |
+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 the safer syntax for existing parameter :
Instead of modifying parameters with full type specs, which can be interpreted as an insertion of a new parameter, it is a safer way to protect from parameter name mistakes and will also help in possible parameter migrations.
(The previous PR for RecoHI is PR#32031, PR#32386, PR#32396)
In this PR, a total of 11 files changed.
CommonTools/ParticleFlow : 7 files
CommonTools/PileupAlgos : 1 file
CommonTools/RecoAlgos : 1 file
CommonTools/RecoUtils : 2 files
PR validation:
Event Content comparison check was also done and there is no change with these updates.
Tested in CMSSW_11_2_X, the basic test all passed in the CMSSW PR instructions.