Skip to content
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

implementation of WH(tautau) analysis #216

Merged
merged 7 commits into from
Apr 28, 2023
Merged

implementation of WH(tautau) analysis #216

merged 7 commits into from
Apr 28, 2023

Conversation

ralfschmieder
Copy link
Contributor

No description provided.

Copy link
Contributor

@harrypuuter harrypuuter left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Some smaller remarks; the rest looks fine ! (although I did not check the triple selection code, since you are the only user of it ;) )

return ROOT::Math::PtEtaPhiEVector(default_float,default_float,default_float,
default_float);;
auto dileptonsystem = p4_1 + p4_2;
auto dileptonsystem_scaled = 0.47*dileptonsystem;
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

why not use a more generic implementation, where you can configure this correction factor ? From what I see, the lt and tt functions are identical apart from the 0.47 and the 0.69

///
/// \returns a dataframe with the new column

ROOT::RDF::RNode Lt(ROOT::RDF::RNode df, const std::string &outputname,
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

choose a more descriptive name like sum_pts()

///
/// \returns a dataframe with the new column

ROOT::RDF::RNode eta_vis(ROOT::RDF::RNode df, const std::string &outputname,
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

a more descriptive name, maybe pair_eta ?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think it is more consistent to use eta_vis and phi_vis, since we have also m_vis and pt_vis

///
/// \returns a dataframe with the new column

ROOT::RDF::RNode phi_vis(ROOT::RDF::RNode df, const std::string &outputname,
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

same as above

const ROOT::Math::PtEtaPhiMVector &p4_2) {
if (p4_1.pt() < 0.0 || p4_2.pt() < 0.0)
return ROOT::Math::PtEtaPhiEVector(default_float,default_float,default_float,
[p4_miss_sf](const ROOT::Math::PtEtaPhiMVector &p4_23) {
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

use general names here: scale and p4 should be fine

Copy link
Contributor

@harrypuuter harrypuuter left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

👍🏼

@harrypuuter harrypuuter merged commit 92c6651 into main Apr 28, 2023
@harrypuuter harrypuuter deleted the wh_analysis branch April 28, 2023 14:55
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants