Updates:
Labels: Solvers
Comment #15 on issue 1621 by asmeu...@gmail.com: Initial conditions in
dsolve()
http://code.google.com/p/sympy/issues/detail?id=1621
I dislike it too. {f(1):2, diff(f(x), x).subs(x, 2): 3} is much more
readable, even more so if we get a D operator that lets
Comment #14 on issue 1621 by krastano...@gmail.com: Initial conditions in
dsolve()
http://code.google.com/p/sympy/issues/detail?id=1621
This and more is already implemented in the pull request mentioned above.
The issues with it are *not* related to math, but to integration in the
current
Comment #12 on issue 1621 by krastano...@gmail.com: Initial conditions in
dsolve()
http://code.google.com/p/sympy/issues/detail?id=1621
some of this is done here[1], but it depends on actually creating
a IntegrationConstant object (done) and fixing all the tests (not done).
[1]
Comment #11 on issue 1621 by asmeu...@gmail.com: Initial conditions in
dsolve()
http://code.google.com/p/sympy/issues/detail?id=1621
The new pdsolve needs this too.
--
You received this message because this project is configured to send all
issue notifications to this address.
You may
Comment #6 on issue 1621 by renato.c...@gmail.com: Initial conditions in
dsolve()
http://code.google.com/p/sympy/issues/detail?id=1621
Another question: what should the interface be? The only way to keep full
compatibility is accepting initial conditions in kwargs, but it feels more
Comment #7 on issue 1621 by asmeurer: Initial conditions in dsolve()
http://code.google.com/p/sympy/issues/detail?id=1621
I think the syntax should be dsolve(ode, f(x), ics={f(0):1, f'(0):2}).
As far as solving, I think we should just try to solve for the constants
with what's given. If it
Comment #8 on issue 1621 by asmeurer: Initial conditions in dsolve()
http://code.google.com/p/sympy/issues/detail?id=1621
By the way, you can't have dsolve(**ics) anyway because named keyword args
have to be valid Python identifiers, not f(0).
--
You received this message because you are
Comment #9 on issue 1621 by renato.c...@gmail.com: Initial conditions in
dsolve()
http://code.google.com/p/sympy/issues/detail?id=1621
By the way, the nicer syntax from issue 1620 would make these much easier
to enter for derivatives (right now you would have to call .subs, which
is a
Comment #2 on issue 1621 by sapta.ii...@gmail.com: Initial conditions in
dsolve()
http://code.google.com/p/sympy/issues/detail?id=1621
Not that simple. Occasionally you will get a solution like this: exp(C0 +
x). Putting this simply in the solver will cause it to choke because it
gives
Comment #3 on issue 1621 by Vinzent.Steinberg: Initial conditions in
dsolve()
http://code.google.com/p/sympy/issues/detail?id=1621
Please note that our solver supports nonlinear equations too.
--
You received this message because you are subscribed to the Google Groups
sympy-issues group.
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
Updates:
Blockedon: 1620
Comment #1 on issue 1621 by asmeurer: Initial conditions in dsolve()
http://code.google.com/p/sympy/issues/detail?id=1621
(No comment was entered for this change.)
--
You received this message because you are listed in the owner
or CC fields of this issue, or
Status: Accepted
Owner: asmeurer
Labels: Type-Enhancement Priority-Medium EasyToFix
New issue 1621 by asmeurer: Initial conditions in dsolve()
http://code.google.com/p/sympy/issues/detail?id=1621
I finished up the ODE module, and it is now in the master branch (see issue
1611), but I never
13 matches
Mail list logo
