Updates:
Labels: -EasyToFix
Comment #4 on issue 1621 by asmeurer: Initial conditions in dsolve()
http://code.google.com/p/sympy/issues/detail?id=1621
I think we should just pass it to solve() and if it can't handle it, raise
NotImplementedError. In other words, if solve() can't handle it, it is a
problem with solve(), not dsolve().
Note that it will also be possible that someone passes conditions to
dsolve() which do not actually determine unique values for the constants.
We can tell if this is the case in the linear case, so we should probably
raise an error to that effect in that case. But in the non-linear case, I
don't think we can tell the difference between the system being
inconsistent or non zero-dimensional and solve() not implementing it in
general, so we will just have to raise NotImplementedError with a note that
it might be solve's fault, or it might be a bad set of initial conditions.
By the way, this is only "EasyToFix" after issue 1620 is fixed.
--
You received this message because you are subscribed to the Google Groups
"sympy-issues" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/sympy-issues?hl=en.
