-
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
Move MSLayerKeeper* objects from thread-local into EventSetup #35269
Move MSLayerKeeper* objects from thread-local into EventSetup #35269
Conversation
+code-checks Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-35269/25261
|
A new Pull Request was created by @makortel (Matti Kortelainen) for master. It involves the following packages:
@Martin-Grunewald, @jpata, @cmsbuild, @slava77 can you please review it and eventually sign? Thanks. cms-bot commands are listed here |
@cmsbuild, please test |
// Using NavigationSchoolRecord here sounds a bit confusing, that | ||
// that depends only on TrackerRecoGeometryRecord and | ||
// IdealMagneticFieldRecord | ||
std::unique_ptr<MultipleScatteringParametrisationMaker> produce(const NavigationSchoolRecord& iRecord); |
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.
Note that I blatantly reused the NavigationSchoolRecord
for this ESProduct, as that record depends exactly on the two records (TrackerRecoGeometryRecord
and IdealMagneticFieldRecord
) needed for the MultipleScatteringParametrisation
). If that is considered too confusing, I can create a new record (or put it to some other existing record like CkfComponentsRecord
, but those may have smaller IOVs than the intersection of TrackerRecoGeometryRecord
and IdealMagneticFieldRecord
).
-1 Failed Tests: AddOn CMS StaticAnalyzer warnings: There are 10 EventSetupRecord::get warnings. See https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-c6a8f8/18601/llvm-analysis/esrget-sa.txt for details. AddOn Tests
Expand to see more addon errors ...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:
|
fa1e4e0
to
3f99a0d
Compare
@Martin-Grunewald I see the addOn tests that run HLT and RECO in the same job. Should I then use the same label for the ESProducer in both HLT and RECO so those jobs would have only one instance of it? I.e. in |
+code-checks Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-35269/25271
|
Pull request #35269 was updated. @Martin-Grunewald, @jpata, @cmsbuild, @slava77 can you please check and sign again. |
+code-checks Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-35269/25441
|
Pull request #35269 was updated. @malbouis, @yuanchao, @Martin-Grunewald, @missirol, @slava77, @jpata, @francescobrivio, @tvami can you please check and sign again. |
+1 Summary: https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-c6a8f8/18811/summary.html CMS StaticAnalyzer warnings: There are 10 EventSetupRecord::get warnings. See https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-c6a8f8/18811/llvm-analysis/esrget-sa.txt for details. Comparison SummarySummary:
|
+reconstruction
|
+alca
|
+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, @qliphy (and backports should be raised in the release meeting by the corresponding L2) |
@makortel I was having a look for HLT, and wanted to ask a clarification (maybe I'm missing something obvious). IIuc, in #35269 (comment) you mention that Maybe the HLT customisation is really needed, but not for that specific |
@missirol Looking closer, the step in A consequence of the HLT+RECO jobs in the addOnTests that I referred to in #35269 (comment) was the use of |
I see. All clear now. Thanks, Matti. |
+1 |
PR description:
This PR is part of #31061 and focuses on the
MultipleScatteringParametrisation
helper. That class relied an old hack to cache EventSetup datacmssw/RecoTracker/TkMSParametrization/src/MultipleScatteringParametrisation.cc
Lines 45 to 49 in 919a747
that this PR suggests to finally fix properly by moving the
MSLayersKeeperX0DetLayer
,MSLayersKeeperX0AtEta
, andMSLayersKeeperX0Averaged
from thread-locals into EventSetup itself. In the EventSetup they are abstracted intoMultipleScatteringParametrisationMaker
class that is then used to makeMultipleScatteringParametrisation
objects. The corresponding ESProducer is added into thecustomizeHLTforCMSSW.py
and in various cff fragments within reconstruction configuration (I can't exclude missing some places).This PR also completes the esConsumes migration for touched helper classes where that was feasible.
As in #35081, despite of being part of #31061 this PR adds some new calls to the deprecated
EventSetupRecord::get()
function withoutesConsumes()
. All these cases have some relation toTrackingRegion
classes, and will be addressed in a subsequent PR (I have the work done already, but I though they would be easier to review separately).Resolves cms-sw/framework-team#251
PR validation:
Tested on earlier IB (on top of #35081) that limited matrix runs. After rebase checked that the code compiles.