-
Notifications
You must be signed in to change notification settings - Fork 4.3k
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
guard against no L1T uGT digis in L1TriggerResultsConverter
#40528
Conversation
type bugfix |
+code-checks Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-40528/33739
|
A new Pull Request was created by @missirol (Marino Missiroli) for master. It involves the following packages:
@cmsbuild, @swertz, @vlimant can you please review it and eventually sign? Thanks. cms-bot commands are listed here |
please test |
+1 Summary: https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-d919dc/30005/summary.html Comparison SummaryThere are some workflows for which there are errors in the baseline: Summary:
|
@cms-sw/xpog-l2 Can you please review this PR? |
see comments above |
there are no comments, maybe you didnt hit 'finish review' |
const std::vector<bool>* wordp = nullptr; | ||
bool unprefireable_bit = false; | ||
if (!legacyL1_) { | ||
const auto& resultsProd = iEvent.get(token_); | ||
wordp = &resultsProd.at(0, 0).getAlgoDecisionFinal(); | ||
if (resultsProd.size() > 0) { |
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.
can it happened that resultsProd.size()
is non zero and resultsProd.size(0)
is ?
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.
Good point.. I don't know (maybe @cms-sw/l1-l2 knows?), and I had the same doubt.
I used size
to be consistent with
if (handleExtResults->size() != 0) { |
and similar cases seen elsewhere
if (uGtAlgoBlocks->size() == 0) { |
but now I also see cases where the
0
is explicitly usedif (not bxvector.isEmpty(0)) { |
I think the correct call is size(0)
(actually, isEmpty(0)
is sufficient and a bit cheaper), so I switched to that, for both resultsProd
and handleExtResults
.
33f7784
to
c3d66ef
Compare
+code-checks Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-40528/33812
|
please test |
+1 Summary: https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-d919dc/30085/summary.html Comparison SummarySummary:
|
@cms-sw/xpog-l2 Do you have other comments on this PR? |
+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. @perrotta, @dpiparo, @rappoccio (and backports should be raised in the release meeting by the corresponding L2) |
a backport might be required, although data taking will move on to 13.0 AFAIK |
The 12_6_X backport is in place, and tested, at #40588. |
+1 |
PR description:
This PR fixes the edge case reported in #40494. It adds a check on the size of the L1T uGT digis, returning
false
for all L1T algorithms when said input collection has0
elements for the relevant BX (see #40528 (comment) for details).PR validation:
Fixes the crash reproduced from the instructions in #40494 (tested in
13_0_X
):If this PR is a backport, please specify the original PR and why you need to backport that PR. If this PR will be backported, please specify to which release cycle the backport is meant for:
TBD