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
Whereas Parsl can launch a Python function given the function itself, Fireworks uses the name of the function, which it serializes and imports in the environment that it's actually run.
This is an issue for functions defined interactively in an IPython session, since they aren't defined in a .py file that can be imported remotely.
We should perhaps serialize the text of the function ourselves, create a .py file, and ship it to fireworks. We should look into how Parsl and IPyParallel handle this.
The text was updated successfully, but these errors were encountered:
Whereas Parsl can launch a Python function given the function itself, Fireworks uses the name of the function, which it serializes and imports in the environment that it's actually run.
This is an issue for functions defined interactively in an IPython session, since they aren't defined in a .py file that can be imported remotely.
We should perhaps serialize the text of the function ourselves, create a .py file, and ship it to fireworks. We should look into how Parsl and IPyParallel handle this.
The text was updated successfully, but these errors were encountered: