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
[RPC] Changing the RPCDcsInfo* about an issue of the DQM legacy module #31056
Conversation
…PC DCS bits that saved at the DQMProvInfo
The code-checks are being triggered in jenkins. |
-code-checks Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-31056/17567
Code check has found code style and quality issues which could be resolved by applying following patch(s)
|
The code-checks are being triggered in jenkins. |
-code-checks Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-31056/17593
Code check has found code style and quality issues which could be resolved by applying following patch(s)
|
The code-checks are being triggered in jenkins. |
+code-checks Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-31056/17594
|
A new Pull Request was created by @jeongsumin (jeongsumin) for master. It involves the following packages: DQM/RPCMonitorClient @kmaeshima, @cmsbuild, @andrius-k, @jfernan2, @fioriNTU can you please review it and eventually sign? Thanks. cms-bot commands are listed here |
@@ -7,5 +7,3 @@ DEFINE_FWK_MODULE(RPCMonitorDigi); | |||
DEFINE_FWK_MODULE(RPCRecHitProbability); | |||
#include "DQM/RPCMonitorDigi/interface/RPCTTUMonitor.h" | |||
DEFINE_FWK_MODULE(RPCTTUMonitor); | |||
#include "DQM/RPCMonitorDigi/interface/RPCDcsInfo.h" | |||
DEFINE_FWK_MODULE(RPCDcsInfo); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
If you are making it so the module can never be loaded, then shouldn't RPCDcsInfo.h and RPCDcsInfo.cc both be removed from CMSSW?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I forgot to update the removal... Thank you for mentioning that!
Comparison job queued. |
Comparison is ready Comparison Summary:
|
+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 |
After this PR was merged, this unit test started failing in all IBs
|
@jeongsumin I believe it has to do with the Online client in |
@jfernan2 Thanks for checking that. I will see that right now. |
@jfernan2 @mrodozov Sorry for the late reply. Have you ever seen that message when running the unit test? I don't know the reason why this error can be occurred for now. |
@jeongsumin you removed the plugin in: |
@jfernan2 I forgot to do the unit test by using the before merged version yesterday. I'm so sorry about that. The "[RPCMonitorDigi]: Muons - Product not valid for event" error also occurs at the before merged version when doing the unit test using by RPC online client. I'm not sure, but It seems to some option that the muon information can be used when the unit test. So I think if the RPCDcsInfo process is removed from RPC online client, there will be no more test failing in all IBs. |
@jeongsumin if RPC is fine removing the module from Online DQM, we are fine too :-) |
@jfernan2 Thanks a lot. Then I will make the PR about this right now. |
PR description:
The RPCDcsInfo module has a problem because of using DQMOneLumiEDAnalyzer.
(This problem was already issued in the #25090 )
This module gets the RPC DCS bit per Lumi-Section using 'scalersRawToDigi'.
So in the harvesting step, RPCDcsInfoClient also affected by this problem.
But DCS bit already contained in the reportSummaryMap which is histogramming at the DQMProvInfo module.
Therefore, we do not need to use the RPCDcsInfo module and the luminosity block (dqmEndLuminosityBlock) in the RPCDcsInfoClient.
From this change, RPC does not have an issue with this.
At the bottom, I attach the RPC HV status plot which affected by RPC DCS bit.
before & after changing the module:
** HV status histogram: If the scalersRawToDigi (DCS bit) not found, then HV status is 0 (HV was off). If not, then HV status is 1 (HV was on)
*** This data has 576 LumiSection
PR validation:
Tested by runTheMatrix 138.1 (RunCosmics2020, MWGR data) with multi-thread and single-thread
if this PR is a backport please specify the original PR and why you need to backport that PR:
@andresib @jhgoh
I make the new PR about changing the RPC DQM legacy module.