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
Phase 2 Trackers. Remove T12 and T13 (IT portcards placement study). Add T15 (Major Inner Tracker MB update from latest Mechanical designs). #26544
Conversation
… geometry same as T14). + Remove XMLs from T12 and T13.
…rs T12 and T13 respectively).
…ws associated to D36 and D37 geometry scenarios. Made workflow numbering invariant.
The code-checks are being triggered in jenkins. |
+code-checks Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-26544/9440
|
A new Pull Request was created by @ghugo83 for master. It involves the following packages: Configuration/Geometry @cmsbuild, @prebello, @Dr15Jones, @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 |
please test workflow 29434.0 |
The tests are being triggered in jenkins. |
+1 The following merge commits were also included on top of IB + this PR after doing git cms-merge-topic: |
Comparison job queued. |
Comparison is ready @slava77 comparisons for the following workflows were not done due to missing matrix map:
Comparison Summary:
|
Comparison is ready @slava77 comparisons for the following workflows were not done due to missing matrix map:
Comparison Summary:
|
+upgrade |
+1 |
+operations the update of Configuration packages is coherent with the purpose of the PR |
@fabiocos I also noticed this new scenario includes very old versions of other Phase 2 subdetectors. I think this is done to be consistent with other tracker test scenarios for comparisons. But I agree, at some point (11_0_X?), we should move every scenario toward the more recent configurations. |
+1 |
merge |
+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. |
PR description:
This PR adds Tracker T15, and its associated workflows.
This Tracker has same active geometry as T14, but significant MB update from latest Mechanical designs. More details in [1].
Thanks a lot to IT Mechanics group for the fruitful exchange!
Full Tracker description is accessible at: http://ghugo.web.cern.ch/ghugo/layouts/T15/OT616_200_IT613/info.html
Geometry scenario is: 2023D42.
Workflows are: 294xx (no PU), 296xx (PU).
Tracking performance should be compared with T14 (2023D40 scenario).
Notably, it would be valuable to get the fake rate at PU200 (workflow 29434.0) versus T14.
This PR also removes the Trackers which were used for IT portcards placement study (T12 and T13 + their associated workflows).
NB: This includes data from latest Mechanical designs, which is a moving process: obviously IT MB will still need to be further updated, as latest designs become available. This can imply significant changes.
This PR does however contain a first deep review of full IT MB.
This should also point out the importance of Mechanical choices, which can have a deep impact on the tracking performance.
PR validation:
Following was done for validation:
[1] Tracker changes in this PR (versus T14 description):
Outer Tracker:
Slight diff in MB, intentionally kept to non-significant.
Inner Tracker:
TO DO:
FYI: @emiglior @jalimena @boudoul @kpedro88 @pwittich @alkemyst