-
Notifications
You must be signed in to change notification settings - Fork 4.6k
Phase2-hgx364X Add the tools with some more diagnostic help to debug the issue of wrong DetID->Position->DetID assignment #49763
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
Conversation
…ong DetID->Position->DetID assignment
|
cms-bot internal usage |
|
-code-checks Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-49763/47353 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-49763/47354 |
|
A new Pull Request was created by @bsunanda for master. It involves the following packages:
@Dr15Jones, @bsunanda, @civanch, @cmsbuild, @kpedro88, @makortel, @mdhildreth can you please review it and eventually sign? Thanks. cms-bot commands are listed here |
|
@cmsbuild Please test |
|
@cmsbuild Please test |
|
-1 Failed Tests: RelVals Failed RelVals |
|
This error is not due to the changes of the PR. It needs investigation |
|
+geometry |
|
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. @mandrenguyen, @ftenchini, @sextonkennedy (and backports should be raised in the release meeting by the corresponding L2) |
|
The exception is coming from this line:
It's not clear to me why this is only popping up in this PR and not others. Would you expect a change in geometry could cause us to hit the error by accident? |
|
This PR is affecting the rebuilding of geometry which triggers this test. But the changes in this PR is addition of a few diagnostic messages which cannot cause the error. This error was reported earlier and needs investigation.
…________________________________
From: Matthew Nguyen ***@***.***>
Sent: 12 January 2026 13:37
To: cms-sw/cmssw ***@***.***>
Cc: Sunanda Banerjee ***@***.***>; Mention ***@***.***>
Subject: Re: [cms-sw/cmssw] Phase2-hgx364X Add the tools with some more diagnostic help to debug the issue of wrong DetID->Position->DetID assignment (PR #49763)
[https://avatars.githubusercontent.com/u/5022810?s=20&v=4]mandrenguyen left a comment (cms-sw/cmssw#49763)<#49763 (comment)>
The exception is coming from this line:
https://github.com/cms-sw/cmssw/blob/fc98c6521423acce9e64292eee60586ed64418b1/L1Trigger/L1THGCal/src/backend/HGCalHistoSeedingImpl.cc#L103
It's not clear to me why this is only popping up in this PR and not others. Would you expect a change in geometry could cause us to hit the error by accident?
—
Reply to this email directly, view it on GitHub<#49763 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/ABGMZOQJM2BGX77QJHQ4JTD4GNI4PAVCNFSM6AAAAACRKWCNVWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTOMZXGMYTSOBQGU>.
You are receiving this because you were mentioned.Message ID: ***@***.***>
|
Is #41451 back? |
|
Is the pileup file made with the same CMSSW version - I mean the IB + current PR?
…________________________________
From: Matti Kortelainen ***@***.***>
Sent: 12 January 2026 20:08
To: cms-sw/cmssw ***@***.***>
Cc: Sunanda Banerjee ***@***.***>; Mention ***@***.***>
Subject: Re: [cms-sw/cmssw] Phase2-hgx364X Add the tools with some more diagnostic help to debug the issue of wrong DetID->Position->DetID assignment (PR #49763)
[https://avatars.githubusercontent.com/u/33993?s=20&v=4]makortel left a comment (cms-sw/cmssw#49763)<#49763 (comment)>
The exception is coming from this line:
https://github.com/cms-sw/cmssw/blob/fc98c6521423acce9e64292eee60586ed64418b1/L1Trigger/L1THGCal/src/backend/HGCalHistoSeedingImpl.cc#L103
It's not clear to me why this is only popping up in this PR and not others. Would you expect a change in geometry could cause us to hit the error by accident?
Is #41451<#41451> back?
—
Reply to this email directly, view it on GitHub<#49763 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/ABGMZOTIF3GH4P7OUU2UVTD4GOWVRAVCNFSM6AAAAACRKWCNVWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTOMZYHA3DSOJUGA>.
You are receiving this because you were mentioned.Message ID: ***@***.***>
|
The premixed pileup file itself is done with the same CMSSW version, but MinBias files used as an input for the premixing are read from storage (I see from CMSSW_16_0_0_pre2). If that mismatch is the problem, then we just have to accept the failures until a new MinBias dataset is produced. (it would be great if someone would have time to craft another variant of the workflow that would generate the MinBias on the fly) |
Actually, these exist for alternative pileup options (premixing and hybrid), just not for classical mixing... @makortel could you open an issue for this? |
I can open an issue, but just to clarify, I was talking about premixing. While the X.999 does the premixing on the fly, it relies on existing MinBias files. |
I opened #49776 for the case I had in mind. I can extend the issue to classical mixing if you want (but maybe we should move that discussion to the issue) |
|
@makortel thanks for clarifying. Yes, I would include both in the same issue. |
|
+1 |
|
merge |
|
Some compilation errors were found in CMSSW_16_1_UBSAN_X IBs after this PR cmssw/Geometry/HGCalCommonData/interface/HGCalTypes.h Lines 168 to 173 in c828765
In file included from src/Geometry/HGCalCommonData/interface/HGCalDDDConstants.h:26,
from src/CondFormats/HGCalObjects/interface/HeterogeneousHGCalHEFCellPositionsConditions.h:11,
from src/CondFormats/HGCalObjects/src/T_EventSetup_HeterogeneousHGCalHEFCellPositionsConditions.cc:1:
src/Geometry/HGCalCommonData/interface/HGCalTypes.h:167:85: error: '(((const std::string*)(& HGCalTypes::layerTypes_)) != 0)' is not a constant expression
167 | "Center", "CenterB", "CenterYp", "CenterYm", "CenterR", "CenterXp", "CenterXm"};
| ^
src/Geometry/HGCalCommonData/interface/HGCalTypes.h:168:83: error: '(((const std::string*)(& HGCalTypes::waferType_)) != 0)' is not a constant expression
168 | static constexpr std::string waferType_[4] = {"HD120", "LD200", "LD300", "HD200"};
| ^
src/Geometry/HGCalCommonData/interface/HGCalTypes.h:172:108: error: '(((const std::string*)(& HGCalTypes::waferTypeX_)) != 0)' is not a constant expression
172 | "Unknown18", "Unknown19", "Unknown20", "HDTop", "HDBottom", "HDLeft", "HDRight", "HDFive", "Out"}; |
On the contrary, I think this PR is the primary cause of the recent turbulence in IBs. |
PR description:
Add the tools with some more diagnostic help to debug the issue of wrong DetID->Position->DetID assignment
PR validation:
Tested for the diagnostic
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:
Nothing special