-
Notifications
You must be signed in to change notification settings - Fork 4.2k
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
BMTF-KMTF DQM Algo Selector for the DQM/L1TMonitor Subsystem #24557
BMTF-KMTF DQM Algo Selector for the DQM/L1TMonitor Subsystem #24557
Conversation
The code-checks are being triggered in jenkins. |
-code-checks Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-24557/6441 Code check has found code style and quality issues which could be resolved by applying a patch in https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-24557/6441/git-diff.patch You can run |
@panoskatsoulis Could you please make sure that there is a name of a subsystem in the title of the PR? |
The code-checks are being triggered in jenkins. |
+code-checks Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-24557/6458 |
A new Pull Request was created by @panoskatsoulis for master. It involves the following packages: DQM/L1TMonitor @cmsbuild, @andrius-k, @kmaeshima, @schneiml, @nsmith-, @rekovic, @jfernan2, @thomreis can you please review it and eventually sign? Thanks. cms-bot commands are listed here |
@andrius-k I've changed the title, I hope this is what you were talking about |
please test |
The tests are being triggered in jenkins. |
Comparison is ready Comparison Summary:
|
+1 |
+1 |
This pull request is fully signed and it will be integrated in one of the next master IBs (tests are also fine). This pull request will now be reviewed by the release team before it's merged. @davidlange6, @slava77, @smuzaffar, @fabiocos (and backports should be raised in the release meeting by the corresponding L2) |
+1 |
This pull request is causing segmentation faults in the nightly release validation for workflow 136.8562. E.g. |
Hello,
this seems to come from a try to read a bx that is not present (maybe
because of Zero Suppression).
Can you please send me the workflow to reproduce it?
Maybe an "if" check can be used there.
Kind Regards,
Panos
…On 24/09/18 15:04, Chris Jones wrote:
This pull request is causing segmentation faults in the nightly
release validation for workflow 136.8562. E.g.
https://cmssdt.cern.ch/SDT/cgi-bin/logreader/slc7_amd64_gcc820/CMSSW_10_3_X_2018-09-23-2300/pyRelValMatrixLogs/run/136.8562_RunZeroBias1_hBStarRP+RunZeroBias1_hBStarRP+HLTDR2_2018_hBStar+RECODR2_2018reHLT_Prompt_hBStar+HARVEST2018_hBStar/step3_RunZeroBias1_hBStarRP+RunZeroBias1_hBStarRP+HLTDR2_2018_hBStar+RECODR2_2018reHLT_Prompt_hBStar+HARVEST2018_hBStar.log#/444-444
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#24557 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AU_Y_ciPsUCpaSHE_Y8BiyofUmEleZXjks5ueNhMgaJpZM4Wq-0o>.
|
|
Thanks for this, I will reply back once I have results.
Panos
…On 24/09/18 16:03, Chris Jones wrote:
|runTheMatrix -l 136.8562| should be able to reproduce the problem.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#24557 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AU_Y_ZCZogtwZ4tKCdYaCEguDPV-NlQnks5ueOYvgaJpZM4Wq-0o>.
|
Hello,
when I run the command
"|runTheMatrix -l 136.8562"|||
I cannot fetch the files using DAS. The requested files by the workflow
136.8562 are not to accessible place for me.
Below are the available sited I get by the das query.
T0_CH_CERN_Export
T0_CH_CERN_MSS
T1_US_FNAL_Buffer
T1_US_FNAL_MSS
However, the problem has been spotted since I have the run number now.
The PR 24557 introduces software that is necessary when the BMTF fw runs
with 2 algorithms.
The used run by the test, 314276, is an old run that only one algorithm
runs on the BMTF fpga.
What happened is that the MP7 header is suppressed because all the BXs
are also suppressed.
The L1TBMTFAlgoSelector plugin tries to fetch information from this
header that is not present.
This was not expected to happen because on newer runs the ZS for the
second algorithm is disabled.
The newly added L1TBMTFAlgoSelector is not intended to run under these
circumstances.
The code must be extended to cover such cases.
I will prepare a new PR for the master to fix this. How much urgent is this?
Also, could you please send me an other workflow (old enough) that the
files will be available?
It will be very useful, for debugging this.
Kind Regards,
Panos
…On 24/09/18 16:03, Chris Jones wrote:
|runTheMatrix -l 136.8562| should be able to reproduce the problem.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#24557 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AU_Y_ZCZogtwZ4tKCdYaCEguDPV-NlQnks5ueOYvgaJpZM4Wq-0o>.
|
@panoskatsoulis If you are running your test on CERN infrastructure (lxplus or similar), try running |
It seems this PR also creates the following problem in a TSG HIon workflow:
as verified using CMSSW_10_3_X_2018-09-23-1100 (OK) vs CMSSW_10_3_X_2018-09-23-1100 + this PR (fatal exception). It may be related to the problem discussed above. The cmsDriver command is:
|
The issue about the SEGFAULT is solved in the PR #24652 |
Looks like your bug fix also cures the fatal exception I observed in our TSG tests. Thanks! |
@Martin-Grunewald |
Yes, I added the bug fix PR and reran my tests. |
Great. |
This is the introduction of a new DQM plugin that selects the correct output muons of the BMTF depending on the algorithm that is triggering (Kalman BMTF/ Legacy BMTF).
Also, the PR includes the last BMTF Unpacker which is required by the DQM workflow and by the L1TBMTFAlgoSelector to operate correctly