Opened 23 months ago

Last modified 5 months ago

#27092 new defect

sum(binomial(1,n),n,0,oo) should be 2 instead of 3 (error due to maxima)

Reported by: rburing Owned by:
Priority: major Milestone:
Component: interfaces Keywords: maxima, binomial, series
Cc: Merged in:
Authors: Reviewers:
Report Upstream: Fixed upstream, but not in a stable release. Work issues:
Branch: Commit:
Dependencies: Stopgaps:

Description (last modified by dimpase)

As reported on Ask SageMath:

sage: sum(binomial(1,n),n,0,oo)
3
sage: sum(binomial(1,n),n,0,oo,algorithm='sympy')
2

The error can be traced back to Maxima as follows: evaluating

sum(binomial(1,n),n,0,oo)

returns

from sage.calculus.calculus import symbolic_sum
symbolic_sum(binomial(1,n),n,0,oo)

which calls

maxima_calculus.sr_sum(binomial(1,n),n,0,oo)

which returns

from sage.interfaces.maxima_lib import max_to_sr, maxima_eval, max_ratsimp, max_simplify_sum, max_sum, sr_to_max
args = [binomial(1,n), n, 0, oo]
max_to_sr(maxima_eval([[max_ratsimp],[[max_simplify_sum],([max_sum],[sr_to_max(SR(a)) for a in args])]]))

Indeed we can see the bug in Maxima's simplify_sum:

(%i1) load("simplify_sum");
(%i2) simplify_sum(sum(binomial(1,n),n,0,inf));
(%o2)                                  3

I reported this upstream (upstream committed a fix in Oct 2019).

Change History (5)

comment:1 Changed 20 months ago by embray

  • Milestone changed from sage-8.7 to sage-8.8

Ticket retargeted after milestone closed (if you don't believe this ticket is appropriate for the Sage 8.8 release please retarget manually)

comment:2 Changed 18 months ago by gh-sheerluck

maxima-5.43.0: simplify_sum still has bug

comment:3 Changed 18 months ago by kcrisman

  • Report Upstream changed from Reported upstream. No feedback yet. to Fixed upstream, but not in a stable release.

Bug has a couple possible fixes upstream but apparently no commit yet.

comment:4 Changed 18 months ago by embray

  • Milestone sage-8.8 deleted

As the Sage-8.8 release milestone is pending, we should delete the sage-8.8 milestone for tickets that are not actively being worked on or that still require significant work to move forward. If you feel that this ticket should be included in the next Sage release at the soonest please set its milestone to the next release milestone (sage-8.9).

comment:5 Changed 5 months ago by dimpase

  • Description modified (diff)
Note: See TracTickets for help on using tickets.