-
Notifications
You must be signed in to change notification settings - Fork 62
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
Use SymPy.solve instead of generic lu for A\b #355
Comments
This seems like a job for
I should have time this week. Thanks for all the feedback. |
jverzani
added a commit
to jverzani/SymPy.jl
that referenced
this issue
Jun 1, 2020
Thanks again. I ended using your approach in #356. |
Thanks a lot for sorting things out! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
This doesn't return on my machine, at least not before I got tired of waiting. Seems to work for smaller
n
though, but the solution is very long and not simplified. The problems get worse if more symbolic variables are included. The generic lu that is called by\
doesn't simplify intermediate expressions, which could be one reason for what seems like exponential complexity blow up.SymPy.solve
seems to work better. I guess one should really uselinsolve
, but I couldn't get this to work?! I guess one has to think about what to return, or if to throw an error, if there is no / multiple solutions. However, my feeling is that anything would be better than what is currently done by the genericlu
.The text was updated successfully, but these errors were encountered: