-
Notifications
You must be signed in to change notification settings - Fork 4.2k
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
MTD RECO geometry: MTDNumberingBuilder code simplification #28997
Conversation
The code-checks are being triggered in jenkins. |
+code-checks Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-28997/13838
|
A new Pull Request was created by @fabiocos (Fabio Cossutti) for master. It involves the following packages: Geometry/MTDNumberingBuilder @civanch, @Dr15Jones, @makortel, @cvuosalo, @ianna, @mdhildreth, @cmsbuild, @kpedro88 can you please review it and eventually sign? Thanks. cms-bot commands are listed here |
please test |
The tests are being triggered in jenkins. |
+1 |
Comparison job queued. |
Comparison is ready Comparison Summary:
|
+1 |
@kpedro88 comments? |
@cvuosalo @kpedro88 @silviodonato for the time being, unless you have further comments, I consider this PR as stable, and defer further developments to the next PR I am preparing, essentially adapt this new structure to include the new ETL design (which has a different structure and requires some non-trivial code adjustment). |
+upgrade |
+1 |
please test workflow 23234.1001, 23434.1001 |
The tests are being triggered in jenkins.
|
+1 |
Comparison job queued. |
Comparison is ready @slava77 comparisons for the following workflows were not done due to missing matrix map:
Comparison Summary:
|
+1 |
PR description:
The existing MTD RECO geometry is based on a clone and minimal adjustment of the existing tracker geometry performed mostly by @lgray in view of the MTD TDR release. The need to 1) add the new ETL design and 2) to migrate this code to DD4hep strengthen the need for a code simplification and refresh, already emerged in the 2018 review and in more recent discussions with @ianna.
This PR is the first step in this direction: the aim is to preserve the existing geometry description, to be tested in detail through the refreshed test classes in
Geometry/MTDNumberingBuilder
andGeometry/MTDGeometryBuilder
, while moving from a layered build of theGeometricTimingDet
structure from DDD to a much simpler overall loop, where only the subdetectors (BTL and ETL, two sides) and the final sensitive modules are kept (and appear necessary).Several intermediate classes are removed, with no apparent impact on the final geometry structure produced in
MTDGeometryBuilder
.The following step is the modification of the
DDDCmsMTDConstruction
class (and auxiliary code) to include the new geometry structure of ETL as implemented by @icosivi at xml level.PR validation:
The dumps of the geometries, provided the same version of the test analyzers in
mtd_cfg.py
for the benchmark scenario D50, differ only inGeometricTimingDetAnalyzer
for the fix of the type of modules performed in GeometricTimingDet (but apparently not relevant in the final construction of the geometry):