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 #41185
Added option to trigger on loose HMT showers in EMTF #41185
Conversation
+code-checks Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-41185/34871
|
A new Pull Request was created by @eyigitba for master. It involves the following packages:
@epalencia, @cmsbuild, @cecilecaillol, @aloeliger 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-f11ca3/31591/summary.html Comparison SummarySummary:
|
+l1 |
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, @rappoccio (and backports should be raised in the release meeting by the corresponding L2) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Very minor comments
@eyigitba @aloeliger please decide whether you think it is worth implementing them, or if you are really hurried up and want to merge right now. (In any case, applying the text fixes, rerunning the tests, and re-signing for L1 can take less than half a day: perhaps it cold be already merged in time for the 2300 IB, if you act quickly).
enableTwoLooseShowers_ = pset.getParameter<bool>("enableTwoLooseShowers"); | ||
enableOneNominalShower_ = pset.getParameter<bool>("enableOneNominalShowers"); | ||
enableOneTightShower_ = pset.getParameter<bool>("enableOneTightShowers"); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think these are the wrong name for these things now? Should be Shower
?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
yes, exactly. Apparently I missed these. I changed them now.
Ahh, already got it by the time I said that. |
+code-checks Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-41185/34893
|
Pull request #41185 was updated. @epalencia, @cmsbuild, @cecilecaillol, @aloeliger can you please check and sign again. |
please test |
+1 Summary: https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-f11ca3/31619/summary.html Comparison SummarySummary:
|
+l1 |
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, @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 PR will be backported to 13_0_X, but it depends also on the backport of #40890