-
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
Revision of tau quality cut configuration #30364
Revision of tau quality cut configuration #30364
Conversation
…lt disabled by setting its value to -1.0) - declare all configuration parameters related to RecoTauQualityCuts class in RecoTauQualityCuts.cc - removed obsolete global functions for applying quality cuts from RecoTauQualityCuts.cc
…o RecoTauQualityCuts class
…uested by Sebastian
The code-checks are being triggered in jenkins. |
A new Pull Request was created by @swozniewski for master. It involves the following packages: RecoTauTag/RecoTau @perrotta, @cmsbuild, @slava77 can you please review it and eventually sign? Thanks. cms-bot commands are listed here |
@cmsbuild please test |
The tests are being triggered in jenkins.
|
+1 |
Comparison job queued. |
Comparison is ready Comparison Summary:
|
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 actions are required for this PR.
However, the updates reveal some redundancy/duplication in the way how the configurations are made/used.
to which extent are the files created by fillDescriptions and modified in this PR actually used?
From a cursory check I see that some are used and some are not
- pfTauPrimaryVertexProducer_cfi is not used
- pfRecoTauChargedHadronProducer_cfi is used
Some cleanup/refactoring should be added to directly use the config files generated by the fillDescriptions.
@@ -10,6 +10,7 @@ | |||
maxTrackChi2 = cms.double(100.), # require track Chi2 |
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 file better be populated from a reference file created by fillDescriptions.
The dual support of the content here and in fillDescriptions is not very practical.
+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 now be reviewed by the release team before it's merged. @silviodonato, @dpiparo (and backports should be raised in the release meeting by the corresponding L2) |
I agree. We started a discussion internally how we want to include the autogenerated cfi files but did not want to delay this update. We have in mind (in addition to using only the auto-generated cfi-files of the producers) to make PFRecoTauQualityCuts create its own auto-generated cfi file (as you suggest above), where central modifications like for phase 2 can be applied and which is then shared between the producers like the current cfi for quality cuts. |
Some care may be needed here. |
@@ -91,6 +92,9 @@ namespace reco { | |||
return output; | |||
} | |||
|
|||
/// Declare all parameters read from python config file | |||
static void fillDescriptions(edm::ParameterSetDescription& descriptions); |
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'd suggest to rename this function to
static void fillDescriptions(edm::ParameterSetDescription& descriptions); | |
static void fillPSetDescription(edm::ParameterSetDescription& descriptions); |
to follow a convention used elsewhere (including the helper plugins). The suggested name also signifies that the function fills a description for one PSet instead of arbitrary number of modules.
I don't really have much to add. When a helper class (needing configuration) are used directly by many modules, and if it is expected that helper to configured consistently between the modules, any customization on the configuration of the helper needs to be repeated. The repetition can be avoided by moving the helper algorithm to ED/ES product, in which case the configuration of the ED/ESProducer can be customized in a single place. The established practice is that if the helper needs event data, a new helper object should be produced on each event. If the helper does not need data from any of event, lumi, or run, it would be placed in EventSetup. In principle soon (after #30117 gets merged), a helper that depends only on configuration could be produced in beginProcessBlock transition. |
+1 |
PR description:
Adds parameter maxDeltaZToLeadTrack to the tau quality cut descriptions. While technically usable by producers, this parameter was not used in the past and not represented in the fillDescriptions. In recent trigger studies, it is needed.
Furthermore, the part of fillDescriptions that refers to the qualityCuts and was present in several producers is moved to the RecoTauQualityCuts class and now imported and shared by the producers.
Some deprecated helper functions are removed from the RecoTauQualityCuts class.
This is only a technical change and no changes to physics results are expected.
PR validation: