-
-
Notifications
You must be signed in to change notification settings - Fork 601
enhance desolve output from separable ODEs #17739
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
Comments
comment:1
This would yield (doctest):
|
comment:2
Do we resolve this in Sage, Maxima, or both? |
Upstream: Not yet reported upstream; Will do shortly. |
comment:3
You should report this upstream, but maybe first to the email list, not as a bug. Surely there must be a reason they report the solutions that way ... right? (For instance, maybe this is "more correct" than something with solve that might lose a solution or something. Though it's hard to see how that could happen in your first example!) |
comment:4
Replying to @kcrisman:
It appears not, see http://sourceforge.net/p/maxima/mailman/message/33364512/ |
comment:5
So, the inconsistency is in Sage, which removes 'y==' from the results that have it, perhaps to facilitate further usage of the expression.
We could now either remove the snippet, in order to always get an equation, or always try to solve for |
At the moment,
desolve
behaves like this even with trivial separable ODEs:They could be solved by substituting a variable for
y(t)
and callingsolve
. Only if there is no solution fromsolve
the integrated equation should be given.Upstream: Not yet reported upstream; Will do shortly.
Component: calculus
Issue created by migration from https://trac.sagemath.org/ticket/17739
The text was updated successfully, but these errors were encountered: