New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fixing Stat Overflows consideration on DQM modules #32364
Conversation
please test |
-code-checks Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-32364/20209
Code check has found code style and quality issues which could be resolved by applying following patch(s)
|
none of those (Alignment classes and macros) is run in central workflows, so I think they cannot do any harm anywhere else.
I think there is an ongoing campaign to remove every direct access to the underlying bare ROOT from the ME within the tracker DQM group (see e.g: this talk ) |
Thanks @mmusich I am open to implement the other solution, I do not know which one is best |
IMHO the one you propose here is the better one, but I am definitely not an expert. |
+code-checks Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-32364/20210
|
A new Pull Request was created by @jfernan2 for master. It involves the following packages: DQMOffline/EGamma @andrius-k, @kmaeshima, @ErnestaP, @cmsbuild, @jfernan2, @fioriNTU can you please review it and eventually sign? Thanks. cms-bot commands are listed here |
please test |
The tests are being triggered in jenkins.
|
+1 |
One clarification from my side (for what it's worth): I was not aware of those DQM recommendations (@jfernan2 , could you please point to them?). What was done in #32343 was the only way, at that time, to avoid using ROOT's |
@missirol in principle DQM methods are working on internal "ROOT" objects: cmssw/DQMServices/Core/interface/MonitorElement.h Lines 370 to 430 in d2c2ace
so, to avoid colliding modifications which are difficult to track, direct ROOT modifications are not desired |
@cmsbuild please test |
+1 Summary: https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-13b23a/12328/summary.html Comparison SummarySummary:
|
Thank you very much @arossi83 !! |
unhold |
@amassiro would you be so kind to perform the followup to #32343 you mentioned below? Thanks
|
Oh yes, sorry, github misled me. Thank you @missirol ! |
+1 |
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. @silviodonato, @dpiparo, @qliphy (and backports should be raised in the release meeting by the corresponding L2) |
+1 |
PR description:
This PR tries to fix the problem mentioned in #32343 (comment)
The proposed solution goes directly to DQM core setStatOverflows method instead of using teh ROOT method SetStatOverflow since DQM Monitor Elements inherit from there and this prevents modifying many DQM modules around.
I let coding experts to decide if this solution is preferred to directly modify
DQM/SiStripMonitorCluster/src/SiStripMonitorCluster.cc
DQM/SiStripMonitorTrack/src/SiStripMonitorTrack.cc
DQM/SiStripMonitorDigi/src/SiStripMonitorDigi.cc
DQMOffline/EGamma/src/ElectronDqmAnalyzerBase.cc
as suggested on #3234 instead.
I can switch to that strategy if preferred.
I have also noticed that there are many Alignment classes suffering from this too:
https://github.com/cms-sw/cmssw/search?p=1&q=StatOverflows
PR validation:
Checked compilation and some wf running