-
-
Notifications
You must be signed in to change notification settings - Fork 517
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
"integrate" fails to integrate a convergent integral (sin(x^2)/x^2). #11737
Comments
This comment has been minimized.
This comment has been minimized.
comment:3
This is in Maxima. In the latest:
It used to just return the integral.
I think this integral should converge, right? By the p-test (well, with absolute values) for p=2? And |
Upstream: Not yet reported upstream; Will do shortly. |
Changed upstream from Not yet reported upstream; Will do shortly. to Reported upstream. Little or no feedback. |
comment:4
This is tracked at this Maxima bug artifact. |
comment:5
The absolute value of the function is dominated by |
comment:6
You say potato, I say potahto :) |
comment:7
Karl-Dieter, please can you check the bug is fixed upstream? Laurent (Fousse) says it was caused by commit Paul |
comment:8
As far as I can tell, it's not fixed upstream - I have 5.25.1. The bug report had a resolution but it was something where they apparently typed in the wrong integral. I am ignorant of how to use git and I can't do a text search for that commit line, unfortunately, so I'll take Laurent's word for it. I've put that info on the bug tracker as well. |
comment:9
Laurent tested with both 5.24.0 and the last git maxima version (commit 01679c735de525a39fa1d893f9e1d9f86bd65f91) and he got:
Please can you add this to the maxima bug tracker? Paul |
comment:10
I think that you may have missed the fact that I already did so in comment:4 three months ago. The person from Maxima who first looked at it must have tried something else incorrect, and I updated it yesterday with your information about the commit in question. |
comment:11
This is now fixed upstream.
|
comment:12
Karl-Dieter, do you know in which release of Maxima this will be fixed? Paul |
comment:13
It's in the latest stable release, 5.27.0. Probably it will be easiest to just upgrade. |
Changed upstream from Reported upstream. Little or no feedback. to Fixed upstream, in a later stable release. |
comment:14
Both new Maxima and Wolfram Alpha give the value about 0.2857367, and not 0.28625044 (what you see in the ticket description). Changing the latter to reflect the reality. |
This comment has been minimized.
This comment has been minimized.
Reviewer: Dmitrii Pasechnik |
comment:15
This is fixed (and doctested) at #13364. |
Changed reviewer from Dmitrii Pasechnik to Dmitrii Pasechnik, Karl-Dieter Crisman |
Dependencies: #13364 |
comment:19
Replying to @dimpase:
The value was still off in the last digit given in the test. Fixed in #16697 |
This worked fine until v4.5.3, fails from v4.6.1 onward.
The expected output (with Maxima 5.29.1) is:
Depends on #13364
Upstream: Fixed upstream, in a later stable release.
Component: calculus
Reviewer: Dmitrii Pasechnik, Karl-Dieter Crisman
Issue created by migration from https://trac.sagemath.org/ticket/11737
The text was updated successfully, but these errors were encountered: