-
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
Clean up Phase2 workflows #27449
Merged
Merged
Clean up Phase2 workflows #27449
Changes from all commits
Commits
Show all changes
6 commits
Select commit
Hold shift + click to select a range
3da726e
deprecate outdated phase 2 geometries, add 2 new ones to keep alive c…
kpedro88 72c1b09
make it simpler to add new WFs
kpedro88 aba2c02
add missing era
kpedro88 d5b10c8
simplify
kpedro88 30f72d4
default dataset for D41
kpedro88 9a2a405
use updated I10 for new D45 geometry
kpedro88 File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
8 changes: 8 additions & 0 deletions
8
Configuration/Eras/python/Era_Phase2C6_timing_layer_bar_cff.py
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,8 @@ | ||
import FWCore.ParameterSet.Config as cms | ||
|
||
from Configuration.Eras.Era_Phase2C6_timing_cff import Phase2C6_timing | ||
from Configuration.Eras.Modifier_phase2_timing_layer_cff import phase2_timing_layer | ||
from Configuration.Eras.Modifier_phase2_timing_layer_bar_cff import phase2_timing_layer_bar | ||
|
||
Phase2C6_timing_layer_bar = cms.ModifierChain(Phase2C6_timing, phase2_timing_layer, phase2_timing_layer_bar) | ||
|
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
50 changes: 0 additions & 50 deletions
50
Configuration/Geometry/python/GeometryExtended2023D17Reco_cff.py
This file was deleted.
Oops, something went wrong.
12 changes: 0 additions & 12 deletions
12
Configuration/Geometry/python/GeometryExtended2023D17_cff.py
This file was deleted.
Oops, something went wrong.
54 changes: 0 additions & 54 deletions
54
Configuration/Geometry/python/GeometryExtended2023D19Reco_cff.py
This file was deleted.
Oops, something went wrong.
14 changes: 0 additions & 14 deletions
14
Configuration/Geometry/python/GeometryExtended2023D19_cff.py
This file was deleted.
Oops, something went wrong.
50 changes: 0 additions & 50 deletions
50
Configuration/Geometry/python/GeometryExtended2023D21Reco_cff.py
This file was deleted.
Oops, something went wrong.
12 changes: 0 additions & 12 deletions
12
Configuration/Geometry/python/GeometryExtended2023D21_cff.py
This file was deleted.
Oops, something went wrong.
59 changes: 0 additions & 59 deletions
59
Configuration/Geometry/python/GeometryExtended2023D24Reco_cff.py
This file was deleted.
Oops, something went wrong.
13 changes: 0 additions & 13 deletions
13
Configuration/Geometry/python/GeometryExtended2023D24_cff.py
This file was deleted.
Oops, something went wrong.
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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.
@emiglior @ghugo83 for my own understanding (in view of the other geometry-dependent conditions to be maintained for the future), is T11 (50x50um^2 cell) totally deprecated at this point? Is it going to be superseded by something else?
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.
@mmusich T11 is not yet totally deprecated as currently we do not have another geometry featuring square pixels. As you wrote, it will be superseded once we reach a more stable layout (e.g. skew TBPX ladders and MB updates)
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.
@emiglior thanks. But if I understand correctly the changes proposed here, T11 won't be exercised anymore in any production workflow (starting from the first pre-release in which this is merged). Is this the desired outcome? I am thinking in the scope of maintaining geometry-dependent IT conditions bound to this layout.
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.
To be clear, T11 is not among the geometries explicitly listed to be kept in #26938, and therefore it is removed. We cannot maintain a monotonically increasing list of tracker geometries forever. The tracker group needs to set clear timelines and deliverables for alternate geometry studies.