-
-
Notifications
You must be signed in to change notification settings - Fork 487
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
doctest fixed integral from Maxima #8728
Comments
comment:1
I wonder if this is another manifestation of this bug:
|
comment:2
#8729 may point to a solution. |
comment:3
Hmm, I forgot about this, and it's true it never got implemented, did it? |
comment:4
It was fixed about two weeks ago in maxima. There was a new release of maxima a few days ago---I'm trying to make an spkg right now. |
comment:5
Sweet. I haven't been keeping up on the Maxima list lately, thanks. |
comment:6
Replying to @jasongrout:
I just checked; this ticket isn't the same bug. |
comment:7
The upgrade to maxima 5.21.1 does not fix this. After #8731:
|
comment:8
Maxima 5.23.2 still has this, and we still haven't reported it.
This is now Maxima bug 3211975. |
comment:9
According to the bug report, this is now fixed. However, some examples may still throw a Lisp error, so we should check out whether that will affect us before saying we're totally fixed when we upgrade. |
Changed upstream from Not yet reported upstream; Will do shortly. to Fixed upstream, but not in a stable release. |
comment:10
Maxima 5.28 is now out. |
comment:11
See #13973 where this should (?) be fixed, just need a doctest here? |
comment:15
In Maxima 5.33.0 (see #13973):
This appears to be the correct answer. Note that the answers to both questions are "negative" for all e with -1 < e < 1, so it would be nice if Maxima didn't ask those questions. |
comment:17
The thing noted in the message upstream when they closed their ticket
does still happen, but I think that is a different issue tracked elsewhere here (the usual keepfloat thing). So... do we have a reasonable test case to add here to confirm this is fixed and close it? |
Changed upstream from Fixed upstream, but not in a stable release. to Fixed upstream, in a later stable release. |
This comment has been minimized.
This comment has been minimized.
comment:19
Here's the doctest:
|
Commit: |
New commits:
|
Author: Ralf Stephan |
comment:22
Your assumptions are contradictory: the first assumption ( A fortiori, the other two assumptions (after negating) are actually redundant. It is annoying that we have to add them; ideally, we would only declare this integral to be "fixed" if Maxima did not need the extra two assumptions... |
Changed branch from u/rws/doctest_fixed_integral_from_maxima to u/rws/8728 |
Changed upstream from Fixed upstream, in a later stable release. to none |
New commits:
|
Reviewer: Travis Scrimshaw |
Changed branch from u/rws/8728 to |
Changed commit from |
comment:27
I noticed just now that this ticket has been closed; it seems comment:15 and comment:22 were ignored... |
comment:28
That would seem so. I think you are asking for a feature (redundancy of additional assumptions) in Maxima that would warrant a separate ticket. I apologize for not answering earlier. |
comment:29
Replying to @rwst:
That too, but more importantly I meant the fact that the assumptions that are currently made in the doctest are mutually inconsistent:
Namely, the first assumption is equivalent to There is already some functionality for detecting inconsistent assumptions (e.g. |
This is fixed now and needs a doctest:
From #sage-devel:
Component: calculus
Author: Ralf Stephan
Branch:
d4b0db5
Reviewer: Travis Scrimshaw
Issue created by migration from https://trac.sagemath.org/ticket/8728
The text was updated successfully, but these errors were encountered: