-
-
Notifications
You must be signed in to change notification settings - Fork 489
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Maxima limit() regression #17709
Comments
comment:1
Upstream here. |
Upstream: Reported upstream. No feedback yet. |
comment:2
Seems fixed in 9.2.beta10 - 0 is returned |
comment:3
(The upstream bug in maxima is still present; it seems we are using something else for computing the limit.) |
comment:4
My guess is that we now, as with integration, go through several "algorithms"/programs to get limits. I guess technically this is still a Sage bug, then, if that is true and one then specifies the |
Changed keywords from none to limit |
comment:6
Replying to @kcrisman:
Not yet, as nobody did it..
|
comment:7
Hmm, that is interesting. Maxima returns a nounform
But I don't have the most recent Maxima. Can you test this?
If you get zero then they fixed it, and then a doctest suffices. Otherwise we may have something really weird going on in our own processing, though I don't see what would have changed - Frédéric is right about that, as far as I can tell. |
comment:8
Can you also test this in
|
comment:9
I get
EDIT:
|
comment:10
That is really weird. I really can't find any branch of the code that should just avoid Maxima completely without adding an
now returns zero in that rc version? |
comment:11
no, this does not return 0. Maybe Matthias was looking at something else ? |
comment:12
I cannot confirm my claim from comment 2 above either. I don't know what I may have tested there. |
comment:13
Ok, thanks - setting back settings then. At least now Maxima has acknowledged bug :-) |
Changed upstream from Reported upstream. No feedback yet. to Reported upstream. Developers acknowledge bug. |
comment:14
Setting new milestone based on a cursory review of ticket status, priority, and last modification date. |
comment:18
in 9.7.b1
|
For what it's worth, apparently this is fixed upstream in 5.47. Assuming this is true and that we have that version, adding some tests to confirm it against regressions would be all we need here, right? |
var('n'); u = (1+sqrt(n))^(-n); limit(u(n=n+1)/u,n=infinity)
: this was reported in http://ask.sagemath.org/question/25647/cannot-calculate-limit/ and worked at least in Sage-4.7Upstream: Reported upstream. Developers acknowledge bug.
CC: @sagetrac-tmonteil
Component: calculus
Keywords: limit
Issue created by migration from https://trac.sagemath.org/ticket/17709
The text was updated successfully, but these errors were encountered: