-
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
Support arbitrary path names in the TriggerResultsFilter in HLTPathStatus mode #36732
Support arbitrary path names in the TriggerResultsFilter in HLTPathStatus mode #36732
Conversation
please test |
+code-checks Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-36732/27831
|
A new Pull Request was created by @fwyzard (Andrea Bocci) for master. It involves the following packages:
@Martin-Grunewald, @missirol can you please review it and eventually sign? Thanks. cms-bot commands are listed here |
-1 Failed Tests: RelVals-INPUT RelVals-INPUT
Comparison SummarySummary:
|
…atus mode Other changes: - clean up and modernise the module - add a new unit test for the HLTPathStatus mode
b12fbfa
to
a729d1c
Compare
please test |
+code-checks Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-36732/27847
|
Pull request #36732 was updated. @Martin-Grunewald, @missirol can you please check and sign again. |
-1 Failed Tests: RelVals-INPUT RelVals-INPUT
Comparison SummarySummary:
|
|
||
# L1-like path name | ||
process.filter_l1path_pattern = triggerResultsFilter.clone( | ||
triggerConditions = ( 'L1_Path', ), |
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.
Hi @fwyzard, thanks for the PR. I just wanted to ask one clarification before signing it.
In the unit test, I see that the path L1_Path
always returns true
, but the corresponding TriggerResultFilter
(i.e. filter_l1path_pattern
) always returns false
(for filter_l1path_pattern
, I see that m_expression->patterns()
is empty). Is this related to how strings starting with L1_
are handled in TriggerExpressionParser.h
? Could you please elaborate a bit? (I admit I don't follow the details of this)
Yes, strings of the format "L1_Something" are always matched to L1 GT/uGT
trigger results, even if a corresponding path exists in CMSSW.
If I remember correctly the Phase-2 HLT menu uses "L1T_Something" for
L1-like selections.
|
+hlt |
This pull request is fully signed and it will be integrated in one of the next master IBs (but tests are reportedly failing). This pull request will now be reviewed by the release team before it's merged. @perrotta, @dpiparo, @qliphy (and backports should be raised in the release meeting by the corresponding L2) |
+1 |
merge |
PR description:
Support arbitrary path names in the TriggerResultsFilter in HLTPathStatus mode
Other changes:
PR validation:
The new unit tests should run.