[12.5.X] MillePedeDQMModule: add string MonitorElement to signal if the update was vetoed

[mmusich]

backport of #39552

PR description:

In PR #28318 some additional details plots were added to the SiPixelAli PCL in order to display more information about if and why the upload was vetoed.
On the other hand the current setup is not super-clear to read if one just wants to know if there was a veto or not.
For this reason we decided to add a simple string MonitorElement in order to write if the DB was updated, there was a veto or N/A in case the PCL was not run.

PR validation:

cmssw compiles.

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:

verbatim backport of #39552 (for data-taking purposes)

[cmsbuild]

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

It involves the following packages:

• Alignment/MillePedeAlignmentAlgorithm (alca)

@malbouis, @yuanchao, @cmsbuild, @saumyaphor4252, @francescobrivio, @ChrisMisan, @tvami can you please review it and eventually sign? Thanks.
@mmusich, @adewit, @tocheng, @tlampen 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

• Backported from MillePedeDQMModule: add string MonitorElement to signal if the update was vetoed #39552

[mmusich]

test parameters:

• workflows = 1001.2, 1001.3

[mmusich]

please test

[cmsbuild]

+1

Summary: https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-ad7db1/27899/summary.html
COMMIT: 9cc016b
CMSSW: CMSSW_12_5_X_2022-09-30-2300/el8_amd64_gcc10
User test area: For local testing, you can use /cvmfs/cms-ci.cern.ch/week0/cms-sw/cmssw/39562/27899/install.sh to create a dev area with all the needed externals and cmssw changes.

Comparison Summary

@slava77 comparisons for the following workflows were not done due to missing matrix map:

• /data/cmsbld/jenkins/workspace/compare-root-files-short-matrix/data/PR-ad7db1/1001.2_RunZeroBias2017F+RunZeroBias2017F+TIER0EXPRUN2+ALCAEXPRUN2+ALCAHARVDSIPIXELCAL+ALCAHARVDSIPIXELCALLA+ALCAHARVD4+ALCAHARVDSIPIXELALIHG
• /data/cmsbld/jenkins/workspace/compare-root-files-short-matrix/data/PR-ad7db1/1001.3_RunSingleMuon2022B+RunSingleMuon2022B+TIER0EXPRUN3+ALCAEXPRUN3+ALCAHARVDEXPRUN3

Summary:

• No significant changes to the logs found
• Reco comparison results: 0 differences found in the comparisons
• DQMHistoTests: Total files compared: 53
• DQMHistoTests: Total histograms compared: 3714389
• DQMHistoTests: Total failures: 2
• DQMHistoTests: Total nulls: 0
• DQMHistoTests: Total successes: 3714365
• DQMHistoTests: Total skipped: 22
• DQMHistoTests: Total Missing objects: 0
• DQMHistoSizes: Histogram memory added: 0.076 KiB( 52 files compared)
• DQMHistoSizes: changed ( 1001.2 ): 0.039 KiB AlCaReco/SiPixelAliHG
• DQMHistoSizes: changed ( 1001.3 ): 0.037 KiB AlCaReco/SiPixelAli
• Checked 223 log files, 49 edm output root files, 53 DQM output files
• TriggerResults: no differences found

[ChrisMisan]

+alca

• differences only in MTD
• backport ok

[cmsbuild]

This pull request is fully signed and it will be integrated in one of the next CMSSW_12_5_X IBs (tests are also fine) and once validation in the development release cycle CMSSW_12_6_X is complete. 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