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
L1T: add HPS taus #33681
L1T: add HPS taus #33681
Conversation
-code-checks Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-33681/22584
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-33681/22586 ERROR: Build errors found during clang-tidy run.
|
+code-checks Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-33681/22587
|
A new Pull Request was created by @cecilecaillol for master. It involves the following packages: DataFormats/L1TParticleFlow The following packages do not have a category, yet: L1Trigger/Phase2L1Taus @cmsbuild, @rekovic, @srimanob, @cecilecaillol, @kpedro88 can you please review it and eventually sign? Thanks. cms-bot commands are listed here |
please test |
+code-checks Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-33681/22647
|
please test |
+l1 |
Hi @sandeepbhowmik1 |
We noticed that although we had added calojet in the code and it was running fine but there was no contribution from jet seeding. Then we found that the daughter information of caloJet is giving zero always. After that we made workaround of that and saw the contribution due to jet seeding is almost negligible. It increases only 1 GeV threshold (21 to 22 GeV) for Tight working point we used for HLT study and almost no effect in efficiency turn-on We have attached that plot in presentation of HLT Upgrade meeting you can have a look it here https://indico.cern.ch/event/1030865/ Slode 22 |
+Upgrade It will be much better if the PR description mentions what is in it, and what to expect (change, adding something, technical). Since we don't have DQM for Phase-2 L1T and no description, it seems to be blind approval on Physics content. It will be difficult to track when we have an issue. |
This pull request is fully signed and it will be integrated in one of the next master IBs after it passes the integration tests. 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 Summary: https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-638d81/15059/summary.html Comparison SummaryThe workflows 140.53 have different files in step1_dasquery.log than the ones found in the baseline. You may want to check and retrigger the tests if necessary. You can check it in the "files" directory in the results of the comparisons Summary:
|
It will be much better if the PR description mentions what is in it, and
what to expect (change, adding something, technical). Since we don't have
DQM for Phase-2 L1T and no description, it seems to be blind approval on
Physics content. It will be difficult to track when we have an issue.
In this case I disagree, unless you consider the results of the HLT TDR as
"blind approval".
… |
Hi Andrea, |
OK.
But what I meant is that the physics changes introduced by this PR are part
of the HLT TDR results.
|
merge |
@cecilecaillol I've added in the PR description a link to #33681 (comment) that point to the expected physics results. |
PR description:
Implement HPS taus at L1T.
See #33681 (comment).
PR validation:
Rebase of cms-l1t-offline#911
if this PR is a backport please specify the original PR and why you need to backport that PR:
Rebase of cms-l1t-offline#911