Phase2 workflows have "_13TeV" in their GlobalTag

[bfonta]

When running (at least some) phase2 workflows, the default auto:phase2_realistic_T33 (using T33 as an example) is concatenated to the _13TeV string, as done here. This happens since all phase2 workflows are using GenSimHLBeamSpot in their ScenToRun attribute (for instance here, taking Run4D121, the latest default geometry, as an example).

Taking the CloseByPGun_Barrel_Front_Run4D121 workflow as an example:

$ runTheMatrix.py -w upgrade -el 34553.0 --show
...
34553.0 CloseByPGun_Barrel_Front_Run4D121_GenSimHLBeamSpot+DigiTrigger_Run4D121+RecoGlobal_Run4D121+HARVESTGlobal_Run4D121+ALCAPhase2_Run4D121 [1]: cmsDriver.py CloseByPGun_Barrel_Front_cfi  -s GEN,SIM -n 10 --conditions auto:phase2_realistic_T33_13TeV --beamspot DBrealisticHLLHC --datatier GEN-SIM --eventcontent FEVTDEBUG --geometry ExtendedRun4D121 --era Phase2C22I13M9 --relval 9000,100 
                                           [2]: cmsDriver.py step2  -s DIGI:pdigi_valid,L1TrackTrigger,L1,L1P2GT,DIGI2RAW,HLT:@relvalRun4 --conditions auto:phase2_realistic_T33 --datatier GEN-SIM-DIGI-RAW -n 10 --eventcontent FEVTDEBUGHLT --geometry ExtendedRun4D121 --era Phase2C22I13M9
                                           [3]: cmsDriver.py step3  -s RAW2DIGI,RECO,RECOSIM,PAT,VALIDATION:@phase2Validation+@miniAODValidation,DQM:@phase2+@miniAODDQM --conditions auto:phase2_realistic_T33 --datatier GEN-SIM-RECO,MINIAODSIM,DQMIO -n 10 --eventcontent FEVTDEBUGHLT,MINIAODSIM,DQM --geometry ExtendedRun4D121 --era Phase2C22I13M9
                                           [4]: cmsDriver.py step4  -s HARVESTING:@phase2Validation+@phase2+@miniAODValidation+@miniAODDQM --conditions auto:phase2_realistic_T33 --mc  --geometry ExtendedRun4D121 --scenario pp --filetype DQM --era Phase2C22I13M9 -n 100 
                                           [5]: cmsDriver.py step5  -s ALCA:SiPixelCalSingleMuonLoose+SiPixelCalSingleMuonTight+TkAlMuonIsolated+TkAlMinBias+MuAlOverlaps+EcalESAlign+TkAlZMuMu+TkAlDiMuonAndVertex+HcalCalHBHEMuonProducerFilter+TkAlUpsilonMuMu+TkAlJpsiMuMu --conditions auto:phase2_realistic_T33 --datatier ALCARECO -n 10 --eventcontent ALCARECO --geometry ExtendedRun4D121 --era Phase2C22I13M9

1 workflows with 5 steps

 -------------------------------------------------------------------------------- 

selected items: [34553.0]

(notice the _13TeV string is added only in the first step).

The configuration in CMSSW is a bit convoluted, with multiple nested imports. It is thus difficult for me to say how exactly the _13TeV addition impacts the workflow configuration.

I would like to know if this is a bug or a feature. If the latter, could you please explain the idea behind it?

Thanks!

---

Seems to be connected to #45685.

[cmsbuild]

cms-bot internal usage

[cmsbuild]

A new Issue was created by @bfonta.

@Dr15Jones, @ftenchini, @makortel, @mandrenguyen, @sextonkennedy, @smuzaffar can you please review it and eventually sign/assign? Thanks.

cms-bot commands are listed here

[makortel]

assign pdmv, alca

[cmsbuild]

New categories assigned: pdmv,alca

@AdrianoDee,@Alejandro1400,@antoniovagnerini,@arunhep,@atpathak,@DickyChant,@JanChyczynski,@miquork,@perrotta you have been requested to review this Pull request/Issue and eventually sign? Thanks

[AdrianoDee]

I think there's a problem with the -e option and --show. 34553.0 wf is not even CloseByPGun. For some reason, the .0 is messing with it.

runTheMatrix.py -w upgrade -el 34533 --show
...
34533.0 WToLNu_14TeV_TuneCP5_pythia8_Run4D121_GenSimHLBeamSpot14+DigiTrigger_Run4D121+RecoGlobal_Run4D121+HARVESTGlobal_Run4D121+ALCAPhase2_Run4D121 [1]: cmsDriver.py WToLNu_14TeV_TuneCP5_pythia8_cfi  -s GEN,SIM -n 10 --conditions auto:phase2_realistic_T33 --beamspot DBrealisticHLLHC --datatier GEN-SIM --eventcontent FEVTDEBUG --geometry ExtendedRun4D121 --era Phase2C22I13M9 --relval 21000,50 
                                           [2]: cmsDriver.py step2  -s DIGI:pdigi_valid,L1TrackTrigger,L1,L1P2GT,DIGI2RAW,HLT:@relvalRun4 --conditions auto:phase2_realistic_T33 --datatier GEN-SIM-DIGI-RAW -n 10 --eventcontent FEVTDEBUGHLT --geometry ExtendedRun4D121 --era Phase2C22I13M9
                                           [3]: cmsDriver.py step3  -s RAW2DIGI,RECO,RECOSIM,PAT,VALIDATION:@phase2Validation+@miniAODValidation,DQM:@phase2+@miniAODDQM --conditions auto:phase2_realistic_T33 --datatier GEN-SIM-RECO,MINIAODSIM,DQMIO -n 10 --eventcontent FEVTDEBUGHLT,MINIAODSIM,DQM --geometry ExtendedRun4D121 --era Phase2C22I13M9
                                           [4]: cmsDriver.py step4  -s HARVESTING:@phase2Validation+@phase2+@miniAODValidation+@miniAODDQM --conditions auto:phase2_realistic_T33 --mc  --geometry ExtendedRun4D121 --scenario pp --filetype DQM --era Phase2C22I13M9 -n 100 
                                           [5]: cmsDriver.py step5  -s ALCA:SiPixelCalSingleMuonLoose+SiPixelCalSingleMuonTight+TkAlMuonIsolated+TkAlMinBias+MuAlOverlaps+EcalESAlign+TkAlZMuMu+TkAlDiMuonAndVertex+HcalCalHBHEMuonProducerFilter+TkAlUpsilonMuMu+TkAlJpsiMuMu --conditions auto:phase2_realistic_T33 --datatier ALCARECO -n 10 --eventcontent ALCARECO --geometry ExtendedRun4D121 --era Phase2C22I13M9

1 workflows with 5 steps

 -------------------------------------------------------------------------------- 

and it's confirmed by --dryRun

runTheMatrix.py -w upgrade -l 34533.0 --dryRun

...

Preparing to run 34533.0 WToLNu_14TeV+Run4D121

# in: /afs/cern.ch/work/a/adiflori/CMSSW_16_0_0_pre3 dryRun for 'cd 34533.0_WToLNu_14TeV+Run4D121
 cmsDriver.py WToLNu_14TeV_TuneCP5_pythia8_cfi  -s GEN,SIM -n 10 --conditions auto:phase2_realistic_T33 --beamspot DBrealisticHLLHC --datatier GEN-SIM --eventcontent FEVTDEBUG --geometry ExtendedRun4D121 --era Phase2C22I13M9 --relval 21000,50 --fileout file:step1.root  > step1_WToLNu_14TeV+Run4D121.log  2>&1
 

# in: /afs/cern.ch/work/a/adiflori/CMSSW_16_0_0_pre3 dryRun for 'cd 34533.0_WToLNu_14TeV+Run4D121
 cmsDriver.py step2  -s DIGI:pdigi_valid,L1TrackTrigger,L1,L1P2GT,DIGI2RAW,HLT:@relvalRun4 --conditions auto:phase2_realistic_T33 --datatier GEN-SIM-DIGI-RAW -n 10 --eventcontent FEVTDEBUGHLT --geometry ExtendedRun4D121 --era Phase2C22I13M9 --filein  file:step1.root  --fileout file:step2.root  > step2_WToLNu_14TeV+Run4D121.log  2>&1
 

# in: /afs/cern.ch/work/a/adiflori/CMSSW_16_0_0_pre3 dryRun for 'cd 34533.0_WToLNu_14TeV+Run4D121
 cmsDriver.py step3  -s RAW2DIGI,RECO,RECOSIM,PAT,VALIDATION:@phase2Validation+@miniAODValidation,DQM:@phase2+@miniAODDQM --conditions auto:phase2_realistic_T33 --datatier GEN-SIM-RECO,MINIAODSIM,DQMIO -n 10 --eventcontent FEVTDEBUGHLT,MINIAODSIM,DQM --geometry ExtendedRun4D121 --era Phase2C22I13M9 --filein  file:step2.root  --fileout file:step3.root  > step3_WToLNu_14TeV+Run4D121.log  2>&1
 

# in: /afs/cern.ch/work/a/adiflori/CMSSW_16_0_0_pre3 dryRun for 'cd 34533.0_WToLNu_14TeV+Run4D121
 cmsDriver.py step4  -s HARVESTING:@phase2Validation+@phase2+@miniAODValidation+@miniAODDQM --conditions auto:phase2_realistic_T33 --mc  --geometry ExtendedRun4D121 --scenario pp --filetype DQM --era Phase2C22I13M9 -n 100  --filein file:step3_inDQM.root --fileout file:step4.root  > step4_WToLNu_14TeV+Run4D121.log  2>&1
 

# in: /afs/cern.ch/work/a/adiflori/CMSSW_16_0_0_pre3 dryRun for 'cd 34533.0_WToLNu_14TeV+Run4D121
 cmsDriver.py step5  -s ALCA:SiPixelCalSingleMuonLoose+SiPixelCalSingleMuonTight+TkAlMuonIsolated+TkAlMinBias+MuAlOverlaps+EcalESAlign+TkAlZMuMu+TkAlDiMuonAndVertex+HcalCalHBHEMuonProducerFilter+TkAlUpsilonMuMu+TkAlJpsiMuMu --conditions auto:phase2_realistic_T33 --datatier ALCARECO -n 10 --eventcontent ALCARECO --geometry ExtendedRun4D121 --era Phase2C22I13M9 --filein file:step3.root --fileout file:step5.root  > step5_WToLNu_14TeV+Run4D121.log  2>&1
 
34533.0_WToLNu_14TeV+Run4D121 Step0-PASSED Step1-PASSED Step2-PASSED Step3-PASSED Step4-PASSED  - time date Mon Dec 15 10:53:25 2025-date Mon Dec 15 10:53:25 2025; exit: 0 0 0 0 0
1 1 1 1 1 tests passed, 0 0 0 0 0 failed

[AdrianoDee]

While with 34553.0

runTheMatrix.py -w upgrade -el 34553.0 --show

...

34553.0 CloseByPGun_Barrel_Front_Run4D121_GenSimHLBeamSpot+DigiTrigger_Run4D121+RecoGlobal_Run4D121+HARVESTGlobal_Run4D121+ALCAPhase2_Run4D121 [1]: cmsDriver.py CloseByPGun_Barrel_Front_cfi  -s GEN,SIM -n 10 --conditions auto:phase2_realistic_T33_13TeV --beamspot DBrealisticHLLHC --datatier GEN-SIM --eventcontent FEVTDEBUG --geometry ExtendedRun4D121 --era Phase2C22I13M9 --relval 9000,100 
                                           [2]: cmsDriver.py step2  -s DIGI:pdigi_valid,L1TrackTrigger,L1,L1P2GT,DIGI2RAW,HLT:@relvalRun4 --conditions auto:phase2_realistic_T33 --datatier GEN-SIM-DIGI-RAW -n 10 --eventcontent FEVTDEBUGHLT --geometry ExtendedRun4D121 --era Phase2C22I13M9
                                           [3]: cmsDriver.py step3  -s RAW2DIGI,RECO,RECOSIM,PAT,VALIDATION:@phase2Validation+@miniAODValidation,DQM:@phase2+@miniAODDQM --conditions auto:phase2_realistic_T33 --datatier GEN-SIM-RECO,MINIAODSIM,DQMIO -n 10 --eventcontent FEVTDEBUGHLT,MINIAODSIM,DQM --geometry ExtendedRun4D121 --era Phase2C22I13M9
                                           [4]: cmsDriver.py step4  -s HARVESTING:@phase2Validation+@phase2+@miniAODValidation+@miniAODDQM --conditions auto:phase2_realistic_T33 --mc  --geometry ExtendedRun4D121 --scenario pp --filetype DQM --era Phase2C22I13M9 -n 100 
                                           [5]: cmsDriver.py step5  -s ALCA:SiPixelCalSingleMuonLoose+SiPixelCalSingleMuonTight+TkAlMuonIsolated+TkAlMinBias+MuAlOverlaps+EcalESAlign+TkAlZMuMu+TkAlDiMuonAndVertex+HcalCalHBHEMuonProducerFilter+TkAlUpsilonMuMu+TkAlJpsiMuMu --conditions auto:phase2_realistic_T33 --datatier ALCARECO -n 10 --eventcontent ALCARECO --geometry ExtendedRun4D121 --era Phase2C22I13M9

1 workflows with 5 steps

 -------------------------------------------------------------------------------- 

[bfonta]

Any update on understanding the underlying bug?