-
Notifications
You must be signed in to change notification settings - Fork 4.5k
[15_0_X] [L1T] Implementing sector based mode 7 promotion in EMTF for Run 3 2025 #48424
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
base: CMSSW_15_0_X
Are you sure you want to change the base?
[15_0_X] [L1T] Implementing sector based mode 7 promotion in EMTF for Run 3 2025 #48424
Conversation
A new Pull Request was created by @eyigitba for CMSSW_15_0_X. It involves the following packages:
@BenjaminRS, @cmsbuild, @quinnanm can you please review it and eventually sign? Thanks. cms-bot commands are listed here |
cms-bot internal usage |
please test |
backport of #48423 |
+1 Size: This PR adds an extra 36KB to repository Comparison SummarySummary:
|
+l1 |
This pull request is fully signed and it will be integrated in one of the next CMSSW_15_0_X IBs (tests are also fine) and once validation in the development release cycle CMSSW_15_1_X is complete. This pull request will now be reviewed by the release team before it's merged. @mandrenguyen, @sextonkennedy, @antoniovilela, @rappoccio (and backports should be raised in the release meeting by the corresponding L2) |
assign ppd |
PR description:
This PR implements the new sector based quality promotion of mode 7 tracks. The firmware was deployed On June 6th, the first run with this firmware is 393039. The JIRA is here: https://its.cern.ch/jira/browse/CMSLITOPS-511
This change in the emulator is required to keep the emulator in line with the firmware. This is not critical for data taking, but it's used in DQM data-emulator comparisons and also in MC production.
PR validation:
Validated with running on data from before/after run 393039 and also with MC. Works as expected.
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 is the backport of #48423