Run3-gex175X Backport #43876 to CMSSW version 14_0_X the changes for te 2024 version of GE21 geometry

[bsunanda]

PR description:

Backport #43876 to CMSSW version 14_0_X the changes for te 2024 version of GE21 geometry

PR validation:

Use the runTheMatrix test workflows

If this PR is a backport please specify the original PR and why you need to backport that PR. If this PR will be backported please specify to which release cycle the backport is meant for:

Backporting #43876 from the master which is already integrated

[cmsbuild]

A new Pull Request was created by @bsunanda (Sunanda Banerjee) for CMSSW_14_0_X.

It involves the following packages:

• Geometry/MuonCommonData (geometry)

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

cms-bot commands are listed here

[cmsbuild]

cms-bot internal usage

[bsunanda]

@cmsbuild Please test

[cmsbuild]

+1

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

Comparison Summary

Summary:

• You potentially added 2 lines to the logs
• Reco comparison results: 50 differences found in the comparisons
• DQMHistoTests: Total files compared: 48
• DQMHistoTests: Total histograms compared: 3248626
• DQMHistoTests: Total failures: 1186
• DQMHistoTests: Total nulls: 0
• DQMHistoTests: Total successes: 3247418
• 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

[bsunanda]

+geometry

[cmsbuild]

This pull request is fully signed and it will be integrated in one of the next CMSSW_14_0_X IBs (tests are also fine) and once validation in the development release cycle CMSSW_14_1_X is complete. This pull request will now be reviewed by the release team before it's merged. @rappoccio, @antoniovilela, @sextonkennedy (and backports should be raised in the release meeting by the corresponding L2)

[antoniovilela]

hold

• While this is further discussed.

[cmsbuild]

Pull request has been put on hold by @antoniovilela
They need to issue an unhold command to remove the hold state or L1 can unhold it for all

[civanch]

@antoniovilela , there is no sense to hold this PR, because it is done only in order of consistency between GT and XML detector description. In production GT is used but if at any moment in time a test GT/XML will be needed for any reason there will be a confusion. It is why we are trying to backport XML modifications like this. Here extra chambers installed during YETS are added to geometry, this chambers will not be used for analysis of data but only to control their performance.

[antoniovilela]

@antoniovilela , there is no sense to hold this PR, because it is done only in order of consistency between GT and XML detector description. In production GT is used but if at any moment in time a test GT/XML will be needed for any reason there will be a confusion. It is why we are trying to backport XML modifications like this. Here extra chambers installed during YETS are added to geometry, this chambers will not be used for analysis of data but only to control their performance.

We have asked and are waiting for a green light from PPD, this is why it is on hold.
Thanks.

[antoniovilela]

unhold

[cmsbuild]

This pull request is fully signed and it will be integrated in one of the next CMSSW_14_0_X IBs (tests are also fine) and once validation in the development release cycle CMSSW_14_1_X is complete. This pull request will now be reviewed by the release team before it's merged. @sextonkennedy, @antoniovilela, @rappoccio (and backports should be raised in the release meeting by the corresponding L2)

[antoniovilela]

We can discuss this PR in the ORP meeting.

[jordan-martins]

+1

[bsunanda]

@antoniovilela, @rappoccio Please merge this. I need to use the IB to backport the next version (scenario definition)

[rappoccio]

+1