-
Notifications
You must be signed in to change notification settings - Fork 4.4k
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
Remove unused L1TCaloSummary DQM sequences causing issues with HCAL. #46482
Conversation
Also changes Calo Summary DQM configuration to use GT digis instead of test crate digis
cms-bot internal usage |
+code-checks Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-46482/42337 |
A new Pull Request was created by @aloeliger for master. It involves the following packages:
@antoniovagnerini, @cmsbuild, @nothingface0, @rvenditti, @syuvivida, @tjavaid can you please review it and eventually sign? Thanks. cms-bot commands are listed here |
Hi @aloeliger , Thanks for making the PR, I will test this in the local workflow I have and report back |
Hi @aloeliger , I pulled your PR into my working area for 14_1_0, and reran my step3. I now find the number of processed HCAL TPs in the HcalDigis validation is exactly the same between 14_1_0+PR and 14_1_0_pre7 🎉 |
Please test |
+1 Size: This PR adds an extra 20KB to repository Comparison SummarySummary:
|
simCaloStage2Layer1Digis.ecalToken = cms.InputTag("ecalDigis", "EcalTriggerPrimitives") | ||
simCaloStage2Layer1Digis.hcalToken = cms.InputTag("hcalDigis", "") |
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.
Just for my understanding, why is it okay to let this DQM cff modify simCaloStage2Layer1Digis
?
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.
The original simCaloStage2Layer1
is fed from simulated TPs. For emulation purposes here, it is likely better to have them fed from unpacked TPs, and look at the emulation results from that.
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.
Is this a separate instance used solely for DQM purposes, or is this DQM cff modifying the results of the L1T emulation itself (similarly to what happened with the bug that this PR is trying to fix) ?
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 sequence should only be for DQM instances, but since it isn't cloned, it is likely causing the same problem, now that you mention it. I'll fix that.
Thanks. Apparently needs to be backported at least to 14_0_X for coming 2024 MC 🤔 |
urgent |
indeed, it would be great to have a backport to 14_0 and 14_1 asap. Even though it is clear at this point that there is no issue with the HCAL TP, but rather an issue in the validation procedure. |
+code-checks Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-46482/42353 |
please test |
Pull request #46482 was updated. @aloeliger, @antoniovagnerini, @epalencia, @nothingface0, @rvenditti, @syuvivida, @tjavaid can you please check and sign again. |
+1 Size: This PR adds an extra 28KB to repository Comparison SummarySummary:
|
Some differences are observed in the bin-by-bin comparison in the WF |
In my understanding, it should modify them, restoring the correct ones (meaning, baseline results are bugged).
I'm not the relevant expert. I think the question should be directed to @cms-sw/l1-l2. |
Note that there is a comment to address in #46482 (comment). |
This is my understanding as well |
+dqm
|
+l1 |
+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 be automatically merged. |
merge |
PR description:
This PR removes two unused sequences in the CICADA DQM that were potentially causing duplicate TPs seen in HCAL tests. No DQM changes are expected as a result of this change.
Also changes Calo Summary DQM configuration to use GT digis instead of test crate digis, which is more correct.
@missirol FYI
@JHiltbrand Also FYI, but could I ask you to see if you can rerun the test you were looking at with this PR and see if this resolves the issue please?
PR validation:
Changed HCAL workflow was run-again to make sure that the sequence does not crash.
If this PR is a backport please specify the original PR and why you need to backport that PR. If this PR will be backported please specify to which release cycle the backport is meant for:
This PR is not a backport, but may need backporting to online/offline DQM releases.