-
Notifications
You must be signed in to change notification settings - Fork 4.4k
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
Add CPPF DQM modules #38564
Add CPPF DQM modules #38564
Conversation
-code-checks Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-38564/30811
Code check has found code style and quality issues which could be resolved by applying following patch(s)
|
+code-checks Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-38564/30812
|
A new Pull Request was created by @zhangcg123 for master. It involves the following packages:
@epalencia, @emanueleusai, @ahmad3213, @cmsbuild, @rekovic, @jfernan2, @clacaputo, @jpata, @pmandrik, @micsucmed, @cecilecaillol, @rvenditti can you please review it and eventually sign? Thanks. cms-bot commands are listed here |
please test |
+1 Summary: https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-daadf4/25926/summary.html Comparison SummarySummary:
|
+1 |
Hi @cecilecaillol, @epalencia, is this ok to go in |
@zhangcg123 Can you please replace the couts with edmLogWarning/Error/... (https://twiki.cern.ch/twiki/bin/view/CMSPublic/SWGuideMessageLogger) ? |
+reconstruction
|
@zhangcg123 if I compare with the version before your latest squash I get the following diff in DQM/L1TMonitor/python/L1TStage2Emulator_cff.py:
Could you please check? |
Hi @perrotta The new squash was rebased on the top of the newest merged commits at that time. The diff you mentioned is here. 67f988c#diff-958876a581b9e879b842bdfcb4371f7bef929312c19e0d17a8e5c55484708c71 Thanks |
Thank you @zhangcg123 : then you confirm that the update 67f988c#diff-958876a581b9e879b842bdfcb4371f7bef929312c19e0d17a8e5c55484708c71 that is in this PR was already there in the previous one? |
+l1 |
Hi @perrotta I think these changes is not from our side. When we created this PR and now there are couple of PR which is merged. So, the change that you mention is not from our side. It is from the other PR. If you check all the files that we changed here: https://github.com/cms-sw/cmssw/pull/38564/files This link does not show any additional line/file. Let me know if I did not get your message. |
Ah, ok, now I understand. You rebased on top of an older IB than the one in which #38373 was merged The squeeze was correct, then. And as soon as @cms-sw/dqm-l2 signs, this PR can get merged |
@perrotta , we are also getting confused. Thanks for your explanation. |
+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. @perrotta, @dpiparo, @qliphy, @rappoccio (and backports should be raised in the release meeting by the corresponding L2) |
+1 |
@zhangcg123 There is a reval error appearing after merging this PR, please have a look and fix soon: An exception of category 'OutOfRange' occurred while |
@zhangcg123 In case you don't know, you can reproduce the error with The test with CMSSW_12_5_X_2022-07-27-2300 (before your PR merged) is fine, |
@qliphy Many thanks for your instruction, I will try to fix the problem as soon as I can. |
PR description:
Add CPPF online DQM modules L1TdeStage2CPPF and L1TStage2CPPF.
By comparing the CPPF emulator and unpacker outputs and putting some comparison histograms on the CMS online DQM GUI, shifters can monitor the status of the CPPF hardware.
https://twiki.cern.ch/twiki/bin/viewauth/CMS/CPPFDQMDevelopment
https://indico.cern.ch/event/1096936/contributions/4614848/attachments/2347544/4003548/Ram_CPPFUpdate_20211117.pdf
PR validation:
cmsRun DQM/Integration/python/clients/l1tstage2emulator_dqm_sourceclient-live_cfg.py unitTest=True
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:
The PR will have to be backported to 10_4_X