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

Ws are not always included in pdgid #186

Open
smpalome opened this issue Nov 24, 2015 · 2 comments
Open

Ws are not always included in pdgid #186

smpalome opened this issue Nov 24, 2015 · 2 comments

Comments

@smpalome
Copy link

I filled a histogramm with the number of Ws per event and there are many events with 0 or 1 Ws which is odd since we need to have atleast 2 in ttbar events.

ws.pdf

@kreczko
Copy link
Member

kreczko commented Nov 24, 2015

As discussed on slack, the culprit is
https://github.com/BristolTopGroup/NTupleProduction/blob/master/python/BristolNTuple_GenParticles_cfi.py#L7
We need to store more particles. How many? No idea. Probably worth having a test script that looks at all genParticles in MiniAOD and tests which is the highest index that we still get a W.

@EmyrClement
Copy link
Contributor

Also check what genParticles are in the miniAOD

https://twiki.cern.ch/twiki/bin/view/CMSPublic/WorkBookMiniAOD2015#MC_Truth

Also, there's 50-100 per event in prunedGenParticles, so just set it to
50 or 100.

On 24/11/2015 16:38, Luke Kreczko wrote:

As discussed on slack, the culprit is
https://github.com/BristolTopGroup/NTupleProduction/blob/master/python/BristolNTuple_GenParticles_cfi.py#L7
We need to store more particles. How many? No idea. Probably worth
having a test script that looks at all genParticles in MiniAOD and
tests which is the highest index that we still get a W.


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

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

3 participants