-
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
Run3-gex160Z Remove overlaps in the ZDC part and apply the correction to all Run3 scenarios #41464
Conversation
@cmsbuild Please test |
@civanch Should one make payloads for 2021/2023 geometries? |
+code-checks Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-41464/35328
|
A new Pull Request was created by @bsunanda (Sunanda Banerjee) for master. It involves the following packages:
@civanch, @Dr15Jones, @bsunanda, @makortel, @mdhildreth, @AdrianoDee, @srimanob can you please review it and eventually sign? Thanks. cms-bot commands are listed here |
+1 Summary: https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-771a66/32247/summary.html Comparison SummarySummary:
|
+1 |
@bsunanda , all, I think this should be backported to 13_0_X. I am not sure about 12_4_X. |
@cmsbuild please test Re-trigger the test after a week. |
@bsunanda perhaps a backport to 13_1_X could be in order, just in case that release will be used for some reprocessing of this year data later in summer |
Does this PR effect only simulation geometry, or also reconstruction geometry? |
Data uses the whole detector as it is and MC uses some geometry for simulation. The MC production makes use of geometry in payload and the changes will affect only the SIM step. I do not see your reasoning.
…________________________________
From: Phat Srimanobhas ***@***.***>
Sent: 06 May 2023 10:43
To: cms-sw/cmssw ***@***.***>
Cc: Sunanda Banerjee ***@***.***>; Mention ***@***.***>
Subject: Re: [cms-sw/cmssw] Run3-gex160Z Remove overlaps in the ZDC part and apply the correction to all Run3 scenarios (PR #41464)
Hi @bsunanda<https://github.com/bsunanda> @perrotta<https://github.com/perrotta>
Maybe hold 13_0 for now (both coding and mc)? As if partial re-reco will be done, it will still be used with old MC. The update will make inconsistent between data and MC geometry.
—
Reply to this email directly, view it on GitHub<#41464 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/ABGMZOSVK6DFII6TSWUA5YDXEXMXTANCNFSM6AAAAAAXP5FMRA>.
You are receiving this because you were mentioned.Message ID: ***@***.***>
|
My comment based on your answer on reco geometry. If you update the gt and change also reco geometry, then it will not match on ppd plan to keep current mc with partial rereco. |
-1 Failed Tests: AddOn AddOn Tests
Comparison SummarySummary:
|
@cmsbuild Please test |
+1 Summary: https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-771a66/32448/summary.html Comparison SummarySummary:
|
+Upgrade I assume no change can be seen in the PR test, so big samples should be validated, i.e. relvals. |
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) |
+1 |
Run3-gex160Y Backport of #41464 to CMSSW version 13_1_X which contains a bug fix for ZDC simulation geometry
…and Phase2 (cms-sw#41480) to CMSSW version 13_0_X
…and Phase2 (cms-sw#41480) to CMSSW version 13_0_X
PR description:
Remove overlaps in the ZDC part and apply the correction to all Run3 scenarios
PR validation:
Use the overlap check tool in SimG4Core/PrintGeomInfo
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:
Should one make a new geometry payload for 2021 and 2023?