Add AlCaReco producers in phase-2 workflows

[mmusich]

PR description:

The goal of this PR is to start exercising Tracker alcareco producers in the phase-2 workflows, as there is interest in trying a preliminary alignment with the phase-2 geometry.
A minimal set of changes if proposed in order to achieve that goal, including the necessary update of the phase2_realistic autoCond key in order to get most updated trigger bits from the run-3 global tag (see also cmsTalk):

• Global Tag difference: https://cms-conddb.cern.ch/cmsDbBrowser/diff/Prod/gts/125X_mcRun4_realistic_v2/125X_mcRun4_realistic_v3

In addition the pseudo-rapidity range of the alignment alcarecos is modified in the case of the phase-2 tracker to allow full coverage (up to |η|<4).

PR validation:

Run successfully runTheMatrix.py -l 20834.0 -t 4 -j 8

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:

N/A

cc:
@consuegs

[cmsbuild]

+code-checks

Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-39858/32755

• This PR adds an extra 72KB to repository

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

  • File Configuration/AlCa/python/autoCond.py modified in PR(s): Update Run3 offline and offline_relval GTs #39823, Add new HI Beamspot to the Run-3 HI MC + change vertex smearing to use the estimated HI version #39758
  • File Configuration/PyReleaseValidation/python/relval_steps.py modified in PR(s): NANO configuration Cleanup #39796, use --hltProcess reHLT in Run-3 Data RelVals #39834, Add new HI Beamspot to the Run-3 HI MC + change vertex smearing to use the estimated HI version #39758
  • File Configuration/PyReleaseValidation/python/upgradeWorkflowComponents.py modified in PR(s): Add D97 Phase-2 geometry #39841, Add tracking only PU workflows #39722, Add run3 tracking low pu era #33532

[cmsbuild]

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

It involves the following packages:

• Alignment/CommonAlignmentProducer (alca)
• Configuration/AlCa (alca)
• Configuration/PyReleaseValidation (pdmv, upgrade)
• RecoTracker/TransientTrackingRecHit (reconstruction)

@malbouis, @ChrisMisan, @yuanchao, @bbilin, @clacaputo, @cmsbuild, @AdrianoDee, @srimanob, @saumyaphor4252, @kskovpen, @sunilUIET, @tvami, @mandrenguyen, @francescobrivio can you please review it and eventually sign? Thanks.
@VourMa, @felicepantaleo, @kpedro88, @Martin-Grunewald, @tlampen, @trtomei, @slomeo, @pakhotin, @makortel, @JanFSchulte, @dgulhan, @missirol, @beaucero, @GiacomoSguazzoni, @rovere, @VinInn, @tocheng, @mmusich, @mtosi, @fabiocos, @adewit, @gpetruc this is something you requested to watch as well.
@perrotta, @dpiparo, @rappoccio you are the release manager for this.

cms-bot commands are listed here

[mmusich]

@cmsbuild, please test

[cmsbuild]

+1

Summary: https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-64ceed/28531/summary.html
COMMIT: 941de35
CMSSW: CMSSW_12_6_X_2022-10-26-1100/el8_amd64_gcc10
User test area: For local testing, you can use /cvmfs/cms-ci.cern.ch/week0/cms-sw/cmssw/39858/28531/install.sh to create a dev area with all the needed externals and cmssw changes.

Comparison Summary

Summary:

• No significant changes to the logs found
• Reco comparison results: 13 differences found in the comparisons
• Reco comparison had 1 failed jobs
• DQMHistoTests: Total files compared: 48
• DQMHistoTests: Total histograms compared: 2918374
• DQMHistoTests: Total failures: 12
• DQMHistoTests: Total nulls: 0
• DQMHistoTests: Total successes: 2918340
• DQMHistoTests: Total skipped: 22
• DQMHistoTests: Total Missing objects: 0
• DQMHistoSizes: Histogram memory added: 0.0 KiB( 42 files compared)
• Checked 180 log files, 48 edm output root files, 48 DQM output files
• TriggerResults: no differences found

[malbouis]

Thank you for this, @mmusich !

I have created a versioned GT to replace the Candidate GT in autoCond.py: 125X_mcRun4_realistic_v3

The only difference wrt to the previous GT is the AlCaRecoTriggerBits tag: https://cms-conddb.cern.ch/cmsDbBrowser/diff/Prod/gts/125X_mcRun4_realistic_v2/125X_mcRun4_realistic_v3

Would you please replace the Candidate Gt with this versioned one?

[malbouis]

+alca

• I already leave the alca signature but I have no problem signing again in case the tests are re-triggered due to changes :-)
• Changes are inline with the description
• the tests results came back fine, only message logger failures

[mandrenguyen]

+1

[srimanob]

To clarify, the PR proposes to run ALCA step by default in all Phase-2 workflows. What is the cost, i.e. in terms of RelVals disk when we run full set of relvals, both NoPU and PU200?

I see we currently do the same for Run-3 also.

[mmusich]

PU200?

is not run.

[srimanob]

Ah, OK. The Alca step is not in

cmssw/Configuration/PyReleaseValidation/python/upgradeWorkflowComponents.py

Line 2162 in 638de99

upgradeProperties[2026][key+'PU']['ScenToRun'] = ['GenSimHLBeamSpot','DigiTriggerPU','RecoGlobalPU', 'HARVESTGlobalPU']

[srimanob]

+Upgrade

[mmusich]

@cms-sw/pdmv-l2 please have a look and if you agree sign.
Thank you.

[kskovpen]

+pdmv

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

[perrotta]

+1