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
Allow for ME0 triggers to be produced from pads directly #27731
Allow for ME0 triggers to be produced from pads directly #27731
Conversation
The code-checks are being triggered in jenkins. |
-code-checks Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-27731/11361
Code check has found code style and quality issues which could be resolved by applying following patch(s)
|
The code-checks are being triggered in jenkins. |
+code-checks Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-27731/11362
|
A new Pull Request was created by @dildick (Sven Dildick) for master. It involves the following packages: L1Trigger/ME0Trigger @cmsbuild, @rekovic, @benkrikler, @kpedro88 can you please review it and eventually sign? Thanks. cms-bot commands are listed here |
please test workflow 20034.0 |
The tests are being triggered in jenkins. |
Comparison job queued. |
Comparison is ready Comparison Summary:
|
Pull request #27731 was updated. @cmsbuild, @rekovic, @benkrikler, @kpedro88 can you please check and sign again. |
please test |
The tests are being triggered in jenkins. |
Comparison job queued. |
Comparison is ready Comparison Summary:
|
+upgrade |
@rekovic @benkrikler do you have comments about this PR? |
I am fine with this PR. We don't need to backport this to phase2-l1t-offline, as there should be no change in performance, so I would rather not push it there. |
+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 |
PR description:
Recent hardware developments by the GEM group argue for an FPGA-less ME0 front-end electronics design. This means that trigger pad clusters will not be produced in the L1-trigger chain during Phase-2. This is the currently the case in the simulation though. In Phase-2, ME0 triggers will be constructed out of trigger pads directly. This PR updates the simulation accordingly. More details can be found in this presentation: https://indico.cern.ch/event/831338/contributions/3482241/attachments/1869796/3079349/Change-ME0-001_CMS_Black.pdf.
I added a flag in the configuration to choose the input (pad or pad cluster). Other modifications include additional member data and a function that was templated.
PR validation:
I ran the workflow 20034.0 successfully.
There should be no change in the performance as ME0 pseudo-triggers are still the actual objects that are used in the L1T Muon chain.
FYI: @jshlee @tahuang1991 @rekovic