Vhbb heppy722patch2 taustuff

[arizzi]

replaces #13 and #15
@veelken

[veelken]

Hi Andrea,

thank you very much for merging the pull requests.

I see only 1 sample that we need for the tth study:
/TTbarH_HToTauTau_M-125_13TeV_amcatnlo-pythia8-tauola/Phys14DR-AVE30BX50_tsg_PHYS14_ST_V1-v1/MINIAODSIM

I am looking at the VHbb Ntuples now and I notice that TBrowser->Inspect does not tell me the type of the branches.
Could you tell me how you read e.g.
Jet_pt
?

Thank you,

Christian

[arizzi]

Try tree->sprint()
Il 01/mar/2015 14:08 "Christian Veelken" [email protected] ha
scritto:

Hi Andrea,

thank you very much for merging the pull requests.

I see only 1 sample that we need for the tth study:

/TTbarH_HToTauTau_M-125_13TeV_amcatnlo-pythia8-tauola/Phys14DR-AVE30BX50_tsg_PHYS14_ST_V1-v1/MINIAODSIM

I am looking at the VHbb Ntuples now and I notice that TBrowser->Inspect
does not tell me the type of the branches.
Could you tell me how you read e.g.
Jet_pt
?

Thank you,

Christian

—
Reply to this email directly or view it on GitHub
#17 (comment).

[arizzi]

I meant print ... Not sprint
Il 01/mar/2015 14:09 "Andrea Rizzi" [email protected] ha scritto:

Try tree->sprint()
Il 01/mar/2015 14:08 "Christian Veelken" [email protected] ha
scritto:

Hi Andrea,

thank you very much for merging the pull requests.

I see only 1 sample that we need for the tth study:

/TTbarH_HToTauTau_M-125_13TeV_amcatnlo-pythia8-tauola/Phys14DR-AVE30BX50_tsg_PHYS14_ST_V1-v1/MINIAODSIM

I am looking at the VHbb Ntuples now and I notice that TBrowser->Inspect
does not tell me the type of the branches.
Could you tell me how you read e.g.
Jet_pt
?

Thank you,

Christian

—
Reply to this email directly or view it on GitHub
#17 (comment).

[veelken]

Ok, I did tree->Print() and I see now that the branches are stored as Double_t or Int_t [*].

The number of entries in the branch matches the number of processed events (98 in my case), however, so I think I am still missing something.

Do you store the information for jets as Double_t[nJet] or std::vector<Double_t> in order to handle more than one jet per event ?

I noticed that the list of triggers defined in VHbbAnalysis/Heppy/test/vhbb.py does not contain the lepton+tau and double-tau triggers that we need for the tth analysis yet. I am wondering if I can just add these triggers to the TrigAna.triggerBits config with new keys (e.g. "EleTau") or do the keys need to match a certain naming scheme ?

I noticed also that the matching of offline reconstructed leptons (e, mu, tau) to the HLT trigger objects is not present in the Ntuple yet. Can you remind me how you do the trigger matching (or does this still need to be implemented ?)

[*]

............................................................................
*Br 457 :Jet_mass : *

•     | Double_t mass for Cental+fwd jets after full selection and cleaning, sorted by b-tag*
  

  Entries : 98 : Total Size= 7555 bytes File Size = 4050 *
  *Baskets : 1 : Basket Size= 32000 bytes Compression= 1.71 *
  *............................................................................

[arizzi]

Hi,
yes the information is store as Jet_pt[nJet], Jet_eta[nJet] etc..

yes you can add your triggers there.

Concerning the trigger matching we should check if something already exists
from the CMG side but for sure we (VH) did not implement it.

PS: I'm surprised we are storing as Double rather than Float... a bug
perhaps... let me see

On Sun, Mar 1, 2015 at 2:25 PM, Christian Veelken [email protected]
wrote:

Ok, I did tree->Print() and I see now that the branches are stored as
Double_t or Int_t [*].

The number of entries in the branch matches the number of processed events
(98 in my case), however, so I think I am still missing something.

Do you store the information for jets as Double_t[nJet] or std::vector in
order to handle more than one jet per event ?

I noticed that the list of triggers defined in
VHbbAnalysis/Heppy/test/vhbb.py does not contain the lepton+tau and
double-tau triggers that we need for the tth analysis yet. I am wondering
if I can just add these triggers to the TrigAna.triggerBits config with new
keys (e.g. "EleTau") or do the keys need to match a certain naming scheme ?

I noticed also that the matching of offline reconstructed leptons (e, mu,
tau) to the HLT trigger objects is not present in the Ntuple yet. Can you
remind me how you do the trigger matching (or does this still need to be
implemented ?)

[*]

............................................................................
*Br 457 :Jet_mass : *

• | Double_t mass for Cental+fwd jets after full selection and
  cleaning, sorted by b-tag* Entries : 98 : Total Size= 7555 bytes File
  Size = 4050 * *Baskets : 1 : Basket Size= 32000 bytes Compression= 1.71 *
  *............................................................................

—
Reply to this email directly or view it on GitHub
#17 (comment).

[arizzi]

please make a PR adding the dataset in datasets.txt and the trigger bits in vhbb.py

[veelken]

Ok, the changes are included in PR #19