-
Notifications
You must be signed in to change notification settings - Fork 97
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
Is it possible conserve the workspace between two different calls of the function mlab.run_code() for instance? #23
Comments
Sorry for the delay in reply. The answer is yes. For example, once you have started an instance of the bridge, the following should work:
|
Thank you! I found it out! But I cannot use it anyway because when I need
|
Hmm - interesting. Would you mind posting a minimal example of all the code Thanks ! On Sat, Jun 29, 2013 at 6:12 PM, crygiova notifications@github.com wrote:
|
Hi I made up an example that give me exactly the same error of my script. If you can let me know some informations when you try it, it will be very 2013/7/1 Ariel Rokem notifications@github.com
|
Hi, I need to generate dynamically a matlab script from python and I would like to use the bridge to send execute my dynamic scripts in Mlab, but I would like to conserve the workspace between two Mlab calls. Is this possible?
The text was updated successfully, but these errors were encountered: