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
Develop dqm 710pre2 v03 #3049
Develop dqm 710pre2 v03 #3049
Conversation
…nd JPT related parts
… functionality from OfflineClient now in other analyzers, take out of sequence
… to make it reproducible
A new Pull Request was created by @webermat for CMSSW_7_1_X. Develop dqm 710pre2 v03 It involves the following packages: DQMOffline/JetMET @ojeda, @danduggan, @rovere, @cmsbuild, @nclopezo, @deguio, @Degano can you please review it and eventually sign? Thanks. |
Looking through the comparison plots, I noticed additional plots which didn't appear when i ran locally. Reason: a boolean was defined but used uninitialized, I apologize for only noticing this so late. |
ciao @webermat I have written it in red now: ;) Could you please make sure that only the modules run in DQM step1 have been migrated? thanks, |
and I fear there is more. apparently both the JetAnalyzer and the MetAnalyzer are accessing thread-unsafe event setup object. they still need to be fixed. for a list have a look at the table in slide9: I am not asking you to take care of those, but I have to keep the pull request pending for now. I am sorry about that. it is a huge transition the one we are facing. hopefully it will be smoother and smoother soon... |
so the first comments have been taken care off (reverting back to the EDAnalyzer structure for the Harvesting modules). I am afraid we cannot take care of everything for the second item. I removed the call of the MagneticField, which we used to calculate the slope of tracks to the Calorimeter. Since we needed it only for JPTJets and these are to be removed, we don't need that call anymore. |
As long as a module is kept with the old interface it is safe to talk to thread unsafe EventSetup objects (i.e. JetCorrector). Now it happens the JetCorrector has been fixed since the last time we did the 'module to bad EventSetup' check. |
-1 |
Calls of functions of the DQMStore should have been removed by now to run safely in threaded DQM. Only exception is a DQMStore ->save() call if we run our code privately (switched off per default).
The only place where we still use DQMStore functionality is during the harvesting step, so hopefully all problematic issues have been solved.
We work with release CMSSW_7_1_0_pre2.