I would suggest keeping all three 'a-', 'ar-', 'arc-' as aliases for the
same function (we could keep the 'a-' as the default as it is the shortest
to type). This is because I have seen all three versions being used across
Computer Science and Mathematics, and restricting anyone of them would
fricas also uses atanh (and yes, I agree that the a- prefix would be better
than arc- and ar-)
On Wednesday, 23 March 2022 at 14:57:26 UTC+1 Nathan Dunfield wrote:
> Mathematica, Maple, and numpy all use "arctanh"; MATLAB uses "atanh".
> It's "arctanh" in the NIST Digital Library of
On Wed, 23 Mar 2022, 13:57 Nathan Dunfield, wrote:
> Mathematica, Maple, and numpy all use "arctanh"; MATLAB uses "atanh".
atanh, etc., i.e. just "a-"-prefix is well in line with the tradition of
Fortran libraries,
as well as C libm's.
It's "arctanh" in the NIST Digital Library of
Mathematica, Maple, and numpy all use "arctanh"; MATLAB uses "atanh". It's
"arctanh" in the NIST Digital Library of Mathematical Functions as well:
https://dlmf.nist.gov/4.37
It is the case that "ar-" prefix is the current ISO standard, and per the
Wikipedia talk page the "ar-" prefix is more
I'd be in favor of the change (keeping arc- as an alias, of course). It is
not a good experience to explain in the course how the function is defined,
and then see sage print it wrong.
On Wednesday, 23 March 2022 at 11:54:34 UTC+1 kcrisman wrote:
> In terms of the missions statement,
In terms of the missions statement, apparently we aren't the only ones, so
consistency might be more important in any
case: https://reference.wolfram.com/language/ref/ArcTanh.html
Note e.g. sympy uses atanh as the
"ordinary":
Note that Sage also provides aliases with `a-`
(the display is still with `arc-`):
```
sage: asinh, acosh, atanh, acoth, asech, acsch
(arcsinh, arccosh, arctanh, arccoth, arcsech, arccsch)
```
--
You received this message because you are subscribed to the Google Groups
"sage-devel" group.
To
