#10682: sum fails with lower bound != 0 or 1 (upgrade maxima to 5.26)
---------------------------------------------------------+------------------
Reporter: fmaltey | Owner:
burcin
Type: defect | Status:
needs_info
Priority: critical | Milestone:
sage-5.0
Component: symbolics | Keywords:
maxima 5.26.0 binomial sum
Work_issues: domain issue, error handling in nintegral | Upstream: N/A
Reviewer: Jean-Pierre Flori, | Author:
Dima Pasechnik
Merged: | Dependencies:
---------------------------------------------------------+------------------
Comment(by nbruin):
Replying to [comment:61 nbruin]:
{{{
#This is just a work around until there is a response to
#http://www.math.utexas.edu/pipermail/maxima/2008/012975.html
if 'quad_qags' in str(v):
raise ValueError, "Maxima (via quadpack) cannot compute the
integral to that precision"
}}}
My apologies! I've looked at the
[http://maxima.git.sourceforge.net/git/gitweb.cgi?p=maxima/maxima;a=blob;f=src/numerical/slatec/quadpack.lisp;h=c07efea3ce3b57e7797c692aa25dc7dee5feb8b5;hb=HEAD#l48
quadpack.lisp source] and as you might notice, there's a `handler-case ...
error` construct there, which is a lisp version of `try ... except`. The
error clause constructs a return value which would be an unevaluated
`quad_qags` call in maxima. So the raise above could in principle still be
triggered (e.g., give an integrand that triggers an error when evaluated
in a way that's not caught otherwise). We need to leave this in. One could
leave out the try...except around the maxima call if the error messages
produced by maxima are sufficiently informative.
The patch that triggered Mike Hansen's request and Dodier's answer is
probably
[http://maxima.git.sourceforge.net/git/gitweb.cgi?p=maxima/maxima;a=commitdiff;h=9f156949a789dab37bf548acc20a08f4fd9c6086
this one]. That code is still there as far as I can see. I think we're
best off leaving both error checks in there. The change in behaviour
between 5.24 to 5.26 is likely caused somewhere else. The 5.26 behaviour
is still as documented (provided we consider 1e-14 as 'invalid input').
Whether we want to raise an error rather than return an error code is an
independent question.
--
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/10682#comment:62>
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.
