Run3-hcx378X Backport #46467 to CMSSW_14_1_X which makes RPD as a valid detector in the 2023 scenario

[bsunanda]

PR description:

Backport #46467 to CMSSW_14_1_X which makes RPD as a valid detector in the 2023 scenario

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:

Backport of #46467

[cmsbuild]

A new Pull Request was created by @bsunanda for CMSSW_14_1_X.

It involves the following packages:

• Configuration/Geometry (upgrade, geometry)
• Geometry/CMSCommonData (upgrade, geometry)

@Dr15Jones, @Moanwar, @bsunanda, @civanch, @cmsbuild, @kpedro88, @makortel, @mdhildreth, @srimanob, @subirsarkar can you please review it and eventually sign? Thanks.
@Martin-Grunewald, @fabiocos, @martinamalberti, @missirol, @slomeo, @vargasa this is something you requested to watch as well.
@antoniovilela, @mandrenguyen, @rappoccio, @sextonkennedy you are the release manager for this.

cms-bot commands are listed here

[cmsbuild]

cms-bot internal usage

[mandrenguyen]

Please explain why this is needed in 14_1_X which is a closed release cycle

[bsunanda]

I understood from yesterday's AlCaReco meeting that there is a plan to ReReco 2023 HI data using 14_1_X. In 14_1_X, RPD is an invalid detector. So if 14_1_X is used to do ReReco, one needs this PR to be included.

…

________________________________ From: Matthew Nguyen ***@***.***> Sent: 22 October 2024 12:03 To: cms-sw/cmssw ***@***.***> Cc: Sunanda Banerjee ***@***.***>; Mention ***@***.***> Subject: Re: [cms-sw/cmssw] Run3-hcx378X Backport #46467 to CMSSW_14_1_X which makes RPD as a valid detector in the 2023 scenario (PR #46468) Please explain why this is needed in 14_1_X which is a closed release cycle — Reply to this email directly, view it on GitHub<#46468 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/ABGMZOTCBHYZJXSTF2NATQDZ4XWSXAVCNFSM6AAAAABQLWCE42VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDIMRYGM3TCMRSHA>. You are receiving this because you were mentioned.Message ID: ***@***.***>

[mandrenguyen]

hold
Since RPD is not being reconstructed in 2024 data presumably it is not needed in 2023 either.

[cmsbuild]

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