-
Notifications
You must be signed in to change notification settings - Fork 24
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
Querying quark content from Particle is difficult, is there an easier way? #264
Comments
Hans, isn't |
BTW, I get many more particles via your query:
That's strange what you are getting. BTW, that quarks info is one of the extra info we provide, not given via the annual .mcd files from the PDG. Let us know if you spot any place where the info is missing. |
Ignore my last comment. I read too quicky. You meant "also get". |
I should not that the README has example for queries according to quark content. Maybe that's not visible enough? |
Happy for this to be closed, @HDembinski? Seems to me as a solved issue. |
Thank you for the proposed solution. I didn't really study the Readme, so that is on me. I think it is odd though that I cannot query everything from particle, that I have to go to .pdgid. Wouldn't it make more sense if Particle derives from PDGID? |
That's a discussion in the other focused issue, whereasthe question here is dealt with within the present scope of the package, hence I'm closing. Let's continue to discuss the design of the class in #263. |
Today I wanted to get all particles which have at least one strange quark. I found
Particle.quarks
and so I naively did:However, this finds also
It makes sense to me that
Particle.quarks
returns this, but it makes selecting particles by quark content surprisingly difficult. I would have run into the same issue if I asked for particles with a top quark.I can work around this, no problem, but I wonder if there is an easier way to select particles by quark content, this seems like a common query.
Particle
to query strangeness, charmness, bottomness, etc?The text was updated successfully, but these errors were encountered: