[13.2.X] Introduce PCL-like workflows for SiStrip Lorentz Angle Monitoring (and potentially calibration)

[mmusich]

backport of #42574
backport of #42680

From the original PRs:

PR description:

This PR introduces a PCL-like workflow for SiStrip Lorentz Angle Monitoring (and potentially calibration), by using the SiStripCalCosmics dataset in input. The setup closesly resemble the one presented multiple times (see e.g. this talk) in which the hall mobility of the strips modules (only TIB and TOB for the time being, grouped in regions sharing same layer / module type) is estimated by fitting the distribution of the Strip cluster multiplicity as a function of the track grazing angle.
The SiStripCalCosmics AlCaReco producer is added to the ExpressCosmics PD in autoAlCa while the new PromptCalibProdSiStripLA ALCAPrompt producer is introduced in several configuration files in Configuration/StandardSequences package.
As a minimal follow-up, in order to be able to support uploads from the Prompt Calibration Loop:

• updated DropBoxMetaData writer and reader configuration files
• provided steering meta-data for upload to prod / prep and for the multi-run harvesting case
• added SiStripLorentzAngle workflow to Calibration/TkAlCaRecoProducers/test/testPCLAlCaHarvesting.py

PR validation:

Run the following command:

cmsDriver.py testReAlCa -s ALCA:PromptCalibProdSiStripLA --conditions 130X_dataRun3_Prompt_v2 --scenario cosmics --data --era Run3_2023 --datatier ALCARECO --eventcontent ALCARECO --processName=ReAlCa -n 100000 --dasquery='file dataset=/Cosmics/Commissioning2023-SiStripCalCosmics-PromptReco-v1/ALCARECO run=364141' --nThreads=4 

followed by:

cmsDriver.py stepHarvest -s ALCAHARVEST:SiStripLA --conditions 130X_dataRun3_Prompt_v2 --scenario pp --data --era Run3_2023 -n -1 --filein file:PromptCalibProdSiStripLA.root

and obtained reasonable output DQM and db files.
Also run successfully the augmented relval wf 1005.0 (runTheMatrix.py -l 1005.0 -t 4 -j 8 --ibeos.

scram b runtests runs fine.

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:

Combined backport of #42574 and #42680
While this PR is not strictly needed for the rest of the 2023 data-taking ppRef / HI runs, it would be nice to have it included in the next 13.2.X (if that's possible) in order to profit of the testing machinery setup at Tier-0, in order to ask for a dedicated replay.

[cmsbuild]

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

It involves the following packages:

• CalibTracker/SiStripLorentzAngle (alca)
• Calibration/TkAlCaRecoProducers (alca)
• CondFormats/Common (db, alca)
• Configuration/AlCa (alca)
• Configuration/EventContent (operations)
• Configuration/PyReleaseValidation (pdmv, upgrade)
• Configuration/StandardSequences (operations)

@perrotta, @rappoccio, @bbilin, @consuegs, @tvami, @cmsbuild, @AdrianoDee, @miquork, @saumyaphor4252, @antoniovilela, @srimanob, @sunilUIET, @francescobrivio, @fabiocos, @davidlange6 can you please review it and eventually sign? Thanks.
@echabert, @VourMa, @felicepantaleo, @robervalwalsh, @argiro, @Martin-Grunewald, @thomreis, @threus, @slomeo, @makortel, @JanFSchulte, @dgulhan, @missirol, @seemasharmafnal, @GiacomoSguazzoni, @rovere, @VinInn, @tocheng, @mmusich, @mtosi, @fabiocos, @rchatter, @gbenelli, @wang0jin, @sameasy this is something you requested to watch as well.
@perrotta, @dpiparo, @antoniovilela, @rappoccio you are the release manager for this.

cms-bot commands are listed here

• Backported from Introduce PCL-like workflows for SiStrip Lorentz Angle Monitoring (and potentially calibration) #42574

[mmusich]

test parameters:

• workflow = 1005.0

[mmusich]

please test

[cmsbuild]

+1

Summary: https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-f0a09c/34541/summary.html
COMMIT: 5566c71
CMSSW: CMSSW_13_2_X_2023-08-29-2300/el8_amd64_gcc11
User test area: For local testing, you can use /cvmfs/cms-ci.cern.ch/week0/cms-sw/cmssw/42683/34541/install.sh to create a dev area with all the needed externals and cmssw changes.

Comparison Summary

Summary:

• You potentially added 1 lines to the logs
• ROOTFileChecks: Some differences in event products or their sizes found
• Reco comparison results: 16 differences found in the comparisons
• DQMHistoTests: Total files compared: 49
• DQMHistoTests: Total histograms compared: 3197913
• DQMHistoTests: Total failures: 6
• DQMHistoTests: Total nulls: 0
• DQMHistoTests: Total successes: 3197885
• DQMHistoTests: Total skipped: 22
• DQMHistoTests: Total Missing objects: 0
• DQMHistoSizes: Histogram memory added: -36749.923 KiB( 48 files compared)
• DQMHistoSizes: changed ( 1005.0 ): -42261.943 KiB AlCaReco/SiStrip
• DQMHistoSizes: changed ( 1005.0 ): 5512.021 KiB AlCaReco/SiStripLorentzAngle
• Checked 211 log files, 160 edm output root files, 49 DQM output files
• TriggerResults: no differences found

[perrotta]

While reviewing, a few minor (and fully innocuous) typos were spot.
They are NOT intended to be implemented in this backport, but can be taken into account for a possible follow up PR in the master

[perrotta]

+alca

• Verbatim backport of Introduce PCL-like workflows for SiStrip Lorentz Angle Monitoring (and potentially calibration) #42574 and add necessary changes to run the uploads of SiStripLorentzAngle payloads in the PCL #42680
• Only the dedicated ExpressCosmics PD is touched (wf 1005 among the tested ones), as planned
• I think this is worth being backported for the next data taking 13_2_X release

[perrotta]

+db

[srimanob]

+upgrade

[sunilUIET]

+pdmv

[mmusich]

They are NOT intended to be implemented in this backport, but can be taken into account for a possible follow up PR in the master

thanks @perrotta I'll take care of these later on in master.

[mmusich]

@cms-sw/operations-l2 this backport is missing your signature

[mmusich]

@cms-sw/orp-l2 please merge this request, this needs to be included in the next 13.2.x release for testing at Tier0

[perrotta]

urgent

[mmusich]

@antoniovilela @rappoccio this PR is fully signed (waiting your operations signature) and despite being flagged urgent, is not yet merged. Can you clarify the foreseen integration path ?

[antoniovilela]

+1

[cmsbuild]

This pull request is fully signed and it will be integrated in one of the next CMSSW_13_2_X IBs (tests are also fine) and once validation in the development release cycle CMSSW_13_3_X is complete. This pull request will be automatically merged.