[GEM] GEMGeometryBuilder update for the 2024 geometry

[yeckang]

PR description:

• The GE2/1 demonstrator was installed at the beginning of Run 3.
• At the beginning of the year, we installed the 2 GE 2/1 production chambers on the other region of the demonstrator.
• @bsunanda made the GEM geometry for 2024. (Run3-gex175 Try to have the 2024 version of GE21 #43876).
• On the testing for the new geometry, the demonstrator is not built with the new 2 production chambers.
• This PR allows the building of the demonstrator with the 2 new chambers.

PR validation:

• scram b code-format and scram b code-checks are applied
• The built geometry has been tested with GEMGeometryAnalyzer

@watson-ij

[cmsbuild]

cms-bot internal usage

[cmsbuild]

+code-checks

Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-43948/38820

• This PR adds an extra 20KB to repository

[cmsbuild]

A new Pull Request was created by @yeckang (Yechan Kang) for master.

It involves the following packages:

• Geometry/GEMGeometryBuilder (upgrade, geometry)

@civanch, @makortel, @srimanob, @Dr15Jones, @subirsarkar, @mdhildreth, @cmsbuild, @bsunanda can you please review it and eventually sign? Thanks.
@watson-ij, @giovanni-mocellin, @fabiocos, @slomeo, @bsunanda, @jshlee this is something you requested to watch as well.
@antoniovilela, @sextonkennedy, @rappoccio you are the release manager for this.

cms-bot commands are listed here

[watson-ij]

please test

[cmsbuild]

+1

Summary: https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-477748/37398/summary.html
COMMIT: c4711e6
CMSSW: CMSSW_14_1_X_2024-02-12-2300/el8_amd64_gcc12
User test area: For local testing, you can use /cvmfs/cms-ci.cern.ch/week0/cms-sw/cmssw/43948/37398/install.sh to create a dev area with all the needed externals and cmssw changes.

Comparison Summary

Summary:

• You potentially removed 24 lines from the logs
• Reco comparison results: 64 differences found in the comparisons
• DQMHistoTests: Total files compared: 48
• DQMHistoTests: Total histograms compared: 3248554
• DQMHistoTests: Total failures: 1189
• DQMHistoTests: Total nulls: 0
• DQMHistoTests: Total successes: 3247343
• DQMHistoTests: Total skipped: 22
• DQMHistoTests: Total Missing objects: 0
• DQMHistoSizes: Histogram memory added: 0.0 KiB( 47 files compared)
• Checked 200 log files, 161 edm output root files, 48 DQM output files
• TriggerResults: no differences found

[civanch]

@bsunanda , is it enough to enable extra GEM station?

[bsunanda]

I am waiting to make a new scenario once I put up a version for the new RPC

…

________________________________ From: Vladimir Ivantchenko ***@***.***> Sent: 13 February 2024 21:49 To: cms-sw/cmssw ***@***.***> Cc: Sunanda Banerjee ***@***.***>; Mention ***@***.***> Subject: Re: [cms-sw/cmssw] [GEM] GEMGeometryBuilder update for the 2024 geometry (PR #43948) @bsunanda<https://github.com/bsunanda> , is it enough to enable extra GEM station? — Reply to this email directly, view it on GitHub<#43948 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/ABGMZOQ33FAMTETE4KCTAI3YTOHAZAVCNFSM6AAAAABDF4P7V6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSNBRHEZTGNZSGQ>. You are receiving this because you were mentioned.Message ID: ***@***.***>

[civanch]

+1

@yeckang , please, try to make a backport of this PR to 14_0

[civanch]

@srimanob , please, review this PR

[srimanob]

@yeckang what do I expect from this PR? No change in any workflow?

Note that, @cms-sw/alca-l2 @cms-sw/pdmv-l2 PR test have not moved to 2024. Should it be moved? For example, #43876 is XML of 2024, so we did not really test it until we have it in GT. Thx.

[saumyaphor4252]

Note that, @cms-sw/alca-l2 @cms-sw/pdmv-l2 PR test have not moved to 2024. Should it be moved? For example, #43876 is XML of 2024, so we did not really test it until we have it in GT. Thx.

We'll start updating the GT as soon as we have the tags/payloads from @bsunanda

[srimanob]

+Upgrade

[cmsbuild]

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

[srimanob]

Converging with @civanch that this PR can be signed. No change is expected, but @yeckang please confirm, also prepare the backport to 14_0.

[yeckang]

@srimanob I don't expect any changes from any workflow.
I will prepare the backport.

[antoniovilela]

+1