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
Preping Online/Offline HCAL DQM Applications for MWGR2 and beyond #17657
Conversation
A new Pull Request was created by @vkhristenko (Viktor Khristenko) for CMSSW_9_0_X. It involves the following packages: DQM/HcalCommon @cmsbuild, @dmitrijus, @vanbesien, @davidlange6 can you please review it and eventually sign? Thanks. cms-bot commands are listed here #13028 |
Please register it in https://twiki.cern.ch/twiki/bin/viewauth/CMS/DQMP5TagCollector |
Pull request #17657 was updated. @cmsbuild, @dmitrijus, @vanbesien, @davidlange6 can you please check and sign again. |
Pull request #17657 was updated. @cmsbuild, @dmitrijus, @vanbesien, @davidlange6 can you please check and sign again. |
Pull request #17657 was updated. @cmsbuild, @dmitrijus, @vanbesien, @davidlange6 can you please check and sign again. |
@dmitrijus , I updated the tag collector - but that is for 900_pre5 for today, either @DryRun cherry picks it or we run as is VK |
@DryRun is working on the 830 version of this PR. he can update the tag collector when ready |
@@ -32,17 +32,25 @@ namespace hcaldqm | |||
24, 0, 20, 0, 21, 0, 25, 0, 31, 0, | |||
35, 0, 37, 0, 34, 0, 30, 0, 22,22, | |||
29,29, 32,32, 0, 0, 0, 0, 0, 0, | |||
0, 0, 36, 0, 0, 0, 0, 0, 0, 0, | |||
0, 0, 38, 0, 0, 0, 0, 0, 0, 0, | |||
0, 0, 0, 0, 0, 0, 0, 0, 0, 0 | |||
}; | |||
uint16_t const CRATE2FED[50] = { |
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.
Hi @vkhristenko @deguio- ok, so these are indeed not constant constants (as we had worried about last summer). So, are these only for online DQM? I guess the answer is no, as the tier0 sees problems. If not, how do we support 2016 data?
+1 |
The tests are being triggered in jenkins. |
This pull request is fully signed and it will be integrated in one of the next CMSSW_9_0_X IBs after it passes the integration tests. This pull request requires discussion in the ORP meeting before it's merged. @davidlange6, @smuzaffar |
David, I requested from Hcal that somehow this mapping is obtainable from within cmssw. HCAL Status is generated per FED and all of the monitoring is done in that at cDAQ, therefore when I was writing this I thought that it's quite prudent to see the status in a similar fashion without thinking of how to convert. However, there is a limitation of having to deal with this mapping.
What to do - is up to @deguio, @hatakeyamak and Hcal Operations. VK |
point taken. we will find a way to accomodate new and old detector together. |
-1 Tested at: b83b0f3 You can see the results of the tests here: I found follow errors while testing this PR Failed tests: RelVals
When I ran the RelVals I found an error in the following worklfows: runTheMatrix-results/136.731_RunSinglePh2016B+RunSinglePh2016B+HLTDR2_2016+RECODR2_2016reHLT_skimSinglePh_HIPM+HARVESTDR2/step4_RunSinglePh2016B+RunSinglePh2016B+HLTDR2_2016+RECODR2_2016reHLT_skimSinglePh_HIPM+HARVESTDR2.log10021.0 step5 runTheMatrix-results/10021.0_TenMuE_0_200+TenMuE_0_200_pythia8_2017_GenSimFull+DigiFull_2017+RecoFull_2017+ALCAFull_2017+HARVESTFull_2017/step5_TenMuE_0_200+TenMuE_0_200_pythia8_2017_GenSimFull+DigiFull_2017+RecoFull_2017+ALCAFull_2017+HARVESTFull_2017.log10024.0 step5 runTheMatrix-results/10024.0_TTbar_13+TTbar_13TeV_TuneCUETP8M1_2017_GenSimFull+DigiFull_2017+RecoFull_2017+ALCAFull_2017+HARVESTFull_2017/step5_TTbar_13+TTbar_13TeV_TuneCUETP8M1_2017_GenSimFull+DigiFull_2017+RecoFull_2017+ALCAFull_2017+HARVESTFull_2017.log10824.0 step5 runTheMatrix-results/10824.0_TTbar_13+TTbar_13TeV_TuneCUETP8M1_2018_GenSimFull+DigiFull_2018+RecoFull_2018+ALCAFull_2018+HARVESTFull_2018/step5_TTbar_13+TTbar_13TeV_TuneCUETP8M1_2018_GenSimFull+DigiFull_2018+RecoFull_2018+ALCAFull_2018+HARVESTFull_2018.log |
Comparison not run due to runTheMatrix errors (RelVals and Igprof tests were also skipped) |
Hum - problem is that it seems this pr breaks also 2017 mc?
David
On 3 Mar 2017, at 00:46, Federico De Guio <notifications@github.com<mailto:notifications@github.com>> wrote:
point taken. we will find a way to accomodate new and old detector together.
(not for 840 though)
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub<#17657 (comment)>, or mute the thread<https://github.com/notifications/unsubscribe-auth/AEzyw03xTKG1xYhY2CbXjDzk8GRM5uKTks5rh1SYgaJpZM4MO8U3>.
|
yes. With exactly the same problem as for 2016. Because of this mapping of crate2fed and fed2crate VK |
what a mess. this of course means that even the MC, the right information is available via the GT... but anyway, I would suggest that we just leave out the hcal dqm in the tier0 instead of breaking it everywhere else. |
I should have clarified, that the reverse (disable everywhere but tier0) is also fine in case that matches the priorities better. |
we need only online dqm - the rest can be switched off (offline workflows) for now until hcal sorts out the issue. and regarding MC and GT - it's not a question of GT. It's a question of what FEDs/Crates are at cDAQ for that MC VK |
"FEDs/Crates are at cDAQ for that MC" : is that not defined for MC in a GT or in code (we certainly don't get the info from P5 via a phone call / email:) ) ? |
David, we can discuss forever. Bottom line, what I mean is that I can not customize my application to account for a conversion from FED2Crate and from Crate2FED. May be I don't understand the joke.... all I'm trying to say is that I'm not able to customize that part, period. If hcal dpg decides they do not need that part - we will rewrite removing these dependencies completely. I hope we can close on this subject here. VK |
I guess I simply don't understand why beyond just not getting the needed small help from your conditions people. but ok, its silly for me to spend time getting hcal people to talk to other hcal people.
… On Mar 3, 2017, at 1:40 PM, Viktor Khristenko ***@***.***> wrote:
David, we can discuss forever.
Bottom line, what I mean is that I can not customize my application to account for a conversion from FED2Crate and from Crate2FED. May be I don't understand the joke.... all I'm trying to say is that I'm not able to customize that part, period. If hcal dpg decides they do not need that part - we will rewrite removing these dependencies completely. I hope we can close on this subject here.
VK
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.
|
will come back in a different form. Closing until that happens. |
Updates for HCAL DQM
VK