Using CP5 tune generator fragments for Phase2/Run3 RelVal samples

[siddhesh86]

PR includes

1. Added a few generator fragments (e.g. TTbar, MinBias at 14TeV) with CP5 tune, intended to use for phase2 RelVal production in CMSSW release validation
2. Added new generator fragments needed for phase2 RelVal production in CMSSW release validation
3. Added corresponding entries for 1) and 2) in the RelVa submission macros (upgradeWorkflowComponents.py, relval_steps.py)
4. MatrixInjector.py: wmsplit set to 1 for high PU RelVal submission for recent detector configurations (D35, D49 etc). It is needed to run highPU phase2 workflows smoothly in the computing system.

[cmsbuild]

The code-checks are being triggered in jenkins.

[cmsbuild]

-code-checks

Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-28880/13655

• 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): New relvals workflows for JME customized nanoaod #28857

Code check has found code style and quality issues which could be resolved by applying following patch(s)

• code-checks:
  https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-28880/13655/code-checks.patch
  e.g. curl https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-28880/13655/code-checks.patch | patch -p1
  You can also run scram build code-checks to apply code checks directly

[smuzaffar]

@siddhesh86 , can you please resolve the conflit?

[siddhesh86]

@smuzaffar, the conflict has been resolved. Thanks.

[cmsbuild]

The code-checks are being triggered in jenkins.

[cmsbuild]

+code-checks

Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-28880/13687

• This PR adds an extra 52KB 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): New relvals workflows for JME customized nanoaod #28857

[cmsbuild]

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

It involves the following packages:

Configuration/Generator
Configuration/PyReleaseValidation

@SiewYan, @pgunnell, @efeyazgan, @mkirsano, @chayanit, @zhenhu, @kpedro88, @cmsbuild, @agrohsje, @alberto-sanchez, @qliphy can you please review it and eventually sign? Thanks.
@Martin-Grunewald, @makortel this is something you requested to watch as well.
@davidlange6, @silviodonato, @fabiocos you are the release manager for this.

cms-bot commands are listed here

[kpedro88]

@efeyazgan, @agrohsje, @alberto-sanchez, @qliphy do we no longer put the tune name in the fragment? This seems potentially confusing to me.

[efeyazgan]

@kpedro88 yes, we should definitely have the tune names in the fragments. @siddhesh86 please update the fragments.

[chayanit]

@silviodonato I would like to have this PR in 11_1_0_pre3 if possible. I was traveling so didn't join release meeting today, when will you create pre3? @siddhesh86 could you make change soon?

[silviodonato]

urgent

[silviodonato]

@chayanit I will try to include it. It depends on how much time will take the update and review of this PR.

[siddhesh86]

@chayanit, @silviodonato, @kpedro88, @efeyazgan:
The suggested corrections in the generator fragments including tune name are implemented and another PR (#28932) is created including these corrections. Please continue/move to the PR28932.
Thank you.

[kpedro88]

please close