-
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
[14.0.X] MultiTrajectoryStateAssembler
: protect removeWrongPz
when average pZ sign is identically 0
#45647
[14.0.X] MultiTrajectoryStateAssembler
: protect removeWrongPz
when average pZ sign is identically 0
#45647
Conversation
when average pZ sign is identically 0.
A new Pull Request was created by @mmusich for CMSSW_14_0_X. It involves the following packages:
@cmsbuild, @jfernan2, @mandrenguyen can you please review it and eventually sign? Thanks. cms-bot commands are listed here |
cms-bot internal usage |
@cmsbuild, please test |
+1 Size: This PR adds an extra 16KB to repository Comparison SummarySummary:
|
+reconstruction |
This pull request is fully signed and it will be integrated in one of the next CMSSW_14_0_X IBs (tests are also fine) and once validation in the development release cycle CMSSW_14_1_X is complete. This pull request will now be reviewed by the release team before it's merged. @sextonkennedy, @mandrenguyen, @antoniovilela, @rappoccio (and backports should be raised in the release meeting by the corresponding L2) |
+1 |
backport of #45646
PR description:
This PR is meant as a fix for the situation that occurred in online HLT operations and lead to #45639.
As explained in detailed #45639 (comment), in this event, some states have positive pz-sign, and some states have negative pz-sign, which is a problem.
The chain of calls is the following:
GsfMultiStateUpdator
callsMultiTrajectoryStateAssembler::combinedState()
, which in turn callsMultiTrajectoryStateAssembler::prepareCombinedState()
. At this stage, the algo tries to fix the problem by callingremoveWrongPz()
. In most casesremoveWrongPz
will solve the issue.In one special case , where
meanPz=0
, it will not be able to solve the issue and it will let the charged-flipped states pass which will create the crash later on, where there is another check of pz-sign.This PR circumvents the issue by explicitly logging an error when this happens, clear the states vector and then do an early return.
PR validation:
Tested in
CMSSW_14_0_13_MULTIARCH
+ this commit mmusich@24d4fd2 with the reproducer at #45639 (comment):and observed no crash.
N.B.
It's worth noting that the crash doesn't appear to start with in
CMSSW_14_0_13
(tout-cout) , so it looks like theMULTIARCHS
variant (hencex86-64-v3
micro-architecture) is triggering the problem in the first place, see #45639 (comment).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:
Verbatim backport of #45646 for 2024 online HLT data-taking puroposes.