Add Phase 2 Trackers T21 + T22 + T23 (Mechanical Update in Outer Tracker + Sensors studies in Inner Tracker)

[ghugo83]

PR description:

This PR:

• Introduces a Tracker baseline, called T21. It has a Phase 2 Outer Tracker with updated TBPS (changes in Layer 1 to facilitate IT insertion) and TEDD (update sensors Z inter-spacing in all TEDD).
• Introduces T22, a Tracker based on T21, but with 50x50 um2 pixels everywhere in Inner Tracker.
• Introduces T23, a Tracker based on T21, but with 3D sensors in TBPX L1 + TBPX L2 + TFPX R1.

T21:
tkLayout description: http://ghugo.web.cern.ch/ghugo/layouts/T21/OT800_IT615/layoutpixel.html
Geometry scenario: 2026D63.
Workflows: 294xx (no PU), 296xx (PU).

T22:
tkLayout description: http://ghugo.web.cern.ch/ghugo/layouts/T22/OT800_IT621/layoutpixel.html
Geometry scenario: 2026D64.
Workflows: 298xx (no PU), 300xx (PU).

T23:
tkLayout description: http://ghugo.web.cern.ch/ghugo/layouts/T23/OT800_IT700/layoutpixel.html
Geometry scenario: 2026D65.
Workflows: 302xx (no PU), 304xx (PU).

Following comparisons should be made:

Validate new Outer Tracker:

Compare T21 versus T20 (2026D63 versus 2026D56).
Should not expect any meaningful change in the tracking performance (maybe an extremely tiny degradation).

Inner Tracker sensors studies:

Now have a common base to compare different sensors options.
Only bricked pixels sensors option is missing (I included that geometry in another private branch).

25x100 -> 50x50:
Compare T22 (50x50, planar) versus T21 (25x100, planar) (2026D64 versus 2026D63).
An interesting fast sim estimate is available at:
25x100: http://ghugo.web.cern.ch/ghugo/layouts/T21/OT800_IT615/errorstracker.html
50x50: http://ghugo.web.cern.ch/ghugo/layouts/T22/OT800_IT621/errorstracker.html
With obviously, especially visible here at high pT, a significant degradation of pT and transverse impact parameter resolution, and an improvement of longitudinal impact parameter resolution. Of course less visible at low pT (multiple scattering).

planar -> 3D:
Compare T23 (3D) versus T21 (planar) (2026D65 versus 2026D63).
tkLayout track parameters code fully debugged and operational in the case of 3D sensors.
Though, would need to fix 3D local resolution parametrization used as input in tkLayout, to get meaningful fast sim results on that front as well.

PR validation:
Following was done for CMSSW validation:

• Checked XMLs make sense from Tracker design point of view, in concordance with Mechanics.
• Checked overlaps with Fireworks + Geant4 tools.
• Checked workflow numbering.
• Checked that workflows with D63, D64, D65 scenarios run smoothly with no extra error / warning.

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

[cmsbuild]

Pull request #30927 was updated. @andrius-k, @gouskos, @lveldere, @chayanit, @wajidalikhan, @sbein, @schneiml, @ianna, @kpedro88, @rekovic, @fioriNTU, @tlampen, @jpata, @pohsun, @santocch, @peruzzim, @perrotta, @civanch, @makortel, @cmsbuild, @fwyzard, @davidlange6, @smuzaffar, @Dr15Jones, @cvuosalo, @ssekmen, @mdhildreth, @jfernan2, @tocheng, @slava77, @ggovi, @qliphy, @fabiocos, @benkrikler, @kmaeshima, @christopheralanwest, @pgunnell, @alja, @franzoni, @silviodonato, @fgolf, @mariadalfonso can you please check and sign again.

[cmsbuild]

The code-checks are being triggered in jenkins.

[cmsbuild]

+code-checks

Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-30927/17420

• This PR adds an extra 304KB to repository

• Found files with invalid states:

  • RecoMET/METFilters/python/BadPFMuonFilter_Dz_cfi.py:
    • Added: 092e313
    • Modified: 5ce8d45
    • Deleted: 4eb0ea0
  • HeterogeneousCore/SonicTriton/src/TritonUtils.cc:
    • Added: 2c5aca0
    • Deleted: 49bf75b
  • HeterogeneousCore/SonicTriton/interface/TritonUtils.h:
    • Added: 2c5aca0
    • Deleted: 49bf75b

[cmsbuild]

Pull request #30927 was updated. @andrius-k, @gouskos, @lveldere, @chayanit, @wajidalikhan, @sbein, @schneiml, @ianna, @kpedro88, @rekovic, @fioriNTU, @tlampen, @jpata, @pohsun, @santocch, @peruzzim, @perrotta, @civanch, @makortel, @cmsbuild, @fwyzard, @davidlange6, @smuzaffar, @Dr15Jones, @cvuosalo, @ssekmen, @mdhildreth, @jfernan2, @tocheng, @slava77, @ggovi, @qliphy, @fabiocos, @benkrikler, @kmaeshima, @christopheralanwest, @pgunnell, @alja, @franzoni, @silviodonato, @fgolf, @mariadalfonso can you please check and sign again.

[ghugo83]

Reopened it at #30976 .
Sorry, but for some mysterious reason, the github comparison is being made here to the 'old' master branch from yesterday.

[alja]

+1

[cmsbuild]

The tests are being triggered in jenkins.

• CMSSW_11_2_X_2020-07-30-1100/slc7_amd64_gcc820: https://cmssdt.cern.ch/jenkins/job/ib-run-pr-tests/8432/console Started: 2020/07/30 18:12

[kpedro88]

please close

[kpedro88]

@smuzaffar @mrodozov can we prevent the bot from starting tests for closed PRs?

[smuzaffar]

sure, bot should not test closed PR. I will fix it.

[cmsbuild]

+1
Tested at: 5afca5e
https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-57c0a5/8432/summary.html
CMSSW: CMSSW_11_2_X_2020-07-30-1100
SCRAM_ARCH: slc7_amd64_gcc820

[cmsbuild]

Comparison job queued.

[cmsbuild]

Comparison is ready
https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-57c0a5/8432/summary.html

Comparison Summary:

• No significant changes to the logs found
• Reco comparison results: 4 differences found in the comparisons
• DQMHistoTests: Total files compared: 34
• DQMHistoTests: Total histograms compared: 2525444
• DQMHistoTests: Total failures: 7
• DQMHistoTests: Total nulls: 0
• DQMHistoTests: Total successes: 2525390
• DQMHistoTests: Total skipped: 47
• DQMHistoTests: Total Missing objects: 0
• DQMHistoSizes: Histogram memory added: 0.0 KiB( 33 files compared)
• Checked 144 log files, 17 edm output root files, 34 DQM output files

[silviodonato]

move to #31673