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
Further preparations of deep tau ID for hlt phase2 #32676
Further preparations of deep tau ID for hlt phase2 #32676
Conversation
+code-checks Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-32676/20773
|
A new Pull Request was created by @swozniewski for master. It involves the following packages: RecoTauTag/RecoTau @perrotta, @jpata, @cmsbuild, @slava77 can you please review it and eventually sign? Thanks. cms-bot commands are listed here |
@@ -415,6 +423,22 @@ namespace { | |||
} | |||
} // namespace dnn_inputs_2017_v2 | |||
|
|||
float getTauID(const pat::Tau& tau, const std::string& tauID, float default_value = -999.) { | |||
std::lock_guard<std::mutex> guard(g_mutex); |
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.
guard
can be placed insideelse
section to not block execution for the cases when tau id is available.- mutex can be defined as static inside
getTauID
instead of using the global namespace
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!
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.
A better solution would be to use something like tbb::concurrent_unordered_set<std::string>
for isFirstWarning
, and check with something like
if (isFirstWarning.insert(tauID).second) {
edm::LogWarning("TauID") << ...
}
which doesn't require any explicit locks.
+code-checks Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-32676/20775
|
@cmsbuild please test |
+1 Summary: https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-0b3e31/12320/summary.html Comparison SummarySummary:
|
-code-checks Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-32676/20787
Code check has found code style and quality issues which could be resolved by applying following patch(s)
|
apparently I was a bit naive about what small changes require different formatting. To be fixed shortly... |
+code-checks Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-32676/21025
|
@cmsbuild please test |
+1 Summary: https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-0b3e31/12734/summary.html Comparison SummarySummary:
|
The quantities where the seven differences show up are not known to me and do not seem to be tau related. Please let me know if you think that these differences are in fact due to the latest commit. |
+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, @qliphy (and backports should be raised in the release meeting by the corresponding L2) |
+1 |
PR description:
Modifications of the DeepTauID code for phase II tau trigger studies:
disable_CellIndex_workaround
,disable_hcalFraction_workaround
to turn off workarounds which won't be needed in the future.enableHGCalWorkaround
to PFRecoTauDiscriminationByIsolation serving as input to DeepTauID to enable a workaround needed for phase II.Clean up of defaults in DeepTauID functions introduced during last preparation of phase II trigger studies (PR #31744 ):
Modifications/defaults preserve the current DeepTauID for PAT level and no physics changes are intended there.
DeepTauID on AOD as introduced recently in PR #31744 is developing and changes are intended.
PR validation: