-
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
Drop of D49-D85 Phase-2 geometry #38594
Comments
A new Issue was created by @srimanob Phat Srimanobhas. @Dr15Jones, @perrotta, @dpiparo, @makortel, @smuzaffar, @qliphy can you please review it and eventually sign/assign? Thanks. cms-bot commands are listed here |
assign upgrade |
New categories assigned: upgrade @AdrianoDee,@srimanob you have been requested to review this Pull request/Issue and eventually sign? Thanks |
FYI @cms-sw/simulation-l2 @cms-sw/hgcal-dpg-l2 |
|
from the MTD point of view keeping just scenario I15 is ok, this will allow us to drop support in the code for obsolete scenarios (like single disc ring-shaped ETL in D49), simplifying the structure. Some initial cleaning is already proposed for BTL in #38589 (not needing this proposal), in preparation of a new BTL geometry (and MTD scenario) to be added in the coming weeks/months. |
I've made a draft PR, so ppl can check: |
@srimanob what do you think about resetting the workflow numbers? |
Hi @kpedro88 Currently, the first upgrade workflow after cleaning will be |
Yes; in particular, you should change this line as follows: |
OK. That line I updated already in the PR, but just to reflect the drop of workflows. I will update again. |
Hello. The L1T team would like to ask if the D49 could be kept. It can be useful for validation studies on the HLT-TDR samples (that we are using for L1T developments since a year). And I think HLT Upgrade would echo this. |
@cbotta Do you have an idea on how long will you need it? Could you please provide more information on the schedule of development? The current plan is to drop by the next release series, i.e. 12_6 at the end of August. |
@srimanob After discussing with the team: we will very likely have our new MC production in 12_5. We think it is useful to keep the D49 up to this release, so that we have one release that can run on both MC productions. But after that we will switch to the new samples, and so it is fine to remove it from 12_6. Thanks! |
@cbotta |
Hi. My understanding is that L1T is still targeting 12_5_0 for the MC production, therefore my previous comment still holds. @cecilecaillol |
Hi @cbotta |
If possible I would wait for @cecilecaillol to confirm that all what we need can be ported to 12_5, and we can start the production there. Should be happening soon |
@cbotta @cecilecaillol @cms-sw/l1-l2 From your plan, it should be OK as all L1T code will be backported to 12_5, so 12_5 will be the release which support both D49 and D88. If there is an objection, please raise it here before the next release meeting (27 Sep). Thanks for understanding. |
We should have a 12_5_1 release for our MC production so this is fine from our side |
Unit test failures after merging cleaning PR:
They call D49 or D76. This should be updated to D88 or later. FYI @cms-sw/geometry-l2 @cms-sw/trk-dpg-l2 |
Please use D92 (or the later version with new Tracker and MTD) and not D88.
…________________________________
From: Phat Srimanobhas ***@***.***
Sent: 29 September 2022 09:30
To: cms-sw/cmssw
Cc: Sunanda Banerjee; Mention
Subject: Re: [cms-sw/cmssw] Drop of D49-D85 Phase-2 geometry (Issue #38594)
Unit test failures after merging cleaning PR:
* Validation/Geometry/test/runP_HGCal_cfg.py
* Geometry/TrackerGeometryBuilder/test/python/testPixelTopologyMapTest_cfg.py
* SimTracker/TrackerMaterialAnalysis/test/trackingMaterialProducer10GeVNeutrino_ForPhaseII.py
* SLHCUpgradeSimulations/Geometry/test/writeFile_phase2_cfg.py
* CondTools/SiPixel/test/SiPixelTemplateDBObjectUploader_Phase2_cfg.py
They call D49 or D76. This should be updated to D88 or later.
FYI @cms-sw/geometry-l2<https://github.com/orgs/cms-sw/teams/geometry-l2> @cms-sw/trk-dpg-l2<https://github.com/orgs/cms-sw/teams/trk-dpg-l2>
—
Reply to this email directly, view it on GitHub<#38594 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/ABGMZOQQKLZA5KOVNKDQVNTWAVAQZANCNFSM52UCJQSQ>.
You are receiving this because you were mentioned.Message ID: ***@***.***>
|
@srimanob I suppose you can also clean up the T* versioned autoCond Global Tags for the Tracker geometries that have been removed? cmssw/Configuration/AlCa/python/autoCondPhase2.py Lines 110 to 119 in 4e89b5b
@cms-sw/alca-l2 |
Hi @mmusich @cms-sw/alca-l2 |
I see a couple of problems:
Footnotes
|
Let's go for D88 in unit tests until we validate D92 and move it to baseline, and have everything ready. |
PR #39535 should take care of these:
as for the others:
I would let it to HGCAL experts (FYI @cms-sw/hgcal-dpg-l2 ) while
requires more involved changes, including an update of the cms-data externals, that I would leave to the Pixel CPE experts (@tvami @SanjanaSekhar) |
Sure I'll have a look |
changing topic, shouldn't be https://github.com/cms-sw/cmssw/blob/master/Configuration/Geometry/README.md also updated to remove the unsupported geometries? |
Thx. I think i forgot it whilt waiting the PR to converge. I will update it together with workflow id resetting. |
|
Staring from CMSSW_12_6_X_2022-10-05-1100, unit tests seem to be OK now. |
Done. |
Following the HGCAL proposal in
https://docs.google.com/document/d/1fCIpJJQLw0vGCKyR9LRmFmWVcAQZOlHk5jK-ESQLJnQ/edit?usp=sharing,
they propose to preserve only V16 and V17 of HGCAL (== C17-C19).
So the affected geometries include
This issue is to collect feedback, or need if other version of geometry should be preserved.
The plan is to implement this proposal when the next release series start, i.e. 12_6_X.
The text was updated successfully, but these errors were encountered: