On Feb 20, 2010, at 12:40 PM, John H Palmieri wrote:
On Feb 19, 9:11 am, John Cremona <john.crem...@gmail.com> wrote:
On 19 February 2010 06:32, Minh Nguyen <nguyenmi...@gmail.com> wrote:
Hi folks,
This is the final alpha release of Sage 4.3.3. The next release
would
be an rc0. The development version of Sage is now in feature freeze.
On 32-bit Suse I get this fuzz:
File "/local/jec/sage-4.3.3.alpha1/devel/sage/sage/misc/
functional.py",
line 705:
sage: h.n()
Expected:
0.33944794097891573
Got:
0.33944794097891567
I was curious about this, so I tried specifying the number of digits:
sage: h = integral(sin(x)/x^2, (x, 1, pi/2)); h
integrate(sin(x)/x^2, x, 1, 1/2*pi)
sage: h.n()
0.33944794097891573
sage: h.n(digits=14)
0.33944794097891573
sage: h.n(digits=600)
0.33944794097891573
sage: h.n(digits=600) == h.n(digits=14)
True
sage: h.n(prec=50) == h.n(prec=1000)
True
Is there an inherit limit in Sage on the accuracy of numerical
integrals?
I don't know if this above uses ginac, maxima, or gsl, but it seems
limited to double precision (which wouldn't surprise me for any of
those three systems). It's also very new. It should probably be
raising a NotImplemented error, but at least it's not casting the
result to a higher precision ring.
- Robert
--
To post to this group, send an email to sage-devel@googlegroups.com
To unsubscribe from this group, send an email to
sage-devel+unsubscr...@googlegroups.com
For more options, visit this group at http://groups.google.com/group/sage-devel
URL: http://www.sagemath.org
