Update 2025 MC GT in autoCond - CMSSW_15_1_X

[perrotta]

PR description:

This PR ports to autoCond the 2025 realistic MC GTs after the following updates:

• The 2025 MC GT was synchronized with the updates already integrated in 150X_mcRun3_2025_realistic_v14 and not yet ported to the 151X version of it; moreover, the fixed SiPixelStatus tags are also integrated

To give some more detail:

• 151X_mcRun3_2025_realistic_v5 - Synchronize with 150X_mcRun3_2025_realistic_v14, i.e.:
  • Update JetCorrector parameters:
    https://cms-talk.web.cern.ch/t/call-for-conditions-for-the-spring25-mc-global-tag/119464/33
  • Update SiStrip bad channels as in https://cms-talk.web.cern.ch/t/call-for-conditions-for-the-spring25-mc-global-tag/119464/37
  • Update SPixel and Pixel Alignment tags as in https://cms-talk.web.cern.ch/t/call-for-conditions-for-the-spring25-mc-global-tag/119464/38
  • (SiPixelStatus will be synchronized separalely)
• 151X_mcRun3_2025_realistic_v6
  • Update SiPixelStatusScenario as in https://cms-talk.web.cern.ch/t/call-for-conditions-for-the-winter26-mc-global-tag/140278/18

The differences with the GTs previously in confDB follows:

• Diff between 151X_mcRun3_2025_realistic_v6 and 151X_mcRun3_2025_realistic_v4

PR validation:

Tested in master

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:

Partial backport of #50274

[perrotta]

please test

[cmsbuild]

A new Pull Request was created by @perrotta for CMSSW_15_1_X.

It involves the following packages:

• Configuration/AlCa (alca)

@Alejandro1400, @JanChyczynski, @arunhep, @atpathak, @perrotta can you please review it and eventually sign? Thanks.
@Martin-Grunewald, @fabiocos, @mmusich, @rsreds, @tocheng, @yuanchao this is something you requested to watch as well.
@ftenchini, @mandrenguyen, @sextonkennedy you are the release manager for this.

cms-bot commands are listed here

• Backported from Update 2025 and 2026 MC Gts #50274

[cmsbuild]

cms-bot internal usage

[cmsbuild]

+1

Size: This PR adds an extra 20KB to repository
Summary: https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-534def/51796/summary.html
COMMIT: c3b7dc1
CMSSW: CMSSW_15_1_X_2026-03-05-2300/el8_amd64_gcc12
User test area: For local testing, you can use /cvmfs/cms-ci.cern.ch/week1/cms-sw/cmssw/50324/51796/install.sh to create a dev area with all the needed externals and cmssw changes.

Comparison Summary

Summary:

• You potentially added 749 lines to the logs
• Reco comparison results: 6930 differences found in the comparisons
• DQMHistoTests: Total files compared: 50
• DQMHistoTests: Total histograms compared: 4124047
• DQMHistoTests: Total failures: 88953
• DQMHistoTests: Total nulls: 2
• DQMHistoTests: Total successes: 4035072
• DQMHistoTests: Total skipped: 20
• DQMHistoTests: Total Missing objects: 0
• DQMHistoSizes: Histogram memory added: -1.842 KiB( 49 files compared)
• DQMHistoSizes: changed ( 17034.0 ): -1.842 KiB SiStrip/MechanicalView
• Checked 215 log files, 184 edm output root files, 50 DQM output files
• TriggerResults: found differences in 2 / 48 workflows

Max Memory Comparisons exceeding threshold

@cms-sw/core-l2 , I found 3 workflow step(s) with memory usage exceeding the error threshold:

Expand to see workflows ...

• Error: Workflow 16834.0_TTbar_14TeV+2025 step2 max memory diff 367.8 exceeds +/- 90.0 MiB
• Error: Workflow 17034.0_TTbar_14TeV+2025PU step2 max memory diff 393.7 exceeds +/- 90.0 MiB
• Error: Workflow 17034.0_TTbar_14TeV+2025PU step3 max memory diff 115.9 exceeds +/- 90.0 MiB

[perrotta]

backport of #50274

[perrotta]

+alca

• Nice to have in CMSSW_15_1_X, so that the latest version of the 2025 MC GTs can be kept tested in the IBs (even though CMSSW_15_1_X will not be used for pp MC productions)

[cmsbuild]

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

[mandrenguyen]

+1