-
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
Phase2-hgx360I Change names from 2026 to Run4 in several scripts of Geometry (CaloTopology|ForwardCommonData|GEMGeometry|MTDCommonData|MuonNumbering|TrackerCommonData|TrackerGeometryBuilder) #46648
Conversation
…pology|ForwardCommonData|GEMGeometry|MTDCommonData|MuonNumbering|TrackerCommonData|TrackerGeometryBuilder)
cms-bot internal usage |
@cmsbuild Please test |
+code-checks Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-46648/42565 |
A new Pull Request was created by @bsunanda for master. It involves the following packages:
@Dr15Jones, @Moanwar, @bsunanda, @civanch, @kpedro88, @makortel, @mdhildreth, @srimanob, @subirsarkar can you please review it and eventually sign? Thanks. cms-bot commands are listed here |
+1 Size: This PR adds an extra 28KB to repository Comparison SummarySummary:
|
+geometry |
Hi @bsunanda |
+code-checks Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-46648/42584 |
Pull request #46648 was updated. @Dr15Jones, @Moanwar, @bsunanda, @civanch, @cmsbuild, @kpedro88, @makortel, @mdhildreth, @srimanob, @subirsarkar can you please check and sign again. |
Hi Phat, I plan to update directory names from 2026 to 2030 for all phase 2 geometries. This will modify all Run4 scenarios. I shall do this once this batch of scenario names are completed. I believe Geometr/SimG4Core/SimG4CMS is now all done. I just added one more PR
…________________________________
From: Phat Srimanobhas ***@***.***>
Sent: 11 November 2024 20:14
To: cms-sw/cmssw ***@***.***>
Cc: Sunanda Banerjee ***@***.***>; Mention ***@***.***>
Subject: Re: [cms-sw/cmssw] Phase2-hgx360I Change names from 2026 to Run4 in several scripts of Geometry (CaloTopology|ForwardCommonData|GEMGeometry|MTDCommonData|MuonNumbering|TrackerCommonData|TrackerGeometryBuilder) (PR #46648)
Hi @bsunanda<https://github.com/bsunanda>
Thanks for the PR. Do you have PRs to come on updating name, on configuration and filenames? So I can recheck again after this PR is merged. For geometry XMLs and folders under Geometry, I will not touch.
—
Reply to this email directly, view it on GitHub<#46648 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/ABGMZOS3CUMI55LRCIB7UUL2AC7GFAVCNFSM6AAAAABRRLI2Q6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDINRYGM2DMNZUGU>.
You are receiving this because you were mentioned.Message ID: ***@***.***>
|
@cmsbuild Please test |
@bsunanda , @srimanob , do I understand correctly that the schema will be following: most python scripts will have "Run4" inside instead of year. Some geometry directories will migrate to 2026 -> 2030. In past, having files corresponding to years was useful but knowing in advance what year will run4 start/changed/ likely impossible. Should we still use year or we can everywhere migrate to "Run4"? |
I believe you have to start with Run4. If geometry changes from year to year, which happened during Run2 and Run3, you may have to give the year name instead of Run4 for the declaration of a scenario. Only time will tell
…________________________________
From: Vladimir Ivantchenko ***@***.***>
Sent: 11 November 2024 22:07
To: cms-sw/cmssw ***@***.***>
Cc: Sunanda Banerjee ***@***.***>; Mention ***@***.***>
Subject: Re: [cms-sw/cmssw] Phase2-hgx360I Change names from 2026 to Run4 in several scripts of Geometry (CaloTopology|ForwardCommonData|GEMGeometry|MTDCommonData|MuonNumbering|TrackerCommonData|TrackerGeometryBuilder) (PR #46648)
@bsunanda<https://github.com/bsunanda> , @srimanob<https://github.com/srimanob> , do I understand correctly that the schema will be following: most python scripts will have "Run4" inside instead of year. Some geometry directories will migrate to 2026 -> 2030. In past, having files corresponding to years was useful but knowing in advance what year will run4 start/changed/ likely impossible. Should we still use year or we can everywhere migrate to "Run4"?
—
Reply to this email directly, view it on GitHub<#46648 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/ABGMZOVHHIBOF7WXWNYFKI32ADMOBAVCNFSM6AAAAABRRLI2Q6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDINRYGU4TEOBXGQ>.
You are receiving this because you were mentioned.Message ID: ***@***.***>
|
I would propose we stay with Run4 as much as possible, and keep 2030 for specific things for that year, that we may need in near future. |
+1 Size: This PR adds an extra 16KB to repository Comparison SummarySummary:
|
+geometry |
@Moanwar, @srimanob, @subirsarkar Please approve this PR |
+Upgrade |
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. @sextonkennedy, @rappoccio, @mandrenguyen, @antoniovilela (and backports should be raised in the release meeting by the corresponding L2) |
+1 |
PR description:
Change names from 2026 to Run4 in several scripts of Geometry (CaloTopology|ForwardCommonData|GEMGeometry|MTDCommonData|MuonNumbering|TrackerCommonData|TrackerGeometryBuilder)
PR validation:
Tested the modified scripts
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