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

Randomly throw signal events containing taus #124

Merged
merged 1 commit into from
Feb 3, 2017

Conversation

blinkseb
Copy link
Member

@blinkseb blinkseb commented Feb 3, 2017

The HH signals used for Moriond 17 have bugs in the generation. The BR
of taus decays is incorrect (= BR(tau -> all) instead of BR(tau -> e / mu))

Mitigate the issue by throwing randomly some events containing taus to
retrieve BR(tau -> e / mu)

I also updated the GTs to use the latest JECs (note: https://github.com/cp3-llbb/Datasets/ must also be updated)

The HH signals used for Moriond 17 have bugs in the generation. The BR
of taus decays is incorrect (= BR(tau -> all) instead of BR(tau -> e / mu))

Mitigate the issue by throwing randomly some events containing taus to
retrieve BR(tau -> e / mu)
@OlivierBondu
Copy link
Member

For the record, it's not a 'bug' in the sense the pythia fragment is doing exactly what we agreed it should be doing.... as we did not want to have hadronic taus in the sample since we wanted to maximize the 'useful' stat of the sample... and we are now exactly reverting this decision, which is what we need for a quick fix.

but ok, it's semantics at this stage, thanks !

@OlivierBondu OlivierBondu merged commit 8b0d428 into cp3-llbb:master Feb 3, 2017
@vidalm
Copy link
Member

vidalm commented Feb 3, 2017

No, we wanted the leptonic decays in the right proportion... (If is doable and how, it is another thing)

@OlivierBondu
Copy link
Member

Which is possible, but I don't think a pythia filter is what you need / want... Analysis-level recipe, which is what we discussed earlier, is still possible, but not a quick fix as this one is.

I will take the blame as needed, but guys, I did ask every single one of you about this...

@swertz
Copy link
Contributor

swertz commented Feb 3, 2017

It's not a bug, it's a feature, and if there is blame to be taken it's for all of us, since as you say we gave our 👍 when the samples were submitted!

@vidalm
Copy link
Member

vidalm commented Feb 3, 2017

First, I am not blaming you. And I will never blame you for doing something I am not able to do. I thank you for that.
Second, the only point here is that we were not smart enough (at least I wasn't) to see the outcome of the filter. But I am not saying is your fault.

continue;

// Count the number of tau coming directly from a W or a Z
if ((pdg_id == 15) && (pruned_decays_from_pdg_id(ip, 24, true) || pruned_decays_from_pdg_id(ip, 23, true))) {
Copy link
Contributor

Choose a reason for hiding this comment

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

Shouldn't this be abs(pdg_id)?

Copy link
Member Author

Choose a reason for hiding this comment

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

Indeed

@blinkseb blinkseb mentioned this pull request Feb 6, 2017
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.

4 participants