-
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
extended existing HLT tau-jet correlation module #40993
extended existing HLT tau-jet correlation module #40993
Conversation
-code-checks Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-40993/34502
Code check has found code style and quality issues which could be resolved by applying following patch(s)
|
+code-checks Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-40993/34504
|
A new Pull Request was created by @brallmond (Braden Allmond) for master. It involves the following packages:
@cmsbuild, @missirol, @Martin-Grunewald can you please review it and eventually sign? Thanks. cms-bot commands are listed here |
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 update of the filter doesn't fit very well with the name of the plugin ("*WithDiTau"). One option is to add a copy of this plugin with a more suitable name (and we keep the current one in 13_1_X and 13_0_X for backward compatibility). This could be done by just doing
DEFINE_FWK_MODULE(HLTPFDiJetCorrCheckerWithDiTau);
using HLTDiPFJetPlusTauFilter = HLTPFDiJetCorrCheckerWithTaus;
DEFINE_FWK_MODULE(HLTDiPFJetPlusTausFilter);
Eventually (e.g. 13_2_X), the old plugin would be removed (and replaced at HLT by the new one). Thoughts?
the same metrics were also computed for the VBF DiTau path with the module extension in place and no differences were found in past and current behavior of the path.
As far as I understand, this is because that single use case in the current HLT is preceded by a filter requiring the input taus are at least 2. In general, this update changes the behaviour of the filter. Is that correct?
Yes, I agree that's a good way to change the filter name in the future and proceed with the change. The code has been added. I think "HLTPFDiJetCorrCheckerWithTaus" above should have been "HLTPFDiJetCorrCheckerWithDiTau" so I changed it in the new commit |
-code-checks Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-40993/34507
Code check has found code style and quality issues which could be resolved by applying following patch(s)
|
Right, sorry for the confusion. |
+code-checks Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-40993/34508
|
+1 Summary: https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-6880f2/31147/summary.html Comparison SummarySummary:
|
+code-checks Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-40993/34528
|
Pull request #40993 was updated. @cmsbuild, @missirol, @Martin-Grunewald can you please check and sign again. |
please test (Didn't squash in 1 commit, but having 3 commits is not a problem, imho.) |
+1 Summary: https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-6880f2/31161/summary.html Comparison SummarySummary:
|
+hlt
|
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. @perrotta, @dpiparo, @rappoccio (and backports should be raised in the release meeting by the corresponding L2) |
+1 |
PR description:
To support a future VBF Single Tau HLT in the scenario that VBF Parking is accepted (see JIRA https://its.cern.ch/jira/browse/CMSLITDPG-1099 and https://its.cern.ch/jira/browse/CMSHLT-2702), a small change to an existing HLT module is necessary. The change extends the module's usage from only handling 2 Jet + 2 Tau events to also handling 2 Jet + 1 Tau events. This change depends on no other PRs and affects code used by one existing HLT path, and would allow the implementation of a future HLT path.
PR validation:
In the course of estimating rate and gain for the proposed VBF Single Tau path, the same metrics were also computed for the VBF DiTau path with the module extension in place and no differences were found in past and current behavior of the path.