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

Use Z-leptons instead of mu1/muplus/... #37

Open
ghost opened this issue Oct 19, 2015 · 4 comments
Open

Use Z-leptons instead of mu1/muplus/... #37

ghost opened this issue Oct 19, 2015 · 4 comments

Comments

@ghost
Copy link

ghost commented Oct 19, 2015

At the moment, we have zmu1X and mu1X quantities (and mu2, muplus, muminus). In most use cases, mu1 is actually used to represent zmu1. It might be worthwhile to phase out mu1 in favor for zmu1 and complete the zmuX quantities.

In case of muplus/muminus, this seems to be not an issue, as they are by design meant to be zmuplus/zmuminus. Any differences are an error in muplus/muminus. For mu1, there is technically a valid difference, however.

My questions: should mu1 be phased out in favor of zmu1? Should the names also be changed from zmu1 to just mu1?

@dhaitz
Copy link
Contributor

dhaitz commented Oct 20, 2015

I think for mu1/2/plus/minus one always wants the muons from Z decay, so yes (to both questions)

@ghost
Copy link
Author

ghost commented Oct 21, 2015

Just another question that came to mind if we are now (potentially) doing Z->ee also. Instead of having zmu1/... and zel1/..., should we use zl1/... and attach also expose the particle ID? The current mu1/... could be made an alias in Merlin only.

@dhaitz
Copy link
Contributor

dhaitz commented Oct 21, 2015

sounds good

@ghost
Copy link
Author

ghost commented Oct 22, 2015

Added zl(1|2|plus|minus)(pt|eta|phi|pdgid) to excalibur itself in e994163.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant