Improve QTest Pixel DQM (BP to [14_0_X])

[alaperto]

PR description:

Changes to Pixel DQM Quality Test

1. L1 cluster size:
   Issue: HI runs from 2023 and early 2024 pp runs had cluster size > 6 (outside allowed range)
   GUI plot: https://tinyurl.com/2ccppw6k
   GUI summary: https://tinyurl.com/2dysgbhe
   Details: slides 5-6-7
   Change: increase error threshold for the QTest from 6 to 7 (L1 mean cluster size)

2. Cluster charge (BPix and FPix):
   Issue: 2024 pp runs have cluster charge close to error threshold (values established 5 years ago, during Run 2)
   GUI plot: https://tinyurl.com/22n2bwvv
   GUI summary: https://tinyurl.com/2xn3uu59
   Details: slides 2-3-4
   Change: reduce error threshold to 15k electrons (BPix and FPix mean cluster charge)

PR validation:

Simple change to config numerical values: no validation done

About backport

This is a backport to 14_0_X of #45840

[cmsbuild]

A new Pull Request was created by @alaperto for CMSSW_14_0_X.

It involves the following packages:

• DQM/SiPixelPhase1Config (dqm)

@antoniovagnerini, @cmsbuild, @nothingface0, @rvenditti, @syuvivida, @tjavaid can you please review it and eventually sign? Thanks.
@arossi83, @fioriNTU, @idebruyn, @jandrea, @mmusich, @sroychow, @threus this is something you requested to watch as well.
@antoniovilela, @mandrenguyen, @rappoccio, @sextonkennedy you are the release manager for this.

cms-bot commands are listed here

• Backported from Improve QTest Pixel DQM #45840

[cmsbuild]

cms-bot internal usage

[tjavaid]

please test

[tjavaid]

backport of #45840

[cmsbuild]

+1

Size: This PR adds an extra 12KB to repository
Summary: https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-1613e7/41200/summary.html
COMMIT: 6b68a34
CMSSW: CMSSW_14_0_X_2024-08-30-1100/el8_amd64_gcc12
User test area: For local testing, you can use /cvmfs/cms-ci.cern.ch/week0/cms-sw/cmssw/45841/41200/install.sh to create a dev area with all the needed externals and cmssw changes.

Comparison Summary

Summary:

• You potentially added 110 lines to the logs
• Reco comparison results: 123 differences found in the comparisons
• DQMHistoTests: Total files compared: 48
• DQMHistoTests: Total histograms compared: 3346748
• DQMHistoTests: Total failures: 2603
• DQMHistoTests: Total nulls: 0
• DQMHistoTests: Total successes: 3344125
• DQMHistoTests: Total skipped: 20
• DQMHistoTests: Total Missing objects: 0
• DQMHistoSizes: Histogram memory added: 0.0 KiB( 47 files compared)
• Checked 202 log files, 165 edm output root files, 48 DQM output files
• TriggerResults: no differences found

[sroychow]

ping @cms-sw/dqm-l2

[tjavaid]

@alaperto , @sroychow , we are testing the PR at our playback machine with Run 384377. Could you please have a look at GUI plots and see whether changes are applied. Thanks!

[alaperto]

Hi @tjavaid is there a reason why you're using Online Playback machine?
The changes were targeting Offline DQM GUI.
By the way, I guess the QTest (modified code) is applied also to Online Summary maps:

• the Cluster Charge Summary appear Green, as expected from the changes
• before the fix, it was showing Red and Orange blocks

[tjavaid]

I guess the QTest (modified code) is applied also to Online Summary maps:

Hi @alaperto , yes. That's also my perception that it also propagates to the Online Summary maps as I looked at the existing plots (thanks for checking from your side as well).
If you are OK with the changes to both Offline/Online plots, we can sign it now.

[alaperto]

Hi @tjavaid looks great! Please, proceed.

[tjavaid]

+1

• P5 tests OK.
• spurious differences seen from unstable WF 12834.7 (open issue spurious differences in outputs of Run-3 wfs *.7 #39803 )

[cmsbuild]

This pull request is fully signed and it will be integrated in one of the next CMSSW_14_0_X IBs (tests are also fine) and once validation in the development release cycle CMSSW_14_2_X is complete. This pull request will now be reviewed by the release team before it's merged. @sextonkennedy, @rappoccio, @mandrenguyen, @antoniovilela (and backports should be raised in the release meeting by the corresponding L2)

[tjavaid]

Hi @tjavaid looks great! Please, proceed.

@alaperto , may I ask to edit title of the PR a bit i.e. change (BP) to [14_0_X]

[antoniovilela]

+1