Limitation of PyRun when used with multithreaded KSolve

[dilawar]

One major reason behind replacing muparser with ExprTK was that muParser was not playing well with multithreaded Ksolve (probably because of how we integrated it). ExprTk worked well with multithreaded Ksolve but not with unpublished Vinu's model.

In Vinu's model, PyRun updates moose objects. Probably because of this, or probably due to python's finicky nature with multithreading, exprtk gives correct results up to the first few iterations, and then all values go to 0.

With new python bindings, the situation improved a bit but I run into GSL integration error. With BOOST solvers, I didn't run into integration error but values became 0 after some iterations.

I'll have another look at it, in detail once bindings are in beta. The PyRun interface is still the same as hand-crafted by Subha.

Until this issue is resolved, warn users if they try to update moose object's from the PyRun process when multithreaded Ksolve is used.