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 DMQ FakeBeamMonitor plugin and clients - backport to 11_1_X #30696
Add DMQ FakeBeamMonitor plugin and clients - backport to 11_1_X #30696
Conversation
A new Pull Request was created by @francescobrivio for CMSSW_11_1_X. It involves the following packages: DQM/BeamMonitor @andrius-k, @kmaeshima, @schneiml, @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.
|
Hi @francescobrivio |
Hi @andrius-k |
So this is a fake client which produces a random beamspot value to test the population of the DB (this will be the new workflow for Run3). In normal conditions we do not need it but as we want to make a test we cannot use the standard client as with cosmic data will always give 0,0,0 as BS position. So we would like to use this fake module ONLY during the test we would like to perform tomorrow or Friday depending on Run Coordination |
Ok, I understand. Just keep in mind that if you want to verify there are no configuration or any other unexpected errors we can run this client in the playback system for a few minutes. |
+1 |
Comparison job queued. |
Hi,@gennai, I tried running the new client in the DQM playback system and it crashes with the following error in the configuration:
Could you please confirm that this crash won't happen during the upcoming MWGR? |
@andrius-k it depends the reason of the crash :-) Did you set noDB=True while running? Other reason could be a missing last_lumi.txt file. @francescobrivio can you try to reproduce the crash? |
I've not seen this crash before, but I can try to reproduce it. @andrius-k what was the command that you used to launch the client? |
@francescobrivio the command that to launch the client was this (from the log): Production system launches DQM Online clients in the same way. @gennai Keep in mind that our playback and production systems are very similar, so a crash in playback is a strong suggestion of a crash in prod. |
@andrius-k point taken, consider that to make the test we would like we will need some real time interaction as It may require to copy a db.key file locally where the jobs is running to access the database and to make sure the url from where the LS number is taken must be working. We will need to coordinate a bit and maybe set up a zoom meeting. The test could just last 10-20 mins if everything works |
Comparison is ready Comparison Summary:
|
@gennai cool, reach out to DQM DOC (me) whenever you're ready to make a test and we can set up a meeting! |
The tests are being triggered in jenkins.
|
This pull request is fully signed and it will be integrated in one of the next CMSSW_11_1_X IBs after it passes the integration tests 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) |
hold |
Pull request has been put on hold by @silviodonato |
+1 |
Comparison job queued. |
Comparison is ready Comparison Summary:
|
+1 |
Hi @silviodonato, |
unhold |
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:
This PR is the backport of #30690 to CMSSW_11_1_X