-
Notifications
You must be signed in to change notification settings - Fork 4.4k
Include CICADA v2.2.0 configuration as modification to 2025 L1T Era #47423
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
Conversation
cms-bot internal usage |
+code-checks Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-47423/43818
|
Pull request #47423 was updated. |
please test with cms-sw/cmsdist#9709 |
+1 Size: This PR adds an extra 16KB to repository The following merge commits were also included on top of IB + this PR after doing git cms-merge-topic: You can see more details here: Comparison SummarySummary:
|
please test |
+1 Size: This PR adds an extra 16KB to repository Comparison SummarySummary:
|
The changes in triggers here are lost CICADA triggers in 2025. Since this is a change of the 2025 model to a generally lower score output model, this is entirely expected |
+l1 |
@aloeliger if this PR is ready to be reviewed by the release team, please remove the "Draft" status. |
+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. |
A new Pull Request was created by @aloeliger for master. It involves the following packages:
can you please review it and eventually sign? Thanks. cms-bot commands are listed here |
PR description:
This PR updates the CICADA L1T Emulator to the proposed model version v2.2.0 for 2025 running. This PR is dependent on cms-sw/cmsdist#9709
PR validation:
The python pathing has been tested to work. The CICADA model has been tested locally to run and provide model accurate CICADA scores.
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 will need to be ported to the eventual data-taking release, whether if that is different from the current cycle.