Re: [sympy] Simple way of numerically evaluating Vectors

2018-10-04 Thread scurrier
The workaround worked for me. Thank you. Btw, I love SymPy. You guys rock, this software is really awesome. -- You received this message because you are subscribed to the Google Groups "sympy" group. To unsubscribe from this group and stop receiving emails from it, send an email to

[sympy] Simple way of numerically evaluating Vectors

2018-09-28 Thread scurrier
I have a Vector whose components are long expressions. I'd like to evaluate them so I can see the numerical value of the components. Is there an easy way to do so? Seems like it should be simpler than the easiest way that I can come up with, which involves taking dot products. I was hoping for

Re: [sympy] SymPy solve() results in unusual memory usage on system of two big equations

2017-06-21 Thread scurrier
Here's the traceback. Traceback (most recent call last): File "solve_closed_form_static_level.py", line 17, in print('Writing to disk complete.') File "C:\Program Files\conda\64bit\lib\site-packages\sympy\solvers\solvers.py", li ne 1071, in solve solution = _solve_system(f,

Re: [sympy] SymPy solve() results in unusual memory usage on system of two big equations

2017-06-05 Thread scurrier
The system of equations is modeling a physical system. I'd think it's tractable, but I guess I'm not sure. I have seen closed form solutions for problems that are similar, but not identical, which were solved with Mathematica. Would it help to incorporate an assumption that all symbols are

Re: [sympy] SymPy solve() results in unusual memory usage on system of two big equations

2017-06-05 Thread scurrier
Hello Mr. Meurer, Thanks for your help and for your efforts towards the project in general. The solve did not finish. I eventually killed it. I will run it again and ctrl+C it to get the traceback at an appropriate time after starting it. There were only two equations and two unknowns

[sympy] SymPy solve() results in unusual memory usage on system of two big equations

2017-05-30 Thread scurrier
While running solve() on a system of two big equations over the course of three days, I came back to find what I'd consider bizarre memory usage. Solve was not complete (not unexpected) and the python process had a commit charge of 100GB with only 6GB in the working set (unexpected). The