You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The Matlab computational engine is inherently serial. In the case here we have Python calling a fitting function in Matlab which requires evaluating a Python model function. The Matlab function yields execution to Python but waits until Python finishes; in the mean time, if the Python function then tries to call Matlab, this causes the program to wait until the Matlab fitting function finishes, causing a deadlock.
We should either try to:
Detect if Matlab is being called from a Python function and give an error
Try to implement some kind of two way communications / server client interface in call.m.
Option 1 is likelier to be much easier...
The text was updated successfully, but these errors were encountered:
The Matlab computational engine is inherently serial. In the case here we have Python calling a fitting function in Matlab which requires evaluating a Python model function. The Matlab function yields execution to Python but waits until Python finishes; in the mean time, if the Python function then tries to call Matlab, this causes the program to wait until the Matlab fitting function finishes, causing a deadlock.
We should either try to:
call.m
.Option 1 is likelier to be much easier...
The text was updated successfully, but these errors were encountered: