Git Product home page Git Product logo

Comments (6)

ktht avatar ktht commented on August 21, 2024

Regarding VBF jets, I think there's a bug in SL channel. Here the VBF jets are cleaned wrt the W->jj jets as identified by the JPA:

cleanedJetsAK4_vbf = jetCleanerAK4_dR08(cleanedJetsAK4_wrtHbb, overlaps);

The AK4 jets that are cleaned wrt the selected H->bb AK8 jet is done here:
cleanedJetsAK4_wrtHbb = jetCleanerAK4_dR12(selJetsAK4, std::vector<const RecoJetBase*>({ selJetAK8_Hbb }));

But the jets that enter the cleaning are central jets:
const std::vector<const RecoJet*> selJetsAK4 = jetSelectorAK4_wPileupJetId(cleanedJetsAK4_wrtLeptons, isHigherPt);

I believe this is by a mistake. I'll reorganize the code a bit because in the synchronization we agreed to record the number of VBF jets:

  • after the selection;
  • after the selection and cleaning wrt the fakeable leptons,
  • after the selection, cleaning wrt the fakeable leptons, and wrt other jets.

from hh-bbww.

veelken avatar veelken commented on August 21, 2024

Hi Karl,

sorry, I don't understand where you see a problem. The AK4 jets that are selected by the JPA are central AK4 jets (|eta| < 2.4). The VBF jets are cleaned wrt the AK4 jets selected by the JPA in these lines:

// select VBF jet candidates
std::vector<const RecoJet*> cleanedJetsAK4_vbf;
if ( selJetAK8_Hbb ) {
std::vector<const RecoJetBase*> overlaps;
if ( selJet1_Wjj ) overlaps.push_back(selJet1_Wjj);
if ( selJet2_Wjj ) overlaps.push_back(selJet2_Wjj);
cleanedJetsAK4_vbf = jetCleanerAK4_dR08(cleanedJetsAK4_wrtHbb, overlaps);
} else {
std::vector<const RecoJetBase*> overlaps;
if ( selJet1_Hbb ) overlaps.push_back(selJet1_Hbb);
if ( selJet2_Hbb ) overlaps.push_back(selJet2_Hbb);
if ( selJet1_Wjj ) overlaps.push_back(selJet1_Wjj);
if ( selJet2_Wjj ) overlaps.push_back(selJet2_Wjj);
cleanedJetsAK4_vbf = jetCleanerAK4_dR08(cleanedJetsAK4_wrtLeptons, overlaps);
}
const std::vector<const RecoJet*> selJetsAK4_vbf = jetSelectorAK4_vbf(cleanedJetsAK4_vbf, isHigherPt);

This looks correct to me.

from hh-bbww.

ktht avatar ktht commented on August 21, 2024

This part is ok, the problem I think is that cleanedJetsAK4_wrtHbb originates from

cleanedJetsAK4_wrtHbb = jetCleanerAK4_dR12(selJetsAK4, std::vector<const RecoJetBase*>({ selJetAK8_Hbb }));

where selJetsAK4 are defined here:
const std::vector<const RecoJet*> selJetsAK4 = jetSelectorAK4_wPileupJetId(cleanedJetsAK4_wrtLeptons, isHigherPt);

The jetSelectorAK4_wPileupJetId selector does not include jets beyond the acceptance region:
RecoJetCollectionSelector jetSelectorAK4_wPileupJetId(era, -1, isDEBUG);
jetSelectorAK4_wPileupJetId.getSelector().set_pileupJetId(apply_pileupJetID);

So, if I'm reading the code correctly, it only considers central jets as the VBF jets in the boosted category.

from hh-bbww.

ktht avatar ktht commented on August 21, 2024

The pT cut on VBF jets was set to 30 GeV in commit 8d614f1 but there is no explanation why the pT cut was raised:

jetSelectorAK4_vbf.getSelector().set_min_pt(30.);

Was this cut taken from bbtautau analysis, maybe?

In any case, the pT cut in our gitlab is still at 25 GeV, so I'll change it back to 25 in my PR, too. Other groups have already synchronized in the VBF jet variables, but we're not.

edit: indeed, the pT > 30 GeV cut was mentioned in bbtautau AN (AN2018/121v4, L291)

from hh-bbww.

veelken avatar veelken commented on August 21, 2024

Hi Karl,

the VBF jet pT > 30 GeV cut was indeed taken from the HH->bbtautau analysis (cf. slide 5 of https://indico.cern.ch/event/963619/contributions/4118889/attachments/2149275/3623492/statusReport_24_11_2020.pdf ). I would prefer if we keep using the 30 GeV cut for VBF jets, if we can convince the Aachen and Louvain groups to switch to 30 GeV, for two reasons:

  1. It will make the documentation and combination of datacards easier if we use the same VBF jet cuts as the HH->bbtautau analysis
  2. The VBF jets are reconstructed outside of the tracking acceptance, so are more affected by pileup and potential miscalibration and/or noise of the calorimeters. My understanding is that the official JetMET recommendation is to use jets of pT > 30 GeV (for b-jets/jets within the tracking acceptance, we get permission to reduce the pT threshold to 25 GeV, because central jets depend more on the track reconstruction and are less affected by pileup and potential miscalibration and/or noise of the calorimeters)

from hh-bbww.

ktht avatar ktht commented on August 21, 2024

Thank you, Christian. I had no strong preference before because we already apply PU jet ID cut also on the VBF jets, so reducing the pT cut by 5 GeV shouldn't make much difference. But I take your point that it's best to keep the common definitions across different HH analyses as similar as possible. I'll let the other groups know that we should use pT > 30 GeV cut for the VBF jets.

from hh-bbww.

Related Issues (20)

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.