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

Phase 2 tracker: add T28 and T29 (geometries with bricked pixels for IT sensor design studies) #36457

Merged
merged 4 commits into from
Dec 21, 2021

Conversation

adewit
Copy link
Contributor

@adewit adewit commented Dec 10, 2021

PR description:

This PR adds two new phase2 tracker layouts proposed in the IT sensors performance task force and correspond to evolutions of T27 (geometry with bricked pixels). More information [in these slides]

In particular this adds:

  • T28, a tracker based on T25, with 25x100 mum2 3D pixels in IT TBPX layer 1, bricked pixels in the central rod of TBPX layers 2 and 3, in the central 3 rods of TBPX layer 4, in TEPX, and in disks 5-8 of TFPX. The other pixels are planar 25x100 mum2.

  • T29, a tracker based on T25, with 25x100 mum2 3D pixels in IT TBPX layer 1, bricked pixels in the central rod of TBPX layers 2 and 3, in the central 3 rods of TBPX layer 4. 50x50 mum2 planar pixels are used in TFPX and TEPX.

There are no changes in the OT wrt T25.

T28 is included in geometry scenario 2026D89 and T29 in scenario 2026D90

important: we use process modifiers to account for the presence of bricked pixels, but no square pixel process modifiers are applied (even in T29). The reason for this is that with the square pixel process modifier the genErrors are used when running the CPE without track angles, but we do not have genErrors for bricked pixels.

@emiglior @tsusa @connorpa fyi

PR validation:

  • checked XMLs make sense wrt tracker design
  • checked that the workflows with scenarios D89 and D90 run smoothly with no warnings.

if this PR is a backport please specify the original PR and why you need to backport that PR:

Not a backport

@cmsbuild
Copy link
Contributor

+code-checks

Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-36457/27303

@cmsbuild
Copy link
Contributor

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

It involves the following packages:

  • Configuration/Geometry (geometry, upgrade)
  • Configuration/PyReleaseValidation (pdmv, upgrade)
  • Configuration/StandardSequences (operations)
  • Geometry/CMSCommonData (geometry, upgrade)
  • Geometry/TrackerCommonData (geometry)

@perrotta, @civanch, @Dr15Jones, @jordan-martins, @makortel, @cvuosalo, @wajidalikhan, @ianna, @mdhildreth, @cmsbuild, @AdrianoDee, @srimanob, @kskovpen, @bbilin, @qliphy, @fabiocos, @davidlange6 can you please review it and eventually sign? Thanks.
@fabiocos, @vargasa, @makortel, @felicepantaleo, @slomeo, @GiacomoSguazzoni, @JanFSchulte, @rovere, @VinInn, @Martin-Grunewald, @bsunanda, @ebrondol, @kpedro88, @lecriste, @mmusich, @ghugo83, @mtosi, @dgulhan, @missirol, @venturia this is something you requested to watch as well.
@perrotta, @dpiparo, @qliphy you are the release manager for this.

cms-bot commands are listed here

@mmusich
Copy link
Contributor

mmusich commented Dec 10, 2021

test parameters:

  • workflows = 39834.0, 40234.0

@mmusich
Copy link
Contributor

mmusich commented Dec 10, 2021

@adewit

important: we use process modifiers to account for the presence of bricked pixels, but no square pixel process modifiers are applied (even in T29).

I guess you do that because otherwise you would fall in the case in which genErrors are used when the CPE is called w/o track angles and there are none for bricked pixels.

(phase2_tracker & (phase2_squarePixels | phase2_3DPixels)).toModify(PixelCPEGenericESProducer,
NoTemplateErrorsWhenNoTrkAngles = False # use genErrors in the seeding step (when no track angles are available)
)

If that's the case might be worth specifying in the PR description.

@adewit
Copy link
Contributor Author

adewit commented Dec 11, 2021

@adewit

important: we use process modifiers to account for the presence of bricked pixels, but no square pixel process modifiers are applied (even in T29).

I guess you do that because otherwise you would fall in the case in which genErrors are used when the CPE is called w/o track angles and there are none for bricked pixels.

(phase2_tracker & (phase2_squarePixels | phase2_3DPixels)).toModify(PixelCPEGenericESProducer,
NoTemplateErrorsWhenNoTrkAngles = False # use genErrors in the seeding step (when no track angles are available)
)

If that's the case might be worth specifying in the PR description.

Yes, that is the reason. Have updated the PR description to be more specific about this.

@cmsbuild
Copy link
Contributor

+code-checks

Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-36457/27307

@cmsbuild
Copy link
Contributor

@mmusich
Copy link
Contributor

mmusich commented Dec 11, 2021

please test

@cmsbuild
Copy link
Contributor

+1

Summary: https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-b9b732/21202/summary.html
COMMIT: fb136d1
CMSSW: CMSSW_12_3_X_2021-12-10-1100/slc7_amd64_gcc900
User test area: For local testing, you can use /cvmfs/cms-ci.cern.ch/week0/cms-sw/cmssw/36457/21202/install.sh to create a dev area with all the needed externals and cmssw changes.

Comparison Summary

@slava77 comparisons for the following workflows were not done due to missing matrix map:

  • /data/cmsbld/jenkins/workspace/compare-root-files-short-matrix/data/PR-b9b732/39834.0_TTbar_14TeV+2026D89+TTbar_14TeV_TuneCP5_GenSimHLBeamSpot14+DigiTrigger+RecoGlobal+HARVESTGlobal
  • /data/cmsbld/jenkins/workspace/compare-root-files-short-matrix/data/PR-b9b732/40234.0_TTbar_14TeV+2026D90+TTbar_14TeV_TuneCP5_GenSimHLBeamSpot14+DigiTrigger+RecoGlobal+HARVESTGlobal

Summary:

  • No significant changes to the logs found
  • Reco comparison results: 0 differences found in the comparisons
  • DQMHistoTests: Total files compared: 42
  • DQMHistoTests: Total histograms compared: 3250704
  • DQMHistoTests: Total failures: 0
  • DQMHistoTests: Total nulls: 0
  • DQMHistoTests: Total successes: 3250682
  • DQMHistoTests: Total skipped: 22
  • DQMHistoTests: Total Missing objects: 0
  • DQMHistoSizes: Histogram memory added: 0.0 KiB( 41 files compared)
  • Checked 177 log files, 37 edm output root files, 42 DQM output files
  • TriggerResults: no differences found

@perrotta
Copy link
Contributor

+operations

@cmsbuild
Copy link
Contributor

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

@perrotta
Copy link
Contributor

merge
(Fixed the geometry scenario in a comment field: no need to re-test)

@cmsbuild
Copy link
Contributor

+code-checks

Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-36457/27511

@cmsbuild
Copy link
Contributor

@cmsbuild cmsbuild merged commit 1d3499a into cms-sw:master Dec 21, 2021
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.

9 participants