-
Notifications
You must be signed in to change notification settings - Fork 4.3k
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
add commissioning_run
as runType
and use it in SiStrip online DQM client [12.0.X]
#35365
add commissioning_run
as runType
and use it in SiStrip online DQM client [12.0.X]
#35365
Conversation
A new Pull Request was created by @mmusich (Marco Musich) for CMSSW_12_0_X. It involves the following packages:
@emanueleusai, @ahmad3213, @cmsbuild, @jfernan2, @pmandrik, @pbo0, @rvenditti can you please review it and eventually sign? Thanks. cms-bot commands are listed here |
@cmsbuild, please test |
+1 Summary: https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-f04dd6/18820/summary.html Comparison SummarySummary:
|
please test |
+1 Summary: https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-f04dd6/19260/summary.html Comparison SummarySummary:
|
@qliphy we need to test this PR at P5, however for a full test, a Global Run of data taking where the DAQ shifter declares commissioning_run would be really desired, if I got it right |
@francescobrivio it's not urgent for the beam test. |
ok I understand! thanks for the explanation @mmusich! |
the validation can be done when Strip detector is switched on (planned for Wednesday/Thursday this week) |
@tsusa how was DQM supposed to validate this, is it ok to replay a cosmics run? @cms-sw/dqm-l2 |
@tvami the test needs a special DAQ configuration in order to fall into the new run Type proposed here. That's why it can't be done with past data |
ok, Tanja edited her message (#35365 (comment)), earlier it said "but we need the PR merged (and 12_0_3)". ok so we wait until Wednesday/Thursday this week, validate and then merge? Is that the plan? |
We are a week later, I wonder what the status for this is? |
From Tracker elog http://cmsonline.cern.ch/cms-elog/1124978:
|
Thanks @ahmad3213 your information appears to be correct, while the one reported above from @francescobrivio seems not. |
Yea you are right, I just copy/pasted the Tracker elog message assuming it was correct, but I did not double checked. Sorry about that! |
da80a05
to
da18851
Compare
Pull request #35365 was updated. @emanueleusai, @ahmad3213, @cmsbuild, @jfernan2, @pmandrik, @pbo0, @rvenditti can you please check and sign again. |
in the last commit I provide a reconstruction scenario for the new |
@cmsbuild please test |
+1 Summary: https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-f04dd6/19689/summary.html Comparison SummarySummary:
|
+1 |
This pull request is fully signed and it will be integrated in one of the next CMSSW_12_0_X IBs (tests are also fine) and once validation in the development release cycle CMSSW_12_1_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 |
backport of #34832 and #35691
PR description:
This PR adds a new DQM
runType
commissioning_run
in order to define a new clause in the SiStrip online client to be used when there are no physics triggers.PR validation:
At the moment none. to be further tested
if this PR is a backport please specify the original PR and why you need to backport that PR:
Original PR: #34832, to be tested in 2021 Commissioning data-taking