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
online Beamspot monitor DQM client (backporting of PR 31904) #31924
online Beamspot monitor DQM client (backporting of PR 31904) #31924
Conversation
A new Pull Request was created by @gennai (simone gennai) for CMSSW_11_1_X. It involves the following packages: DQM/BeamMonitor @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 Tested at: a15087c CMSSW: CMSSW_11_1_X_2020-10-23-1100 I found follow errors while testing this PR Failed tests: UnitTests
I found errors in the following unit tests: ---> test TestDQMOnlineClient-onlinebeammonitor_dqm_sourceclient had ERRORS |
Comparison job queued. |
|
||
), | ||
), | ||
connect = cms.string('oracle://cms_orcon_prod/CMS_CONDITIONS') |
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.
This won't work outside of P5 (e.g. in unit tests).
Monitoring file not found, disabling.
----- Begin Fatal Exception 23-Oct-2020 16:51:46 CEST-----------------------
An exception of category 'ConditionDatabase' occurred while
[0] Constructing the EventProcessor
[1] Constructing ESSource: class=PoolDBESSource label='BeamSpotDBSource'
Exception Message:
Service "cms_orcon_prod" can't be open with the current key. from cond::CredentialStore::setUpConnection
----- End Fatal Exception -------------------------------------------------
---> test TestDQMOnlineClient-onlinebeammonitor_dqm_sourceclient had ERRORS
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.
but it is working on lxplus, at least it is working for me. Do you have the proper connection string to put?
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.
Maybe because you have been given a key file with reader access priviliges by @ggovi ?
frontier://FrontierProd/CMS_CONDITIONS
will work for any user, but not sure that's what you want (at P5).
process.source.streamLabel = cms.untracked.string('streamDQMOnlineBeamspot') | ||
|
||
#ESProducer | ||
process.load("CondCore.DBCommon.CondDBSetup_cfi") |
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.
please use CondCore.CondDB.CondDB_cfi
instead
Comparison is ready Comparison Summary:
|
Pull request #31924 was updated. @andrius-k, @kmaeshima, @ErnestaP, @cmsbuild, @jfernan2, @fioriNTU can you please check and sign again. |
please test |
The tests are being triggered in jenkins.
|
Comparison is ready Comparison Summary:
|
Hi, I have checked DT_DQM error and in fact it does not depend on my PR: ---> test TestDQMOnlineClient-dt_dqm_sourceclient had ERRORS It is more an issue with the files chosen to be run in the unitTest. @jfernan2, @silviodonato How shall I proceed? |
@cmsbuild, please test |
The tests are being triggered in jenkins.
|
+1 |
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 CMSSW_11_1_X IBs (tests are also fine) and once validation in the development release cycle CMSSW_11_2_X is complete. 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:
With the new BeamSpot workflow in Run3 two clients will run in DQM producing two different beamspot payloads. An ESProducer is run at HLT to make a reproducible choice of which payload to use. This new client is monitoring the values of the two payloads as well as plotting which one of the two is chosen by the ESProducer logic.
PR validation:
I have run the DQM/Integration/python/clients/onlinebeammonitor_dqm_sourceclient-live_cfg.py with unitTest=True option.
The plots looks right.
if this PR is a backport please specify the original PR and why you need to backport that PR:
this is a backporting of #31904, it is needed for next MWGR