Adding Golden Workflows for 2022 and 2023 Data

[AdrianoDee]

PR description:

Following the setup introduced in #45055 for 2024 data wfs, this PR proposes to add also the equivalent set of workflows for 2022 and 2023 data. As in the parent PR a smaller set of wfs is added to relval_standard.py just to keep testing the machinery in the IBs, while the higher stats wfs are in relval_data_highstats.py.

PR validation:

E.g. runTheMatrix.py -w data -l 2022.000005, 2023.001005.

[cmsbuild]

cms-bot internal usage

[cmsbuild]

+code-checks

Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-45836/41579

[cmsbuild]

A new Pull Request was created by @AdrianoDee for master.

It involves the following packages:

• Configuration/PyReleaseValidation (pdmv, upgrade)

@AdrianoDee, @cmsbuild, @kskovpen, @miquork, @srimanob, @subirsarkar, @sunilUIET can you please review it and eventually sign? Thanks.
@Martin-Grunewald, @fabiocos, @makortel, @missirol, @slomeo 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]

+code-checks

Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-45836/41581

[cmsbuild]

Pull request #45836 was updated. @AdrianoDee, @cmsbuild, @kskovpen, @miquork, @srimanob, @subirsarkar, @sunilUIET can you please check and sign again.

[cmsbuild]

+code-checks

Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-45836/41593

[cmsbuild]

Pull request #45836 was updated. @AdrianoDee, @cmsbuild, @kskovpen, @miquork, @srimanob, @subirsarkar, @sunilUIET can you please check and sign again.

[AdrianoDee]

test parameters:

• workflows = 2022.000001,2022.001001,2022.100001,2022.101001,2023.000001,2023.001001,2023.100001,2023.101001

[AdrianoDee]

please test

[cmsbuild]

+code-checks

Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-45836/41595

[cmsbuild]

Pull request #45836 was updated. @AdrianoDee, @cmsbuild, @kskovpen, @miquork, @srimanob, @subirsarkar, @sunilUIET can you please check and sign again.

[AdrianoDee]

please test

[cmsbuild]

+1

Size: This PR adds an extra 72KB to repository
Summary: https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-14f195/41212/summary.html
COMMIT: 29dc453
CMSSW: CMSSW_14_2_X_2024-09-01-0000/el8_amd64_gcc12
User test area: For local testing, you can use /cvmfs/cms-ci.cern.ch/week1/cms-sw/cmssw/45836/41212/install.sh to create a dev area with all the needed externals and cmssw changes.

Comparison Summary

Summary:

• You potentially added 4 lines to the logs
• Reco comparison results: 105 differences found in the comparisons
• DQMHistoTests: Total files compared: 44
• DQMHistoTests: Total histograms compared: 3328315
• DQMHistoTests: Total failures: 2855
• DQMHistoTests: Total nulls: 0
• DQMHistoTests: Total successes: 3325440
• DQMHistoTests: Total skipped: 20
• DQMHistoTests: Total Missing objects: 0
• DQMHistoSizes: Histogram memory added: 0.0 KiB( 43 files compared)
• Checked 193 log files, 163 edm output root files, 44 DQM output files
• TriggerResults: no differences found

[AdrianoDee]

+pdmv

[srimanob]

Hi @AdrianoDee
Is it by intention that you run 2023 data with GRun in HLT step, e.g. here?

Thx.

[AdrianoDee]

Hi @srimanob, yes, this was a trick to continue testing the 2024 menu on 2023 samples until 2024 RelVals were out. Now we can most probably move this to Fake (I imagine, @cms-sw/hlt-l2 ?). But this is valid in general for 2023 data wfs.

[mmusich]

Now we can most probably move this to Fake (I imagine, @cms-sw/hlt-l2 ?). But this is valid in general for 2023 data wfs.

yes, provided we have workflows that run GRun on 2024 in master, you can move 2023 to Fake2.

[srimanob]

Hi @AdrianoDee
Do you want to fix, or we let's it go? I am fine in either ways.

[AdrianoDee]

Hi @srimanob I'd split it into another cleanup PR.

[srimanob]

+Upgrade

There will be follow up cleanup PR.

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

[mandrenguyen]

+1