-
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
Add Skewed Phase 2 Inner Tracker geometry (T16). #27824
Conversation
… from bsunanda to avoid issues in workflow numbering.
…the latest CMS geometries. Hence, D48 is now same as D47, but with Tracker T16 instead of T15.
The code-checks are being triggered in jenkins. |
A new Pull Request was created by @ghugo83 for master. It involves the following packages: Configuration/Eras @cmsbuild, @prebello, @Dr15Jones, @chayanit, @cvuosalo, @civanch, @ianna, @mdhildreth, @pgunnell, @franzoni, @kpedro88, @zhenhu, @fabiocos, @davidlange6 can you please review it and eventually sign? Thanks. cms-bot commands are listed here |
Configuration/Geometry/README.md
Outdated
@@ -37,5 +39,7 @@ Several detector combinations have been generated: | |||
* D44 = T14+C6+M3+I7+O2+F3 | |||
* D45 = T15+C8+M3+I10+O3+F2 | |||
* D46 = T15+C9+M3+I10+O3+F2 | |||
* D47 = T15+C10+M3+I10+O3+F3 | |||
* D48 = T16+C10+M3+I10+O3+F3 |
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.
I don't think a tracker test workflow needs to include the HF nose. I would make either D45 or D46 the basis for D48.
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.
Are C10 and F3 not the latest descriptions available?
In that case, why not having the latest Tracker description with them, and compare D48 versus D47?
It would avoid having latest subdetectorA with old subdetectorB and latest subdetectorB with old subdetectorA. Which would imply that when one wants to access the latest available CMS geometry, it does not exist?
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.
C10 and F3 are the latest version of the HF nose. This is a detector R&D effort that is not yet an approved part of the Phase 2 upgrade project. Combining tracker tests with this will just lead to confusion and inconsistencies.
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.
Ha I didn't know C10 and F3 were purely in an hypothetical state for now.
Ok I will simply revert my last commit then.
The code-checks are being triggered in jenkins. |
Comparison is ready @slava77 comparisons for the following workflows were not done due to missing matrix map:
Comparison Summary:
|
+1 |
@kpedro88 as stated in the PR description:
This means that using |
+upgrade |
+operations |
+1 |
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. @davidlange6, @slava77, @smuzaffar, @fabiocos (and backports should be raised in the release meeting by the corresponding L2) |
+1 |
PR description:
This PR adds Skewed Phase 2 Inner Tracker geometry (T16), and its associated workflows.
The skewed Inner Tracker description is accessible at: http://cms-tklayout.web.cern.ch/cms-tklayout/layouts-work/repository-git-dev/OT616_200_IT613/layoutpixel.html
Several ladders are rotated in TBPX around CMX_Z axis ('skewed'). This is to allow space for cooling pipes, as it will be in the detector to be installed.
There is no update in terms of Material Budget here, focus is geometry-only.
Geometry scenario is: 2026D48.
Workflows are: 228xx (no PU), 230xx (PU).
Tracking performance should be compared with T15 (2026D46 scenario).
NB:
Please merge PR Phase2-hcx214 Add a new scenario and workflow with latest Phase2 configuration including HFNose #27665 first.
Present PR is created on top of 27665, to avoid having shifts in workflow numbering (no need to leave free spots for D47).
I (might) have very trivial conflict to solve once 27665 is merged into master.
IMPORTANT: This only introduces the skewed geometry description. There might be adjustments to do on CMSSW side to deal with the skewed ladders.
Got runs through the 4 steps without extra warning/error, which is already a good sign, but obviously does not mean at all everything is OK...
On CMSSW side, I checked that the sim geometry construction is OK.
First feedback from @migliore is that DIGI step should be fine, this should be looked at in details though.
Possible tunings needed on top of this PR!
PR validation:
Following was done for validation:
This allows to reuse the fakeConditions from T15.
FYI: @emiglior @pwittich @bsunanda @fabiocos @kpedro88 @mmusich @jalimena @boudoul