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
Updated PR for CorrWithOverlapRemovalCondition.cc #36758
Updated PR for CorrWithOverlapRemovalCondition.cc #36758
Conversation
+code-checks Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-36758/27881
|
A new Pull Request was created by @namppl (Kyungwook Nam) for master. It involves the following packages:
@epalencia, @cmsbuild, @cecilecaillol, @rekovic can you please review it and eventually sign? Thanks. cms-bot commands are listed here |
please test |
This PR is the change of logic from the one meant by OverlapRemoval. In the logic of this PR there is no OverlapRemoval but rather a condition of three objects with correlation conditions imposed on pairs of two. No L1T object is removed !! The logic of this PR is what I implemented in the new class CorrThreeBodyByTwoBodyCondition #36441 which was resently reverted and which I am now fixing. Development of the logic of this PR needs to continue on that class and not touch the CorrWithOverlapRemovalCondition which does something very different, removes overlapping objects at L1T, many of them, to reduce the fake rate. Both emulators need to be made available in the GlobalTrigger emulation and part of the CMSSW release for physics (May), This PR destroys and hijacks the ongoing developments of OverlapRemoval which tries to improve the GlobalTrigger by ridding the overlaps. Since the proponents of the new condition did not bother developing the emulator for their proposals, I am making one for them!! The hope is to have the GlobalTrigger emulator fully supporting this logic in the ThreeByTwoBodyCorrelation and the one of true OverlapRemoval next week. |
-1 Failed Tests: RelVals-INPUT RelVals-INPUT
Comparison SummarySummary:
|
please test |
+l1 |
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. @perrotta, @dpiparo, @qliphy (and backports should be raised in the release meeting by the corresponding L2) |
-1 Failed Tests: RelVals-INPUT RelVals-INPUT
Comparison SummarySummary:
|
@cecilecaillol I don't think that @rekovic agrees with the content of this PR, see #36758 (comment) I'll keep this PR on hold while waiting for such additional information |
hold |
Pull request has been put on hold by @perrotta |
@perrotta Merging this PR is supported by L1 DPG conveners and L1 project managers |
@perrotta I confirm that the strategy of this PR is blessed by L1 DPG. We would need it to be merged as soon as possible for seed developments that need to make it in 12_3. Thanks ! |
unhold |
This pull request is fully signed and it will be integrated in one of the next master IBs (but tests are reportedly failing). This pull request will now be reviewed by the release team before it's merged. @perrotta, @dpiparo, @qliphy (and backports should be raised in the release meeting by the corresponding L2) |
+1
|
merge |
PR description:
Update of #36103. Rebased to the latest commit.
PR validation:
Unit tests done