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

WP on Z' samples should have the option to be based on ttbar #163

Open
samvanstroud opened this issue Mar 3, 2023 · 3 comments
Open

WP on Z' samples should have the option to be based on ttbar #163

samvanstroud opened this issue Mar 3, 2023 · 3 comments

Comments

@samvanstroud
Copy link
Contributor

No description provided.

@afroch
Copy link
Contributor

afroch commented Mar 6, 2023

Thinking about this, I'd guess the easiest way is to just give the draw_vlines object the x values for that. Because connecting the two samples (calculating on the one and plotting the other) is not so trivial. Because these two samples are normally not plotted in the same plot. We could however, add a little helper function to draw_vlines where we can just give him the disc cut values and he automatically calculates the x_values for the given plot/sample.

Is this something which would work for you @samvanstroud?

@samvanstroud
Copy link
Contributor Author

@afroch do you mean to use draw_vlines to compute the cut values on ttbar, and then to manually pipe this info to the plotting script for Z'?

That is one option. Previously I handled this by allowing the taggers to specify their own WP cut values, and then use a helper script to define these. We could add this e.g. in the High Level API, e.g. something like:

Tagger(..., wp_cuts={70: 1.5})

Then the plotting script can just use the provided WP cut values for each tagger

@samvanstroud
Copy link
Contributor Author

The tools package now includes a handy script to calculate working points. We could use this in the solving of this issue

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

No branches or pull requests

2 participants