Skip to content
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 Outer Tracker with sensors updates + OTST MB update. Remove T18. #29607

Merged
merged 10 commits into from
May 5, 2020

Conversation

ghugo83
Copy link
Contributor

@ghugo83 ghugo83 commented Apr 30, 2020

PR description:

This PR introduces a Phase 2 Outer Tracker with thicker sensors (+ other updates in modules) + includes very significant changes in OTST MB.
Was presented at: https://indico.cern.ch/event/889563/contributions/3760870/attachments/1992522/3323596/hugo.pdf

The new Tracker is called T20.
Geometry scenario: 2026D56.
Workflows: 266xx (no PU), 268xx (PU).

OT:

  • Sensor thickness: 200 → 290 um
    Total Outer Tracker weight: +56 kg (1630 kg → 1686 kg).
  • MB modules update: sensors inactive Si (inactive edges + deep diffused) + MPA.
  • New PS module model. Sensors have different lengths, s-sensor slightly longer than p-sensor.

Before PR: http://cms-tklayout.web.cern.ch/cms-tklayout/layouts-work/repository-git-dev/OT616_200_IT613/weightsouter.html
After PR: http://cms-tklayout.web.cern.ch/cms-tklayout/layouts-work/repository-git-dev/OT616_IT613/weightsouter.html
sensors_ratio

OTST:
Many changes in geo and MB from Mechanics, the most significant one being: CFRP skin: 2 mm → 4 mm.
Total OTST mass: 147 kg → 300 kg.
otst_ratio

NB: Only Outer Tracker is updated here, no IT included. An existing Inner Tracker is directly called (T17).

Following comparisons should be made:
T17 versus T20 (2026D51 versus 2026D56).

PR validation:
Following was done for validation:

  • Solved all overlaps on CMSSW with Fireworks and Geant4 tools.
  • Even if the active geometry is different from T15, logically there should be no DetId diff (based on how the DetIds are computed in CMSSW). Checked that this is the case indeed.
    This allows to reuse the fakeConditions from T15.
  • Checked workflow numbering.
  • Checked that workflows with D56 run smoothly with no extra error / warning.

FYI: @dpiparo @civanch @ianna @emiglior @skinnari @mmusich @jalimena @bsunanda @fabiocos @kpedro88

ghugo83 added 9 commits April 30, 2020 17:34
…+ Update in Module MB + PS modules: s-sensor 164 um longer + Major update in OTST MB.
…plit (in Z) TFPX design, as done by Mechanics, on tracking performance.
…n OT modules MB (sensors thickness + hybrids + MPA MB).
… (error throwm with muon xml missing), so keep including M4 version for now. Do not care about muon version for this tracker performance test study anyway.
@cmsbuild
Copy link
Contributor

The code-checks are being triggered in jenkins.

@cmsbuild
Copy link
Contributor

+code-checks

Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-29607/14943

  • This PR adds an extra 124KB to repository

@cmsbuild
Copy link
Contributor

A new Pull Request was created by @ghugo83 for master.

It involves the following packages:

Configuration/Geometry
Configuration/PyReleaseValidation
Configuration/StandardSequences
Geometry/CMSCommonData
Geometry/TrackerCommonData
Geometry/TrackerRecoData

@pgunnell, @civanch, @Dr15Jones, @chayanit, @cvuosalo, @wajidalikhan, @ianna, @mdhildreth, @cmsbuild, @makortel, @franzoni, @silviodonato, @kpedro88, @fabiocos, @davidlange6 can you please review it and eventually sign? Thanks.
@fabiocos, @vargasa, @makortel, @felicepantaleo, @GiacomoSguazzoni, @rovere, @VinInn, @Martin-Grunewald, @lecriste, @ebrondol, @dgulhan, @venturia this is something you requested to watch as well.
@silviodonato, @dpiparo you are the release manager for this.

cms-bot commands are listed here

@cvuosalo
Copy link
Contributor

@cmsbuild please test

@cmsbuild
Copy link
Contributor

cmsbuild commented Apr 30, 2020

The tests are being triggered in jenkins.
https://cmssdt.cern.ch/jenkins/job/ib-run-pr-tests/5937/console Started: 2020/04/30 22:58

… version are unchanged, can also add with no harm that Tracker version to the supported geometries in recent code in L1Trigger/TrackerDTC.
@cvuosalo
Copy link
Contributor

cvuosalo commented May 1, 2020

+1

@chayanit
Copy link

chayanit commented May 4, 2020

+1

@kpedro88
Copy link
Contributor

kpedro88 commented May 4, 2020

+upgrade

@silviodonato
Copy link
Contributor

+operations

@silviodonato
Copy link
Contributor

do you have any comments @rekovic ?

@rekovic
Copy link
Contributor

rekovic commented May 5, 2020

+1

@cmsbuild
Copy link
Contributor

cmsbuild commented May 5, 2020

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. @silviodonato, @dpiparo (and backports should be raised in the release meeting by the corresponding L2)

@silviodonato
Copy link
Contributor

+1

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

8 participants