You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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?
The text was updated successfully, but these errors were encountered:
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.
At the moment, we have zmu1X and mu1X quantities (and mu2, muplus, muminus). In most use cases,
mu1
is actually used to representzmu1
. It might be worthwhile to phase out mu1 in favor forzmu1
and complete thezmuX
quantities.In case of
muplus
/muminus
, this seems to be not an issue, as they are by design meant to bezmuplus
/zmuminus
. Any differences are an error inmuplus
/muminus
. Formu1
, there is technically a valid difference, however.My questions: should
mu1
be phased out in favor ofzmu1
? Should the names also be changed fromzmu1
to justmu1
?The text was updated successfully, but these errors were encountered: