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
GE0 geometry builder #29624
GE0 geometry builder #29624
Conversation
Adds a new Geometry and a test file to check that the geometry can be built and to compare with ME0.
The code-checks are being triggered in jenkins. |
-code-checks Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-29624/14993
Code check has found code style and quality issues which could be resolved by applying following patch(s)
|
The code-checks are being triggered in jenkins. |
+code-checks Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-29624/14994
|
A new Pull Request was created by @watson-ij (Ian J. Watson) for master. It involves the following packages: Geometry/GEMGeometry @civanch, @Dr15Jones, @makortel, @cvuosalo, @ianna, @mdhildreth, @cmsbuild, @kpedro88 can you please review it and eventually sign? Thanks. cms-bot commands are listed here |
superChamber->add( | ||
theGeometry.chamber(GEMDetId(detId.region(), detId.ring(), detId.station(), 2, detId.chamber(), 0))); | ||
foundSuperChamber = true; | ||
int nstation = (st == 0) ? 6 : 2; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
magic numbers should be named constants
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@watson-ij Please use these constants. https://github.com/cms-sw/cmssw/blob/master/DataFormats/MuonDetId/interface/GEMDetId.h#L30-L31. I also suggest to rename nstation
to nlayers
.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
int nstation = (st == 0) ? 6 : 2; | |
int nlayers = (st == 0) ? GEMDetId::maxLayerId0 : GEMDetId::maxLayerId; |
So, just to check @kpedro88 something like this would be okay, or I also need to introduce a named constant somewhere for st==0
?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
You could use GEMDetId::minStationId0
please test |
The tests are being triggered in jenkins. |
@slomeo - FYI |
The code-checks are being triggered in jenkins. |
+code-checks Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-29624/15270
|
Pull request #29624 was updated. @civanch, @Dr15Jones, @makortel, @cvuosalo, @ianna, @mdhildreth, @cmsbuild, @kpedro88 can you please check and sign again. |
please test |
The tests are being triggered in jenkins. |
+1 |
Comparison job queued. |
Comparison is ready Comparison Summary:
|
+1 |
+upgrade |
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) |
+1 |
PR description:
Updates to build GE0 geometry: that is, ME0 as part of GEM rather than a separate system.
Builds on the GE0 geometry xmls introduced in PR #29463 with the following:
@jshlee @bsunanda
PR validation:
I tested by writing a testGE0Geometry_cfg.py which loads the new geometry (GE0 as part of GEM geometry) and writing a script to compare the positions of the GE0 with the output of testME0Geometry_cfg.py; all corresponding eta partitions are in the same positions. I also checked that a 2026 upgrade workflow still runs correctly. Running with the new geometry requires changes upstream of geometry and will be made later.
if this PR is a backport please specify the original PR and why you need to backport that PR:
Before submitting your pull requests, make sure you followed this checklist: