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
A little bit more research at wiki Shows that emu has indeed different meanings.
Also, lack of unique unit names leads to a great confusion:
thus "15 emu" may mean either 15 abvolts, or 15 emu units of electric dipole moment,
or 15 emu units of magnetic susceptibility, sometimes (but not always) per gram, or per mole.
I've also looked into this a bit in the weekend, and it's very confusing. EMU to me looks more like a unit system than a unit itself. So what about removing/deprecating 'emu' from the alternatives list of u.Bi, so anyone wanting to use either EMU current or charge won't fall in the trap of using the other by accident.
@pllim It was not a general confusion, the code example was oversimplified. I had an error at a place where I didn't expect it. I could read in all magnetisation data files without a problem. Later in the calculations, it crashed. I would prefer not having ambiguous units. After all having units is to avoid errors not create them.
@embray@mhvk - Do you have any pro or con for deprecating u.emu, or at least give a warning when someone trying to use it? If there is no objections, I can open a PR and maybe we can still include it in 1.2 so the final removal can be done in 2.0?
I guess the only issue that might arise is when an external table uses the unit. I certainly have not encountered such tables myself, and would guess they are rare inside astronomy. Furthermore, I guess in that case the unit would be unclear anyway, so am happy to deprecate.
@p3trus , u.emu will no longer be accessible by default due to the confusion (in dev and in v2.0 release). Please use u.Bi or its other aliases. u.deprecated.emu is available but not recommended.
Activity
pllim commentedon May 16, 2016
I am not familiar with this unit, but looks like @embray added it via 68f574c . And it might be related to https://en.wikipedia.org/wiki/Abampere
p3trus commentedon May 17, 2016
A little bit more research at wiki Shows that emu has indeed different meanings.
pllim commentedon May 17, 2016
@p3trus , so this looks like just general confusion? You can always define your own units.
http://astropy.readthedocs.io/en/stable/units/combining_and_defining.html
http://astropy.readthedocs.io/en/stable/api/astropy.units.def_unit.html#astropy.units.def_unit
bsipocz commentedon May 17, 2016
I've also looked into this a bit in the weekend, and it's very confusing.
EMUto me looks more like a unit system than a unit itself. So what about removing/deprecating'emu'from the alternatives list ofu.Bi, so anyone wanting to use either EMU current or charge won't fall in the trap of using the other by accident.pllim commentedon May 17, 2016
@embray , since you added it, do you have a preference in deprecating
emu?p3trus commentedon May 17, 2016
@pllim It was not a general confusion, the code example was oversimplified. I had an error at a place where I didn't expect it. I could read in all magnetisation data files without a problem. Later in the calculations, it crashed. I would prefer not having ambiguous units. After all having units is to avoid errors not create them.
mhvk commentedon May 19, 2016
In case anyone is keen to do work to support the various cgs EM systems, see #4359...
bsipocz commentedon May 25, 2016
@embray @mhvk - Do you have any pro or con for deprecating
u.emu, or at least give a warning when someone trying to use it? If there is no objections, I can open a PR and maybe we can still include it in 1.2 so the final removal can be done in 2.0?cc @astrofrog @eteq
mhvk commentedon May 25, 2016
I guess the only issue that might arise is when an external table uses the unit. I certainly have not encountered such tables myself, and would guess they are rare inside astronomy. Furthermore, I guess in that case the unit would be unclear anyway, so am happy to deprecate.
pllim commentedon Mar 28, 2017
@p3trus ,
u.emuwill no longer be accessible by default due to the confusion (in dev and in v2.0 release). Please useu.Bior its other aliases.u.deprecated.emuis available but not recommended.