-
-
Notifications
You must be signed in to change notification settings - Fork 453
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
cosh integral incorrect because of abs_integrate #14591
Comments
comment:3
Fixed by #13973. |
comment:7
The answer cosh(x) is completely wrong, even in a neighbourhood of x = 0:
According to the ask.sagemath.org link in the ticket description, the correct answer can be expressed in terms of an elliptic integral function, which I trust much more. |
comment:8
As Thierry pointed out on the ask.sagemath question. So, does #13973 fix this or not? |
comment:9
Replying to @kcrisman:
Yes, I just wanted to give a clear reason here why the answer couldn't possibly be right.
No, it doesn't. I have been doing some debugging of the Maxima command
which returns |
comment:10
Reported upstream: https://sourceforge.net/p/maxima/bugs/2737/ |
Upstream: Reported upstream. No feedback yet. |
comment:12
See also #12731. |
Stopgaps: #12731 |
Changed keywords from none to abs_integrate |
comment:15
Works (no wrong answer) in sage 8.9.b7 with py3:
|
comment:16
Also in 8.8:
This is most likely due to #12731. I'm not sure we should view this bug as being fixed; ideally, the answer should be given as an elliptic integral (see the ask.sagemath question). |
See this ask.sagemath question.
Not that I'm an expert here, but at any rate, viewed as real functions this makes no sense, though perhaps on some branch it does. This happens because
I'm not sure we want to unload
abs_integrate
but we need to figure something out here.Upstream: Reported upstream. No feedback yet.
CC: @sagetrac-tmonteil @gagern
Component: calculus
Keywords: abs_integrate
Stopgaps: #12731
Issue created by migration from https://trac.sagemath.org/ticket/14591
The text was updated successfully, but these errors were encountered: