#12586: [ARM] Maxima has a strange numerical precision issue
---------------------------+------------------------------------------------
Reporter: Snark | Owner: drkirkby
Type: defect | Status: needs_info
Priority: major | Milestone: sage-5.1
Component: porting | Resolution:
Keywords: | Work issues:
Report Upstream: N/A | Reviewers:
Authors: | Merged in:
Dependencies: | Stopgaps:
---------------------------+------------------------------------------------
Comment (by Snark):
On sage.math, this new package makes a single test fail:
{{{
sage -t --long -force_lib "devel/sage/sage/gsl/integration.pyx"
**********************************************************************
File "/home/jpuydt/sage-5.0/devel/sage/sage/gsl/integration.pyx", line
172:
sage: exp(-1/x).nintegral(x, 1, 2) # via maxima
Expected:
(0.504792217873184, 5.604319429344075e-15, 21, 0)
Got:
(0.504792217873184, 5.6043194293440744e-15, 21, 0)
**********************************************************************
}}}
So I guess it's a good package :-)
--
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/12586#comment:2>
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 post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/sage-trac?hl=en.
