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
update L3 filter, for 2017 online muon reconstruction #19465
Conversation
A new Pull Request was created by @sarafiorendi for master. It involves the following packages: HLTrigger/Muon @Martin-Grunewald, @silviodonato, @cmsbuild, @fwyzard, @davidlange6 can you please review it and eventually sign? Thanks. cms-bot commands are listed here |
} | ||
} //MTL loop | ||
|
||
|
||
if ( !( l1CandTag_ == edm::InputTag("")) && check_l1match && matchPreviousCand_){ |
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.
can you use
if (not l1CandTag_.label().empty() ...
instead, to avoid creating InputTag
s every time ?
@cmsbuild , please test |
The tests are being triggered in jenkins. |
+1 The following merge commits were also included on top of IB + this PR after doing git cms-merge-topic: |
Comparison job queued. |
Comparison is ready Comparison Summary:
|
Presumably we need a PR for 92X as well - please make one! |
This change kills off a few triggers (on 100 ttbar events) - new vs old:
eg, for HLT_Mu8, the event flow through all modules is
where this is the killing filter:
Please configure the default working of the new features to reproduce the old behaviour! |
Hi @Martin-Grunewald , this is expected, and in particular it is due to the change here
The modification in this PR are meant to update the filter to be used after L3 candidates are produced using the full iterL3 sequence. To conclude, I can introduce another configurable parameter which would make the filter use the globalTrack until we finally switch to the new menu, where L3FromL2 is replaced by full iterL3 everywhere. thanks |
If the new parameter is used only during the transition, I would rather not add it. Instead, can we pick one of these options:
.A |
+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 requires discussion in the ORP meeting before it's merged. @davidlange6, @smuzaffar |
Pull request #19465 was updated. @Martin-Grunewald, @silviodonato, @cmsbuild, @fwyzard, @davidlange6 can you please check and sign again. |
@cmsbuild, please test |
+1 |
The tests are being triggered in jenkins. |
This pull request is fully signed and it will be integrated in one of the next master IBs after it passes the integration tests. This pull request requires discussion in the ORP meeting before it's merged. @davidlange6, @smuzaffar |
+1 The following merge commits were also included on top of IB + this PR after doing git cms-merge-topic: |
Comparison job queued. |
Comparison is ready Comparison Summary:
|
+1 |
Update of the L3 filter in order to: