Geometry.save is not an app #37
Answered
by
svandenhaute
tbraeckevelt
asked this question in
Q&A
-
I was wondering why Geometry.save() is not a python_app? I wrote a wrapper around the function so that I could save future Geometries:
But this might not be necessary if Geometry.save() is already a python_app. |
Beta Was this translation helpful? Give feedback.
Answered by
svandenhaute
Aug 7, 2024
Replies: 1 comment
-
geometry = ... #
geometry.save(my_path) # OK
future_of_geometry.save(my_path) # will not work because Parsl Futures do not know what `save` is To avoid writing an app for this, you can use the Dataset([future_of_geometry]).save(path_out) |
Beta Was this translation helpful? Give feedback.
0 replies
Answer selected by
tbraeckevelt
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
save()
is an instance method, so you need to call it on an existing geometry, you cannot call it on a future of a geometry:To avoid writing an app for this, you can use the
Dataset
functionality, which works in both cases: