On Thu, Aug 5, 2010 at 10:23 AM, David Kirkby <david.kir...@onetel.net> wrote:
> BTW, do you have any ideas why the second failure at #9099 might occur
>
> sage -t -long devel/sage/sage/symbolic/expression.pyx
> **********************************************************************
> File
> "/home/palmieri/fulvia/sage-4.5.2.rc0/devel/sage-main/sage/symbolic/expression.pyx",
> line 498\
> 3:
> sage: maxima('sinh(1.0)')
> Expected:
> 1.175201193643801
> Got:
> 1.175201193643802
> **********************************************************************
> File
> "/home/palmieri/fulvia/sage-4.5.2.rc0/devel/sage-main/sage/symbolic/expression.pyx",
> line 508\
> 8:
> sage: maxima('asinh(1.0)')
> Expected:
> 0.881373587019543
> Got:
> .8813735870195429
> **********************************************************************
>
>
> Why should the zero be missing in the case observed on Solaris x86?i
> In other words, why do we see .8813735870195429 instead of
> 0.8813735870195429 ? Te exact value of the last digit is unimportant,
> and one clearly can't expect to get all digits spot on, but one would
> hope that a zero should be printed when its needed.
Well, it seems likely that the issue is within maxima (either in
maxima itself or in the Common Lisp implementation). To verify that
the problem has nothing to do with Sage, you can use "sage -maxima"
and try the test case on both machines:
cwi...@red-spider:~/sage$ ./sage -maxima
;;; Loading #P"/home/cwitty/sage/local/lib/ecl/defsystem.fas"
;;; Loading #P"/home/cwitty/sage/local/lib/ecl/cmp.fas"
;;; Loading #P"/home/cwitty/sage/local/lib/ecl/sysfun.lsp"
Maxima 5.20.1 http://maxima.sourceforge.net
using Lisp ECL 10.2.1
Distributed under the GNU Public License. See the file COPYING.
Dedicated to the memory of William Schelter.
The function bug_report() provides bug reporting information.
(%i1) asinh(1.0);
(%o1) 0.881373587019543
(Don't forget the semicolon on the "asinh(1.0);" line; without that,
maxima will wait forever for more input.)
If the results do differ with "sage -maxima", I guess the next step
would be to report the problem to the maxima mailing list or the bug
tracker (bearing in mind that the problem may actually be in the
Common Lisp implementation we use).
Carl
--
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
