Phase2-HGX350X Add a new workflow for a version containing V18 definition of HGCal

[bsunanda]

PR description:

Add a new workflow for a version containing V18 definition of HGCal

PR validation:

Use runTheMatrix test workflow 27234.0 designed for this scenario 2026D104

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:

Nothing special

[cmsbuild]

+code-checks

Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-43466/38019

• This PR adds an extra 56KB to repository

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

  • File Configuration/Geometry/README.md modified in PR(s): ETL Geometry V8 #43407, Run3-gex174 Add RPD in the latest version of 2023 Gemetry as requested by the ZDC group for the next HI simulation effort #43418
  • File Configuration/Geometry/python/GeometryDD4hepExtended2026D104Reco_cff.py modified in PR(s): ETL Geometry V8 #43407
  • File Configuration/Geometry/python/GeometryDD4hepExtended2026D104_cff.py modified in PR(s): ETL Geometry V8 #43407
  • File Configuration/Geometry/python/GeometryExtended2026D104Reco_cff.py modified in PR(s): ETL Geometry V8 #43407
  • File Configuration/Geometry/python/GeometryExtended2026D104_cff.py modified in PR(s): ETL Geometry V8 #43407
  • File Configuration/Geometry/python/dict2026Geometry.py modified in PR(s): revert PR 40443 w/o introducing bricked pixels #42454, ETL Geometry V8 #43407
  • File Configuration/PyReleaseValidation/python/relval_2026.py modified in PR(s): Guard for No Digis for Phase2 and Patatrack NuGun #41255, ETL Geometry V8 #43407
  • File Configuration/PyReleaseValidation/python/upgradeWorkflowComponents.py modified in PR(s): Add run3 tracking low pu era #33532, Porting Pixel Tracks to Alpaka [Not to Merge]  #41117, Guard for No Digis for Phase2 and Patatrack NuGun #41255, Add Phase-2 workflow with Phase-2 ECal trigger primitive, also with ECal component #43057, Pixel Alpaka Migration: Configs and Fixes [VII] #43294, ETL Geometry V8 #43407
  • File Configuration/StandardSequences/python/GeometryConf.py modified in PR(s): ETL Geometry V8 #43407
  • File Geometry/CMSCommonData/data/dd4hep/cmsExtendedGeometry2026D104.xml modified in PR(s): ETL Geometry V8 #43407
  • File Geometry/CMSCommonData/python/cmsExtendedGeometry2026D104XML_cfi.py modified in PR(s): ETL Geometry V8 #43407

[cmsbuild]

A new Pull Request was created by @bsunanda (Sunanda Banerjee) for master.

It involves the following packages:

• Configuration/Geometry (geometry, upgrade)
• Configuration/PyReleaseValidation (pdmv, upgrade)
• Configuration/StandardSequences (operations)
• Geometry/CMSCommonData (geometry, upgrade)
• Geometry/HGCalCommonData (geometry, upgrade)

@sunilUIET, @Dr15Jones, @cmsbuild, @rappoccio, @antoniovilela, @bsunanda, @civanch, @davidlange6, @makortel, @fabiocos, @mdhildreth, @srimanob, @AdrianoDee, @miquork can you please review it and eventually sign? Thanks.
@VourMa, @sameasy, @rovere, @mmusich, @vargasa, @felicepantaleo, @VinInn, @makortel, @GiacomoSguazzoni, @fabiocos, @dgulhan, @Martin-Grunewald, @missirol, @mtosi, @slomeo, @JanFSchulte this is something you requested to watch as well.
@antoniovilela, @sextonkennedy, @rappoccio you are the release manager for this.

cms-bot commands are listed here

[bsunanda]

@cmsbuild Please test

[cmsbuild]

+1

Summary: https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-204a05/36237/summary.html
COMMIT: 5c23d2b
CMSSW: CMSSW_14_0_X_2023-11-30-2300/el8_amd64_gcc12
User test area: For local testing, you can use /cvmfs/cms-ci.cern.ch/week1/cms-sw/cmssw/43466/36237/install.sh to create a dev area with all the needed externals and cmssw changes.

Comparison Summary

Summary:

• You potentially added 63 lines to the logs
• Reco comparison results: 3 differences found in the comparisons
• DQMHistoTests: Total files compared: 50
• DQMHistoTests: Total histograms compared: 3370032
• DQMHistoTests: Total failures: 73
• DQMHistoTests: Total nulls: 0
• DQMHistoTests: Total successes: 3369937
• DQMHistoTests: Total skipped: 22
• DQMHistoTests: Total Missing objects: 0
• DQMHistoSizes: Histogram memory added: 0.0 KiB( 49 files compared)
• Checked 214 log files, 167 edm output root files, 50 DQM output files
• TriggerResults: no differences found

[bsunanda]

+geometry

[bsunanda]

@sunilUIET Can you approve this?

[sunilUIET]

+pdmv

[bsunanda]

@srimanob Can you approve this please?

[civanch]

+1

[srimanob]

test parameters:

• workflow = 27234.0
• relvals_opt = --what cleanedupgrade,standard,highstats,pileup,generator,extendedgen,production,identity,ged,machine,premix,nano,gpu,2017,2026

[srimanob]

@cmsbuild please test

We should test the new workflow in the PR.

[srimanob]

FYI @fabiocos @24LopezR
I propose to merge this PR first. Then ETL (#43407) on top with new defined D105. Thx.

[cmsbuild]

+1

Summary: https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-204a05/36276/summary.html
COMMIT: 5c23d2b
CMSSW: CMSSW_14_0_X_2023-12-01-2300/el8_amd64_gcc12
User test area: For local testing, you can use /cvmfs/cms-ci.cern.ch/week1/cms-sw/cmssw/43466/36276/install.sh to create a dev area with all the needed externals and cmssw changes.

Comparison Summary

Summary:

• You potentially added 6 lines to the logs
• Reco comparison results: 1 differences found in the comparisons
• DQMHistoTests: Total files compared: 50
• DQMHistoTests: Total histograms compared: 3370032
• DQMHistoTests: Total failures: 85
• DQMHistoTests: Total nulls: 0
• DQMHistoTests: Total successes: 3369925
• DQMHistoTests: Total skipped: 22
• DQMHistoTests: Total Missing objects: 0
• DQMHistoSizes: Histogram memory added: 0.0 KiB( 49 files compared)
• Checked 214 log files, 167 edm output root files, 50 DQM output files
• TriggerResults: no differences found

[srimanob]

@bsunanda @cms-sw/trk-dpg-l2

The output of D104 is very very noisy in RECO step. I think it does not relate to this PR, but tracker T35. I may missed it when we integrated D102 which uses T35 also. If this is confirmed, I will sign the PR, and open the issue to follow up. Thx.

%MSG-e SiPixelLorentzAngle:   PixelCPEGenericESProducer:PixelCPEGenericESProducer@callESModule  02-Dec-2023 11:52:15 CET Run: 1 Event: 1
SiPixelLorentzAngle for DetID 303042565 is not stored
%MSG
%MSG-e SiPixelLorentzAngle:   PixelCPEGenericESProducer:PixelCPEGenericESProducer@callESModule  02-Dec-2023 11:52:15 CET Run: 1 Event: 1
SiPixelLorentzAngle for DetID 303042566 is not stored
%MSG
%MSG-e SiPixelLorentzAngle:   PixelCPEGenericESProducer:PixelCPEGenericESProducer@callESModule  02-Dec-2023 11:52:15 CET Run: 1 Event: 1
SiPixelLorentzAngle for DetID 303042569 is not stored
%MSG
%MSG-e SiPixelLorentzAngle:   PixelCPEGenericESProducer:PixelCPEGenericESProducer@callESModule  02-Dec-2023 11:52:15 CET Run: 1 Event: 1
SiPixelLorentzAngle for DetID 303042570 is not stored
%MSG
%MSG-e SiPixelLorentzAngle:   PixelCPEGenericESProducer:PixelCPEGenericESProducer@callESModule  02-Dec-2023 11:52:15 CET Run: 1 Event: 1
SiPixelLorentzAngle for DetID 303042573 is not stored
%MSG
%MSG-e SiPixelLorentzAngle:   PixelCPEGenericESProducer:PixelCPEGenericESProducer@callESModule  02-Dec-2023 11:52:15 CET Run: 1 Event: 1
SiPixelLorentzAngle for DetID 303042574 is not stored
%MSG
%MSG-e SiPixelLorentzAngle:   PixelCPEGenericESProducer:PixelCPEGenericESProducer@callESModule  02-Dec-2023 11:52:15 CET Run: 1 Event: 1
SiPixelLorentzAngle for DetID 303042577 is not stored

[mmusich]

@srimanob

The output of D104 is very very noisy in RECO step. I think it does not relate to this PR, but tracker T35. I may missed it when we integrated D102 which uses T35 also. If this is confirmed, I will sign the PR, and open the issue to follow up. Thx.

this happens because in #41880 it was forgotten to update the labels forWidth and fromAlignment in the map at autoCondPhase2, hence the relval job reads the ones (not being overridden) in the physical GT auto:phase2_realistic. Since this latter is based off geometry T21 it doesn't have the split sensors in BPix1, thus the error messages. This is followed up at #43482 .

[srimanob]

+Upgrade

Thanks @mmusich to follow up on the tracker complain.

[antoniovilela]

+1

[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 be automatically merged.