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
restrict NHF-cut to eta<2.4 to prevent it from being applied in the HF #14095
restrict NHF-cut to eta<2.4 to prevent it from being applied in the HF #14095
Conversation
A new Pull Request was created by @kirschen for CMSSW_8_1_X. It involves the following packages: HLTrigger/JetMET @Martin-Grunewald, @perrotta, @cmsbuild, @fwyzard, @davidlange6 can you please review it and eventually sign? Thanks. cms-bot commands are list here #13028 |
please test |
The tests are being triggered in jenkins. |
+1 |
This pull request is fully signed and it will be integrated in one of the next CMSSW_8_1_X IBs after it passes the integration tests. This pull request requires discussion in the ORP meeting before it's merged. @slava77, @davidlange6, @Degano, @smuzaffar |
+1 The following merge commits were also included on top of IB + this PR after doing git cms-merge-topic: |
Hi @kirschen - I don't really follow this change. What is the difference with respect to just disabling the nhf cut completely? |
Hi @davidlange6 , this change was discussed in The NHF-cut is still to be applied in the tracker-covered region. However, if applied in HF it is doing harm after PF-reconstruction changes, because the "usual" PF-HF jet has close to 100% neutral hadron fraction. That is why it was dropped from offline JetId-recommendations https://twiki.cern.ch/twiki/bin/viewauth/CMS/JetID#Recommendations_for_13_TeV_data and this just propagates this change to the HLT. |
+1 ah - NHF does not stand for what I thought it did.. Thx. |
JetID-fix for 2016 datataking