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 Phase 2 TFPX geometries (T17 and T18) #28503
Conversation
…thin all double-disks + Increased distance between Disks 6 and 7 + Put TBPX portcards between Disks 6 and 7. IT 616, TFPX: Shift all double-disks by + 25mm in Z. All services volumes (& TBPX portcards) are also shifted.
…to be discussed).
The code-checks are being triggered in jenkins. |
@@ -46,5 +48,7 @@ Several detector combinations have been generated: | |||
* D48 = T16+C9+M3+I10+O3+F2 | |||
* D49 = T15+C9+M4+I10+O4+F2 | |||
* D50 = T15+C9+M4+I11+O4+F2 | |||
* D51 = T17+C9+M4+I10+O4+F2 |
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.
It was not clear to me whether I should use M3 or M4, O3 or O4, I10 or I11.
Please let me know in case change is needed here :)
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 think you made the right choice to start from D49, since that is the new baseline for the HLT TDR. (M4 and O4 should always go together.)
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.
ok thanks @kpedro88
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.
+code-checks Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-28503/12954
|
A new Pull Request was created by @ghugo83 for master. It involves the following packages: Configuration/Geometry @cmsbuild, @civanch, @Dr15Jones, @chayanit, @cvuosalo, @ianna, @mdhildreth, @pgunnell, @franzoni, @kpedro88, @zhenhu, @fabiocos, @davidlange6 can you please review it and eventually sign? Thanks. cms-bot commands are listed here |
@@ -8,6 +8,8 @@ Tracker: | |||
* T14: Phase2 tilted tracker (v6.1.6) w/ phase 2 pixel (v6.1.3) (Based from T12. OT: reduced envelope. IT: new chip size, different radii, 2x2 modules everywhere in TEPX, new ring paradigm in TEPX) | |||
* T15: Phase2 tilted tracker (v6.1.6) w/ phase 2 pixel (v6.1.3) (Active geometry: same as T14. Material Budget: major update in IT, gathering info from recent Mechanical designs.) | |||
* T16: Active geometry: skewed Inner Tracker geometry. Material Budget: same as T15. | |||
* T17: Phase2 tilted tracker (v6.1.6) w/ phase 2 pixel (v6.1.5) TFPX: Changed sensors spacing within all double-disks + Increased distance between Disks 6 and 7 + Put TBPX portcards between Disks 6 and 7. | |||
* T18: Phase2 tilted tracker (v6.1.6) w/ phase 2 pixel (v6.1.6) TFPX: Shift all double-disks by + 25mm in Z. All services volumes (& TBPX portcards) are also shifted. |
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.
has this been checked for overlaps?
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.
Yes i always solve all overlaps (it's a show-stopper for tracking) + also did the other checks mentioned in PR validation.
please test workflow 23634.0,24034.0 |
The tests are being triggered in jenkins. |
Comparison job queued. |
Comparison is ready @slava77 comparisons for the following workflows were not done due to missing matrix map:
Comparison Summary:
|
+upgrade |
+1 |
+1 |
+operations the update of StandardSequences is coherent with the purpose of this PR |
+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 be automatically merged. |
@fabiocos: is there any chance that D51 and D52 will be part of 11.0 or they will go in 11.1? |
"Milestone CMSSW_11_1_X" |
@emiglior this is in 11_1_X, as you may also see in https://cmssdt.cern.ch/SDT/html/cmssdt-ib/#/ib/CMSSW_11_1_X . If what you need is a RelVal sample I do not see why this could not be produced in 11_1_0_pre1 (@pgunnell @chayanit please comment in case), of course it depends on what you mean by "large" |
PR description:
TFPX study.
This PR adds 2 Phase 2 Inner Tracker geometries: T17 and T18, and their associated workflows.
T17 corresponds to most realistic TFPX design, while T18 intends to study the effect of shifting TFPX double-disks in Z.
Tracking performance plots are needed for both designs.
Following comparisons should be made:
T16 versus T17 (2026D48 versus 2026D51).
T17 versus T18 (2026D51 versus 2026D52).
T17:
http://ghugo.web.cern.ch/ghugo/layouts/T17/OT616_IT615/materialpixel.html
Changed sensors spacing within all double-disks + Increased distance between Disks 6 and 7 + Put TBPX portcards between Disks 6 and 7.
Geometry scenario is: 2026D51.
Workflows are: 236xx (no PU), 238xx (PU).
T18:
http://ghugo.web.cern.ch/ghugo/layouts/T18/OT616_IT616/materialpixel.html
Shift all double-disks by + 25mm in Z. All services volumes (& TBPX portcards) are also shifted.
Geometry scenario is: 2026D52.
Workflows are: 240xx (no PU), 242xx (PU).
NB: This PR is TFPX-only, does not include recent changes in OT.
PR validation:
Following was done for validation:
This allows to reuse the fakeConditions from T15.
FYI: @emiglior @pwittich @bsunanda @fabiocos @kpedro88 @mmusich @jalimena @boudoul