-
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
Update GEM reco geometry for Run3 MC GTs #36860
Update GEM reco geometry for Run3 MC GTs #36860
Conversation
test parameters:
|
+code-checks Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-36860/28102
|
A new Pull Request was created by @francescobrivio for master. It involves the following packages:
@cmsbuild, @malbouis, @tvami, @yuanchao, @francescobrivio can you please review it and eventually sign? Thanks. cms-bot commands are listed here |
@cms-sw/geometry-l2 @cms-sw/orp-l2 @srimanob this is the PR with updated GTs. |
@cmsbuild please test @francescobrivio |
|
@cmsbuild please abort |
test parameters:
|
@cmsbuild please test Thanks @francescobrivio for reminding since the PR just merged 2 hour ago. |
+1 Summary: https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-8a2cef/22147/summary.html Comparison SummaryThe workflows 1001.0, 1000.0, 136.88811, 136.874, 136.8311, 136.793, 136.7611, 136.731, 4.22 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 @slava77 comparisons for the following workflows were not done due to missing matrix map:
Summary:
|
+alca
|
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) |
In the step3 of the wfs affected by this geometry update, the following warning message systematically shows up:
This is probably something @cms-sw/dqm-l2 should be also made aware of, in ordeer to setup a possible fix |
@hyunyong @sgrzegorz @quark2 @seungjin-yang |
Hi @jfernan2, the above warning is due to offline DQM not handling the new GEM geometry properly. We're aware of the issue and I will fix it. Thank you for reminding me about this issue. |
Thank you @seungjin-yang @francescobrivio I understand that the fix above will go in a different PR: I would wait for that PR being (at least) ready before merging this PR, unless the time needed for it would unacceptably delay this (and in particular the backport) PR. Please advise if you have a different opinion about it. |
@perrotta For me it's fine if it's a matter of waiting 1 or 2 days: I'm thinking especially at the backport and the need to cut (and properly test) a new 12_2 release in time for the Feb MWGR (in ~2 weeks). |
@francescobrivio for the MWGR CMSSW_12_2_0_patch1 could also be used (it only misses #36866, but as far as I understand we could temporarily survive even without it, at worst). |
True for MWGR we can probably survive with CMSSW_12_2_0_patch1.
It was not deployed for production but used in two replays (both successful btw):
|
@perrotta since the DQM PR is somewhat independent of this one, can we just merge this PR? We have another update coming in here https://cms-talk.web.cern.ch/t/gt-mc-update-to-csc-bad-chambers-for-run-3-simulation/5617/2 (that is independent of the geometry changes) |
Or @qliphy |
@tvami Unfortunately I am on vacation for the lunar new year until the weekend. I think probably GEM developers should address (@hyunyong @sgrzegorz @quark2 @seungjin-yang) or at least reply to the above comments: |
+1
|
Thank you @seungjin-yang ! |
PR description:
This PR updates the GEM reco geometry in Run3 MC GTs.
More details are available in
The updated DD4HEP tag is:
GEMRECO_Geometry_123DD4hepV2
At the same time the following DDD tag is updated as well in the
autoCondDDD
:GEMRECO_Geometry_123YV2
The difference in the GTs is:
2021 design
https://cms-conddb.cern.ch/cmsDbBrowser/diff/Prod/gts/123X_mcRun3_2021_design_v4/123X_mcRun3_2021_design_v5
2021 realistic
https://cms-conddb.cern.ch/cmsDbBrowser/diff/Prod/gts/123X_mcRun3_2021_realistic_v4/123X_mcRun3_2021_realistic_v5
2021 cosmics
https://cms-conddb.cern.ch/cmsDbBrowser/diff/Prod/gts/123X_mcRun3_2021cosmics_realistic_deco_v4/123X_mcRun3_2021cosmics_realistic_deco_v5
2021 heavy ion
https://cms-conddb.cern.ch/cmsDbBrowser/diff/Prod/gts/123X_mcRun3_2021_realistic_HI_v4/123X_mcRun3_2021_realistic_HI_v5
2023 realistic
https://cms-conddb.cern.ch/cmsDbBrowser/diff/Prod/gts/123X_mcRun3_2023_realistic_v4/123X_mcRun3_2023_realistic_v5
2024 realistic
https://cms-conddb.cern.ch/cmsDbBrowser/diff/Prod/gts/123X_mcRun3_2024_realistic_v4/123X_mcRun3_2024_realistic_v5
PR validation:
Validated with:
runTheMatrix.py -l 12034.0,11634.0,7.23,312.0,12434.0,12834.0,11634.911,11634.914 --ibeos -j 15
Backport:
This is not a backport but will be backported in #36785
resolves #36826