-
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
Crash in visualization
DQM clients during SPLASH test
#35634
Comments
assign dqm,reconstruction |
New categories assigned: dqm @jfernan2,@ahmad3213,@rvenditti,@emanueleusai,@pbo0,@pmandrik you have been requested to review this Pull request/Issue and eventually sign? Thanks |
A new Issue was created by @francescobrivio . @Dr15Jones, @perrotta, @dpiparo, @makortel, @smuzaffar, @qliphy can you please review it and eventually sign/assign? Thanks. cms-bot commands are listed here |
@mmasciov you may be interested in this as well |
@francescobrivio cmssw/RecoVertex/BeamSpotProducer/python/BeamSpot_cfi.py Lines 7 to 9 in df9a144
see please #35639. I managed to (almost) run your recipe above with it: cmsrel CMSSW_12_0_2_patch1
cd CMSSW_12_0_2_patch1/src
cmsenv
git cms-addpkg DQM/Integration
cmsRun DQM/Integration/python/clients/visualization-live_cfg.py unitTest=True though now it crashes differently with:
somewhat consistently with this comment: cmssw/DQM/Integration/test/BuildFile.xml Lines 32 to 34 in df9a144
what's @cms-sw/alca-l2 plan to fix that? |
Thanks a lot for the quick fix! I left a comment on your PR.
This is already fixed if you force to use the latest 120X GT.
and this ends up in the error that you report. |
I don't think the comment is relevant.
I am not sure. |
OK, apparently #35593 got in the way extremely recently (not yet in an IB) |
@cms-sw/dqm-l2 please see #35642, so that the integration tests do something actually useful and catch this sort of issues earlier. |
Hello, we checked that Event Display clients run fine with this PR for ppEra_Run3 scenario at the playback, thanks |
A crash in the vizualization DQM clients was reported by @pmandrik during the SPLASH test. The clients crashing are:
visualization-live_cfg.py
visualization-live-secondInstance_cfg.py
And the crash error is:
The crash can be easily riproduced by running the unitTest:
DQM online experts can also reproduce the crash in their playback system at P5.
This crash happens only when running with the scenario
ppEra_Run3
and don't crash when running with scenariocosmicsEra_Run3
.IIUC this is because the reco requence in the two cases is different and in in the
pp
case the beamspot is required.Looking into the configuration I can see that the offlineBeamSpot has been swapped with the onlineBeamSpot:
and the only place this swapping happens is in:
cmssw/Configuration/DataProcessing/python/RecoTLR.py
Lines 7 to 15 in 922a36d
which is used to customize the express processing. So now the sequence will look for a
BeamSpotTransientObjectsRcd
but apparently that is not provided by any Source and this is not clear to me because the express customization automatically adds the BeamSpotESProducer.A quick solution would then be to add the ESProducer to the DQM clients:
But I'm not sure if that is the correct way of doing it or if it's better to understand how the customization of the
visualizationProcessing
works and eventually modify it?[EDIT]
The quick solution to add the ESProducer to the DQM clients was already somehow used in #35373
The text was updated successfully, but these errors were encountered: