-
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
Add upper cut on jet time to HLTJetTimingFilter #41089
Conversation
-code-checks Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-41089/34702
Code check has found code style and quality issues which could be resolved by applying following patch(s)
|
+code-checks Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-41089/34705
|
A new Pull Request was created by @ssantpur for master. It involves the following packages:
@cmsbuild, @missirol, @Martin-Grunewald can you please review it and eventually sign? Thanks. cms-bot commands are listed here |
For But, in general, I don't see why it's necessary to allow for 2 time windows in the same instance of the filter. Couldn't one simply have two instances of the filter (one per time window), and combine the resulting jet/egamma candidates later on if needed ? |
@missirol Please let me know if this is a problem and I can have two instances of the same filter instead. |
I think it's worth exploring the option of having 2 instances of the filter, before we complicate the logic of the filters themselves. Feel free to share the corresponding HLT configuration, so we can judge what is the cleaner option. |
+code-checks Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-41089/34825
|
Pull request #41089 was updated. @cmsbuild, @missirol, @Martin-Grunewald can you please check and sign again. |
-code-checks Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-41089/34827
Code check has found code style and quality issues which could be resolved by applying following patch(s)
|
@missirol |
|
Scratch this. There was a mistake in my previous comment. You can rebase on top of |
+code-checks Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-41089/34858
|
Pull request #41089 was updated. @SiewYan, @rappoccio, @kskovpen, @bbilin, @pmandrik, @Saptaparna, @Martin-Grunewald, @alberto-sanchez, @menglu21, @cecilecaillol, @GurpreetSinghChahal, @perrotta, @civanch, @vlimant, @makortel, @cmsbuild, @missirol, @fwyzard, @simonepigazzini, @mandrenguyen, @davidlange6, @smuzaffar, @Dr15Jones, @epalencia, @emanueleusai, @mdhildreth, @AdrianoDee, @syuvivida, @micsucmed, @fabiocos, @francescobrivio, @mkirsano, @swertz, @bsunanda, @clacaputo, @srimanob, @saumyaphor4252, @aloeliger, @sunilUIET, @tvami, @rvenditti can you please check and sign again. |
f43f616
to
1cc25cf
Compare
PR description:
This PR allows for more flexibility in choosing the timing thresholds for the delayed jet and delayed E/gamma triggers, this does not effect any existing triggers or their rates. The modification is to enable triggering on the negative timing region that can target beam halo and satellite collisions, and allow for maximum timing to be specified in the positive timing side to enable some delayed jet triggers to be added to parking dataset.
PR validation:
I ran over HLTPhysics using Run2022G dataset and saw no change in the rates.