umd-lhcb / lhcb-ntuples-gen

ntuples generation with DaVinci and in-house offline components
BSD 2-Clause "Simplified" License
1 stars 0 forks source link

Check of wrong-sign samples reconstruction #48

Closed manuelfs closed 4 years ago

manuelfs commented 4 years ago

In the current version of reco_Dst_D0.py, Yipeng reconstructs three wrong-sign trees

The first is the wrong-sign muon for the D0mu sample, the second the wrong-sign muon for the D*+mu sample, and the third the wrong-sign pion which gives combinatorial D*+ mesons in the D*+mu sample. They all look correct to me. This is how Phoebe defined the wrong-sign samples for the D*+mu sample in the Run 1 ANA note

image

For reference, the correct-sign trees are

yipengsun commented 4 years ago

Also, as we discussed in Tuesday's meeting, you should also check the RequiredSelections of the wrong-sign selections to make sure my logic is correct.

For example, the B0 -> D* Mu, wrong-sign Mu uses:

sel_D0_ws_combo
pr_all_loose_Pi
sel_Mu_ws_combo

as inputs, and you should see if you agree with my choice of input.

manuelfs commented 4 years ago

Checked the inputs to the three wrong sign trees, and I think they are correct (and it was not easy, good job Yipeng!).

There are some inputs that are only used to apply the stripping cuts such as sel_Dst_ws_Mu and sel_Mu_ws_combo. Since wrong-sign trees only make sense in data, which is always stripped, these inputs are redundant and could be removed to clean up the code, but it is fine if they stay.

Specifically, I checked the TupleBminusWS inputs

Checked the TupleB0WSMu inputs

Checked the TupleB0WSPi inputs