#15921: work around Maxima fpprintprec bug and other ARM-specific problems
-------------------------------------+-------------------------------------
Reporter: dimpase | Owner:
Type: defect | Status: needs_review
Priority: major | Milestone: sage-6.3
Component: calculus | Resolution:
Keywords: Maxima, | Merged in:
fpprintprec, ARM | Reviewers:
Authors: | Work issues:
Report Upstream: Reported | Commit:
upstream. Developers acknowledge | 079bb9af4f12892268a19f0d218ac96bd72466f4
bug. | Stopgaps:
Branch: |
u/dimpase/arm_fixes_etc |
Dependencies: |
-------------------------------------+-------------------------------------
Comment (by pbruin):
On both ARM and x86_64, the only noticeable effect of setting
`maxfpprintprec: 21` (see [attachment:maxfpprintprec.patch]) is that
Maxima now prints floating point numbers in (-1, 1) starting with `(-)0.`
instead of just `(-).`. This is of course fairly limited, but still nice.
In a stand-alone Maxima compiled with GCL or SBCL, it actually yields one
extra digit of accuracy (meaning that the last digit is in general wrong,
but it not rounded away and thereby corrupting the previous digit). I
could not find an example where this happens on ECL, so that Sage would
benefit from it.
It seems that we still need a separate fix for the following doctest
failures on ARM (note that the last two are identical, so we could remove
the first one):
{{{
File "src/sage/symbolic/expression.pyx", line 7340, in
sage.symbolic.expression.Expression.gamma
Failed example:
SR(10.0r).gamma()
Expected:
362880.0
Got:
362880.00000000047
File "src/sage/functions/bessel.py", line 1618, in
sage.functions.bessel._Bessel.__call__
Failed example:
_Bessel(20,algorithm='maxima')(5.0)
Expected:
27.703300521289436e-12
Got:
27.70330052128944e-12
File "src/sage/functions/other.py", line 663, in
sage.functions.other.Function_gamma.__init__
Failed example:
gamma1(float(6))
Expected:
120.0
Got:
119.99999999999997
File "src/sage/functions/special.py", line 705, in
sage.functions.special.elliptic_j.EllipticE
Failed example:
elliptic_e(0.5, 0.1)
Expected:
0.498011394498832
Got:
0.498011394498831
File "src/sage/functions/special.py", line 715, in
sage.functions.special.elliptic_j.EllipticE.__init__
Failed example:
elliptic_e(0.5, 0.1)
Expected:
0.498011394498832
Got:
0.498011394498831
}}}
Patch coming soon. (Sticking to patches instead of a Git branch to make
it easier to sort out what do here and what to do on a separate ticket.)
--
Ticket URL: <http://trac.sagemath.org/ticket/15921#comment:20>
Sage <http://www.sagemath.org>
Sage: Creating a Viable Open Source Alternative to Magma, Maple, Mathematica,
and MATLAB
--
You received this message because you are subscribed to the Google Groups
"sage-trac" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/sage-trac.
For more options, visit https://groups.google.com/d/optout.
