-
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
Added option to trigger on loose HMT showers in EMTF #41209
Added option to trigger on loose HMT showers in EMTF #41209
Conversation
A new Pull Request was created by @eyigitba for CMSSW_13_0_X. It involves the following packages:
@epalencia, @cmsbuild, @cecilecaillol, @aloeliger can you please review it and eventually sign? Thanks. cms-bot commands are listed here
|
backport of #41185 |
please test |
+1 Summary: https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-8507e2/31642/summary.html Comparison SummarySummary:
|
+l1 |
This pull request is fully signed and it will be integrated in one of the next CMSSW_13_0_X IBs (tests are also fine) and once validation in the development release cycle CMSSW_13_1_X is complete. This pull request will now be reviewed by the release team before it's merged. @perrotta, @dpiparo, @rappoccio (and backports should be raised in the release meeting by the corresponding L2) |
+1 |
PR description:
Starting from 2023 we will trigger on loose showers in EMTF. This information will be used in uGMT to build the
TwoLooseDiffSectorInTime
trigger.I also cleaned the configurable parameters
nLooseShowers_
,nNominalShowers_
, andnTightShowers_
. The number of showers is already indicated in the boolean name and these configurables don't really add any configuration options. i.e the condition forhasOneNominalInTime
should always be one or more showers.The data format changes were done in #40890 and uGMT logic update is done in #41042
PR validation:
Validated by producing ntuples which had expected amount of loose showers.
Also ran
runTheMatrix.py -l limited -i all --ibeos
with no failures.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 a backport of #41185