#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:66 jpflori]:
> we won't get the last error because of precision stuff, so this can get
removed? My point is that those last lines were explicitely made to catch
that specific error that is not reported as such anymore, so I think it's
useless, or if it can then it won't be becase of precision provlems
anymore so the stuff about precision should be removed
No, you already noted yourself that a failure to convert to float can
trigger this:
{{{
sage: var('n')
sage: x.nintegrate(x,0,n)
...
--> 712 raise ValueError, "Maxima (via quadpack) cannot compute
the integral to that precision"
...
ValueError: Maxima (via quadpack) cannot compute the integral to that
precision
}}}
that's why I said before that this check is necessary.
--
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/10682#comment:67>
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.
