-
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
Standalone version of beamspot DIP client [12_3_X] #37817
Conversation
A new Pull Request was created by @sikler (Ferenc Siklr) for CMSSW_12_3_X. It involves the following packages:
@emanueleusai, @ahmad3213, @cmsbuild, @jfernan2, @pmandrik, @micsucmed, @rvenditti can you please review it and eventually sign? Thanks. cms-bot commands are listed here
|
Pull request #37817 was updated. @emanueleusai, @ahmad3213, @cmsbuild, @jfernan2, @pmandrik, @micsucmed, @rvenditti can you please check and sign again. |
Hi, @sikler , the only place of *TkStatus.txt files creation I found is [0] called by beam client [1] where DIPFileName is 'BeamFitResultsOld.txt' at the moment. Probably beamhlt process workflow (where 'BeamFitResults.txt' is used) is needed to be updated with cms.EDAnalyzer("TKStatus"). [0] https://github.com/cms-sw/cmssw/blob/master/DQM/BeamMonitor/plugins/TKStatus.cc
|
please test |
Pull request #37817 was updated. @malbouis, @pmandrik, @emanueleusai, @ahmad3213, @tvami, @jfernan2, @ggovi, @francescobrivio, @micsucmed, @rvenditti can you please check and sign again. |
@sikler , is it already in 12.4.X/master Ib? |
+1 Summary: https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-e84e80/24478/summary.html Comparison SummarySummary:
|
Hi @smuzaffar, there is now a forward port to master at #37835. |
backport of #37835 |
testing at P5 |
Pull request #37817 was updated. @malbouis, @pmandrik, @emanueleusai, @ahmad3213, @tvami, @cmsbuild, @jfernan2, @ggovi, @francescobrivio, @micsucmed, @rvenditti can you please check and sign again. |
-1 Failed Tests: AddOn AddOn Tests
Comparison SummarySummary:
|
Hi Ferenc (@sikler) could you add an |
Pull request #37817 was updated. @malbouis, @pmandrik, @emanueleusai, @ahmad3213, @tvami, @cmsbuild, @jfernan2, @ggovi, @francescobrivio, @micsucmed, @rvenditti can you please check and sign again. |
Hi @francescobrivio , runtest.sh added to this and to master. Now possible to pass parameters. |
@cmsbuild , please test |
+1 Summary: https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-e84e80/24579/summary.html Comparison SummarySummary:
|
+db |
+1 |
This pull request is fully signed and it will be integrated in one of the next CMSSW_12_3_X IBs (tests are also fine) and once validation in the development release cycle CMSSW_12_4_X is complete. This pull request will now be reviewed by the release team before it's merged. @perrotta, @dpiparo, @qliphy (and backports should be raised in the release meeting by the corresponding L2) |
+1 |
PR description:
The DQM client version was alive only for the duration of the run, and DIP consumers want a steady presence of the beamspot product. This way, the client is now transfered back to a standalone executable, running forever, polling every second some beamspot and tracker status txt files on /nfshome0. To be placed likely in the startup of a local P5 machine, from where both the CMS-related DIP machine (cmsdimns1.cern.ch, cmsdimns2.cern.ch) and /nfshome0 are both visible and accessible.
PR validation:
Tested successfully on fu-c2f11-11-03, by looking at DIP-related pages to check proper placement of publications:
https://cmsonline.cern.ch/webcenter/portal/cmsonline/pages_common/dcs/dipbrowser [under dip/CMS/...]
https://ccde.cern.ch/nxcals/device/313400?subscriptionId=29210033
https://ccde.cern.ch/nxcals/device/1731503?subscriptionId=29407975
https://timber.cern.ch/query?tab=Visualization&configuration=38326
PR issues:
The process is polling two files:
/nfshome0/dqmpro/BeamMonitorDQM/BeamFitResults.txt
/nfshome0/dqmpro/BeamMonitorDQM/BeamFitResults_TkStatus.txt
where the latter has a very old timestamp (from 2018), so very likely the file related to tracker status is not written by any client. Any ideas?