Update BeamSpot in Run3 MC GTs + swap Run3RoundOptics25ns13TeVLowSigmaZ with Realistic25ns13p6TeVEarly2022Collision vtx smearing

[mmusich]

PR description:

PR #38692 changed the default Beam Spot in the Run-3 Global Tag , but it was thn now out-of-synch with the vertex smearing assumed for the Run-3 RelVal workflows, even if it is correct for the 2022 physics MC.
This PR fixes the problem by making Realistic25ns13p6TeVEarly2022Collision the default for Run-3 relval workflows and wherever it is necessary to change it in standalone configurations together with the BeamSpot updates in the Run-3 MC GlobalTags.
In this PR we add:

• the new BeamSpot for Run 3 collisions at 13.6 TeV in all Run3 MC GTs
  • Compatible with the VtxSmearing parameters Realistic25ns13p6TeVEarly2022Collision introduced in Add VtxSmearing scenario for Run 3 early data at 13.6 TeV #38616 and fixed at Fix VtxSmearing parameters for 2022 Run 3 MC #38825 (after using wrong pixel barycenter positions, as described in this CMS Talk Post
  • The new reco BeamSpot was derived from the RelVal produced in JIRA-PDMVRELVALS-156

The new BeamSpot tags are:

• BeamSpotObjects_Realistic25ns_13p6TeVCollisions_Early2022_v3_mc
• BeamSpotOnlineObjects_Realistic25ns_13p6TeVCollisions_Early2022_v2_mc

The GT diffs are:

• MC Run3 realistic https://cms-conddb.cern.ch/cmsDbBrowser/diff/Prod/gts/125X_mcRun3_2022_realistic_v2/125X_mcRun3_2022_realistic_v3
• MC Run3 cosmics realistic https://cms-conddb.cern.ch/cmsDbBrowser/diff/Prod/gts/125X_mcRun3_2022cosmics_realistic_deco_v2/125X_mcRun3_2022cosmics_realistic_deco_v3
• MC Run3 realistic HI https://cms-conddb.cern.ch/cmsDbBrowser/diff/Prod/gts/125X_mcRun3_2022_realistic_HI_v2/125X_mcRun3_2022_realistic_HI_v3
• MC Run3 2023 realistic https://cms-conddb.cern.ch/cmsDbBrowser/diff/Prod/gts/125X_mcRun3_2023_realistic_v2/125X_mcRun3_2023_realistic_v3
• MC Run3 2024 realistic https://cms-conddb.cern.ch/cmsDbBrowser/diff/Prod/gts/125X_mcRun3_2024_realistic_v2/125X_mcRun3_2024_realistic_v3

PR validation:

cmssw compiles

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:

to be backported together with other updates to 12.4.X

cc:
@cms-sw/alca-l2

[cmsbuild]

+code-checks

Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-38760/31084

• This PR adds an extra 80KB to repository

• There are other open Pull requests which might conflict with changes you have proposed:

  • File Configuration/PyReleaseValidation/python/relval_steps.py modified in PR(s): Add Run3 ALCA Express/Prompt workflow #38681, Ari changes #38758, Reorganize FastSim Run3 workflow #38660, Don't recluster jets in HI miniAOD for Run 3  #38711, Add Run3 wfs (NanoV10) #38733
  • File Configuration/PyReleaseValidation/python/upgradeWorkflowComponents.py modified in PR(s): Clean up Phase-2 geometry (Up to D85) #38702, Reorganize FastSim Run3 workflow #38660, Add Run3 wfs (NanoV10) #38733, Add miniAODDQM FastSim Validation #38736, Add run3 tracking low pu era #33532

[cmsbuild]

A new Pull Request was created by @mmusich (Marco Musich) for master.

It involves the following packages:

• Configuration/PyReleaseValidation (pdmv, upgrade)
• EventFilter/CSCRawToDigi (reconstruction)
• Geometry/CMSCommonData (geometry, upgrade)
• Geometry/HcalCommonData (geometry)
• Geometry/TrackerCommonData (geometry)
• Geometry/VeryForwardData (geometry)
• SimG4CMS/Calo (simulation)
• SimG4CMS/ShowerLibraryProducer (simulation)
• SimG4Core/Configuration (simulation)

@civanch, @Dr15Jones, @jordan-martins, @bsunanda, @makortel, @bbilin, @ianna, @mdhildreth, @cmsbuild, @AdrianoDee, @srimanob, @clacaputo, @kskovpen, @jpata can you please review it and eventually sign? Thanks.
@thomreis, @felicepantaleo, @kpedro88, @ghugo83, @Martin-Grunewald, @bsunanda, @grzanka, @trtomei, @slomeo, @venturia, @vargasa, @makortel, @JanFSchulte, @missirol, @simonepigazzini, @beaucero, @barvic, @fabferro, @rovere, @VinInn, @ptcox, @mmusich, @mtosi, @fabiocos this is something you requested to watch as well.
@perrotta, @dpiparo, @qliphy, @rappoccio you are the release manager for this.

cms-bot commands are listed here

[mmusich]

please test

[perrotta]

@mmusich I have prepared the revert of #38692 in #38762
Since I doubt you'll be able to collect all needed signatures by this evening, let me revert that PR now: you can add the new GTs in this PR of yours, so that all changes can be merged together

[perrotta]

@mmusich @francescobrivio please add back here the commit from #38692 that was reverted in the master, see #38762 (comment)

[mmusich]

please add back here the commit from #38692 that was reverted in the master, see #38762 (comment)

done.

[cmsbuild]

+code-checks

Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-38760/31089

• This PR adds an extra 80KB to repository

• There are other open Pull requests which might conflict with changes you have proposed:

  • File Configuration/AlCa/python/autoCond.py modified in PR(s): Ari changes #38758
  • File Configuration/PyReleaseValidation/python/relval_steps.py modified in PR(s): Add Run3 ALCA Express/Prompt workflow #38681, Ari changes #38758, Reorganize FastSim Run3 workflow #38660, Don't recluster jets in HI miniAOD for Run 3  #38711, Add Run3 wfs (NanoV10) #38733
  • File Configuration/PyReleaseValidation/python/upgradeWorkflowComponents.py modified in PR(s): Clean up Phase-2 geometry (Up to D85) #38702, Reorganize FastSim Run3 workflow #38660, Add Run3 wfs (NanoV10) #38733, Add miniAODDQM FastSim Validation #38736, Add run3 tracking low pu era #33532

[srimanob]

+Upgrade

#39041 is OK now.

[tvami]

@cms-sw/simulation-l2 can you please re-sign?

[mmusich]

test parameters:

• pull_request = Update PU for Run3 wfs #39041

[mmusich]

@cmsbuild, please test

[civanch]

+1

[cmsbuild]

+1

Summary: https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-5b625f/27074/summary.html
COMMIT: d7e814e
CMSSW: CMSSW_12_5_X_2022-08-24-2300/el8_amd64_gcc10
User test area: For local testing, you can use /cvmfs/cms-ci.cern.ch/week1/cms-sw/cmssw/38760/27074/install.sh to create a dev area with all the needed externals and cmssw changes.

Comparison Summary

Summary:

• No significant changes to the logs found
• ROOTFileChecks: Some differences in event products or their sizes found
• Reco comparison results: 18500 differences found in the comparisons
• DQMHistoTests: Total files compared: 51
• DQMHistoTests: Total histograms compared: 3693084
• DQMHistoTests: Total failures: 94326
• DQMHistoTests: Total nulls: 2
• DQMHistoTests: Total successes: 3598734
• DQMHistoTests: Total skipped: 22
• DQMHistoTests: Total Missing objects: 0
• DQMHistoSizes: Histogram memory added: 3.007 KiB( 50 files compared)
• DQMHistoSizes: changed ( 11834.0 ): 3.011 KiB SiStrip/MechanicalView
• DQMHistoSizes: changed ( 312.0 ): -0.004 KiB MessageLogger/Warnings
• Checked 212 log files, 49 edm output root files, 51 DQM output files
• TriggerResults: found differences in 8 / 50 workflows

[mmusich]

unhold

• the last round of tests includes also updated PU libraries;
• this PR must be merged in the same IB as Update PU for Run3 wfs #39041

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

[mmusich]

on a side note, it's sad that issue #38980 is not solved yet, as it would have been good to check the differences in more detail at https://tinyurl.com/2jkb6wmw

[mmusich]

some observations from the relmon for wf 11834.0 (TTBar 2021, 14TeV + PU)

the off-centering of the new BeamSpot is clearly visible:

the quality of the IP w.r.t. BeamSpot is similar:

but for some reason we are reconstructing substantially less (?) tracks:

the same effect is NOT visible in the non-PU wf 11634.0 (TTbar 2021, 14TeV)

[perrotta]

+1