#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):
It seems so; the following is based on `bessel.lisp` (case of real and
positive order and argument) and reproduces the numerical inaccuracy
(enter `to_lisp();` in Maxima and then input this):
{{{
#!cl
(let ((order 20)
(arg 5))
(multiple-value-bind (n alpha) (floor (float order))
(let ((jvals (make-array (1+ n) :element-type 'flonum)))
(slatec:dbesj (abs (float arg)) alpha (1+ n) jvals 0)
(aref jvals n))))
}}}
The Lisp function `slatec:dbesj` was apparently automatically translated
from Fortran.
--
Ticket URL: <http://trac.sagemath.org/ticket/15921#comment:24>
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.
