-
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
Enable GEM trigger clusters from EMTF in GEM L1T DQM #35666
Enable GEM trigger clusters from EMTF in GEM L1T DQM #35666
Conversation
+code-checks Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-35666/25946
|
A new Pull Request was created by @dildick (Sven Dildick) for master. It involves the following packages:
@emanueleusai, @ahmad3213, @cmsbuild, @rekovic, @jfernan2, @pmandrik, @cecilecaillol, @pbo0, @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-c7f842/19619/summary.html Comparison SummarySummary:
|
@jfernan2 If we want this to be available at P5 for the upcoming test-beam, does it have to be backported to CMSSW_12_0_X? |
Yes, we need backport to 12_0_X On the other hand, some GEM plots lose stats while others gain, is this expected? |
Before this change, only the "emulated" GEM trigger clusters made any sense. "data" was a copy of "emulated" and "diff" was empty by definition. |
It looks like I shifted the histograms 1 bin to the right... I need to fix that. |
please test |
please test |
+1 Summary: https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-c7f842/19638/summary.html Comparison SummarySummary:
|
@dildick please check that everything looks as expected: |
Looks good. Thanks @jfernan2. |
+1 |
@rekovic Can you sign off, please? There is no update in the emulation, just a test L1T configuration. |
ping @cms-sw/l1-l2 |
@dildick #35666 (comment). |
+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 (and backports should be raised in the release meeting by the corresponding L2) |
+1 |
@jfernan2 Does it make sense to do a backport of the changes in DQM/L1TMonitor to update the DQM for ongoing tests at P5? |
@jfernan2 Actually, it turns out that this PR is incomplete. In a GEM-CSC trigger meeting I found out that the GEM DAQ works very different: rather than only reading out BX0, it integrates over 7BX [BX-3, BX-2, BX-1, BX0, BX+1, BX+2, BX+3] and then assigns the DAQ data to BX0... To do data-vs-emulation comparisons, I'll need to add a feature in the L1T DQM that first gets all the GEM clusters, then sets their BX to BX0, and then does the comparison. So I need to fix this PR before doing any backports! Sorry! |
OK, just let us know. |
PR description:
Data vs emulation for GEM TPs in GEM L1T DQM. The purpose of this PR is not to figure out the differences, but rather update the L1T GEM DQM for Run-3. Basically,
valMuonGEMPadDigiClusters
is replaced withemtfStage2Digis
since we now have GEM trigger data arriving at the EMTF. The data is not necessarily good, and I think it shows in the data-vs-emulation plots.PR validation:
Tested on 10k events of RAW Run-3 data, run 344064. There are many differences, to be discussed at GEM-CSC meetings.
GEM_dataVsEmul_CMS_Run_344064.pdf
Instructions to reproduce the slides on lxplus:
if this PR is a backport please specify the original PR and why you need to backport that PR:
N/A