limit # events to process in 0T PU workflows to avoid exploding in tracking time

[mmusich]

PR description:

In response to #36492. Title says it all.

PR validation:

$ runTheMatrix.py -nel 11834.24
11834.24 2021PU_0T+TTbar_14TeV_TuneCP5_GenSim+DigiPU+RecoNanoPU+HARVESTNanoPU [1]: cmsDriver.py TTbar_14TeV_TuneCP5_cfi  -s GEN,SIM -n 1 --conditions auto:phase1_2021_realistic_0T --beamspot Run3RoundOptics25ns13TeVLowSigmaZ --datatier GEN-SIM --eventcontent FEVTDEBUG --geometry DB:Extended --era Run3 --magField 0T --relval 9000,100 
                                           [2]: cmsDriver.py step2  -s DIGI:pdigi_valid,L1,DIGI2RAW,HLT:@relval2021 --conditions auto:phase1_2021_realistic_0T --datatier GEN-SIM-DIGI-RAW -n 1 --eventcontent FEVTDEBUGHLT --geometry DB:Extended --era Run3 --magField 0T
                                           [3]: cmsDriver.py step3  -s RAW2DIGI,L1Reco,RECO,RECOSIM,EI,PAT,NANO,VALIDATION:@standardValidation+@miniAODValidation,DQM:@standardDQM+@ExtraHLT+@miniAODDQM+@nanoAODDQM --conditions auto:phase1_2021_realistic_0T --datatier GEN-SIM-RECO,MINIAODSIM,NANOAODSIM,DQMIO -n 1 --eventcontent RECOSIM,MINIAODSIM,NANOEDMAODSIM,DQM --geometry DB:Extended --era Run3 --magField 0T
                                           [4]: cmsDriver.py step4  -s HARVESTING:@standardValidation+@standardDQM+@ExtraHLT+@miniAODValidation+@miniAODDQM+@nanoAODDQM --conditions auto:phase1_2021_realistic_0T --mc  --geometry DB:Extended --scenario pp --filetype DQM --era Run3 -n 1 --magField 0T

now 11834.24 has -n 1 in every step.

if this PR is a backport please specify the original PR and why you need to backport that PR:

N/A

[mmusich]

test parameters:

• workflows = 11834.24

[cmsbuild]

+code-checks

Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-36503/27381

• This PR adds an extra 48KB 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): Remove Event Interpretation (EI) from relval steps #36465, Update pileup scenario in RelVals #36388, Hydjet++ 2.4.3 integration #36316

[cmsbuild]

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

It involves the following packages:

• Configuration/PyReleaseValidation (pdmv, upgrade)

@jordan-martins, @bbilin, @wajidalikhan, @cmsbuild, @AdrianoDee, @srimanob, @kskovpen can you please review it and eventually sign? Thanks.
@makortel, @kpedro88, @Martin-Grunewald, @missirol, @fabiocos, @slomeo this is something you requested to watch as well.
@perrotta, @dpiparo, @qliphy you are the release manager for this.

cms-bot commands are listed here

[mmusich]

@cmsbuild, please test

[kpedro88]

@mmusich please don't add special workflow modifications in random places in relval_steps.py where nobody will ever find or remember them.

The actual issue here seems to be:

cmssw/Configuration/PyReleaseValidation/python/upgradeWorkflowComponents.py

Line 888 in cfc6395

stepDict[stepName][k] = merge([{'-n':'1','--magField':'0T','--conditions':myGT}, stepDict[step][k]])

cmssw/Configuration/PyReleaseValidation/python/relval_steps.py

Line 3489 in cfc6395

PUDataSets[ds]={'-n':10,'--pileup':'AVE_35_BX_25ns','--pileup_input':'das:/RelValMinBias_13/%s/GEN-SIM'%(name,)}

cmssw/Configuration/PyReleaseValidation/python/relval_steps.py

Line 3684 in cfc6395

specialWF.setup(upgradeStepDict, k, upgradeProperties[year][k])

cmssw/Configuration/PyReleaseValidation/python/relval_steps.py

Line 3695 in cfc6395

upgradeStepDict[stepNamePU][k]=merge([PUDataSets[k2],upgradeStepDict[stepName][k]])

cmssw/Configuration/PyReleaseValidation/python/relval_steps.py

Line 3698 in cfc6395

specialWF.setupPU(upgradeStepDict, k, upgradeProperties[year][k])

i.e., the '-n':'1' setting is overridden by the PUDataSets contents.

Please see #36505 for an appropriate fix.

[mmusich]

@kpedro88 I was not aware of this setupPU function.