-
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
L1T DQM: Adding the uGT timing sequence back and updating the relevant algo list #38840
Conversation
…on L1Menu_Collisions2022_v1_0_1
+code-checks Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-38840/31228
|
A new Pull Request was created by @vukasinmilosevic (Vukasin Milosevic) for master. It involves the following packages:
@emanueleusai, @ahmad3213, @cmsbuild, @jfernan2, @pmandrik, @micsucmed, @rvenditti can you please review it and eventually sign? Thanks. cms-bot commands are listed here |
please test |
+1 Summary: https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-afe092/26426/summary.html Comparison SummarySummary:
|
type l1t |
+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. @perrotta, @dpiparo, @qliphy, @rappoccio (and backports should be raised in the release meeting by the corresponding L2) |
This PR is adding quite several warning lines in the logs of several workflows, for example wf1306.0:
Please add the new modules only when needed/available, e.g. by using relevant modifiers |
By the way, even the baseline shows for the same wf the following warning messages
I imagine there are other modules in that sequence that should also get protected behind relevant modifiers |
ping @vukasinmilosevic |
Hi @qliphy, @perrotta, apologies for the delay in response. Ok, this seems like it is complaining due to the L1 menu for 2016 lacking the triggers used in 17/18 and Run 3. I can add the protections, but could you please point me to the instructions on how to do so (apologies if this is a basic question)? |
You can configure for the different data taking periods using the corresponding eras, see e..g. https://twiki.cern.ch/twiki/bin/view/CMSPublic/SWGuideCmsDriverEras |
Pull request #38840 was updated. @emanueleusai, @ahmad3213, @cmsbuild, @jfernan2, @pmandrik, @micsucmed, @rvenditti can you please check and sign again. |
from Configuration.StandardSequences.Eras import eras | ||
|
||
eras.run3_common.toReplaceWith(l1tStage2uGTOnlineDQMSeq, _run3_l1tStage2uGTOnlineDQMSeq) |
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.
Thank you @vukasinmilosevic , it should work
Looking at the examples around, the correct way to code it is
from Configuration.StandardSequences.Eras import eras | |
eras.run3_common.toReplaceWith(l1tStage2uGTOnlineDQMSeq, _run3_l1tStage2uGTOnlineDQMSeq) | |
from Configuration.Eras.Modifier_run3_common_cff import run3_common | |
run3_common.toReplaceWith(l1tStage2uGTOnlineDQMSeq, _run3_l1tStage2uGTOnlineDQMSeq) |
@@ -28,7 +28,14 @@ | |||
# sequences | |||
l1tStage2uGTOnlineDQMSeq = cms.Sequence( | |||
l1tStage2uGT + | |||
# l1tStage2uGTTiming + | |||
# l1tStage2uGTTiming + |
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.
This can be removed, you can now compare with the other sequence to identify what's missing
# l1tStage2uGTTiming + |
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.
Thank you @perrotta! I've tested the suggested changes with a Run 3 input file and the timing plots are there as well.
+code-checks Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-38840/31794
|
Pull request #38840 was updated. @emanueleusai, @ahmad3213, @cmsbuild, @jfernan2, @pmandrik, @micsucmed, @rvenditti can you please check and sign again. |
please test |
+1 Summary: https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-afe092/27088/summary.html Comparison SummarySummary:
|
+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. @perrotta, @dpiparo, @rappoccio (and backports should be raised in the release meeting by the corresponding L2) |
+1 |
L1T DQM update: