-
Notifications
You must be signed in to change notification settings - Fork 49
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
Python JobspecV1: Can I use flux batch rather than flux run? #5220
Comments
Are you asking if there is a Let me know if that is not what you need. |
Thanks a lot - |
As far as resource allocation goes, they are the same. The terminology is different for They are called task slots because you're requesting to allocate slots of a given resource size (e.g. cores and gpus) for eventual placement of tasks. |
Ok, thanks again for the explanation. |
@grondo Maybe I do something wrong, but when I submit more than one |
My mistake - I forgot to close the |
For my density functional theory calculation, I typically have a python process running next to an MPI parallel Fortran code. The python process looks at the output file and interrupts the execution when the Fortran code is not converging. While ideally it would be great to handle all the convergence identification inside Fortran directly, the python wrapper offers rapid prototyping and material system specific tuning. When I use flux on the command line I would do something like this:
And then in the
batch.sh
script I would have:I can translate the
flux run
call to aJobspecV1
call in python, but I would prefer to move theflux batch
call to the python level. In particular I like theconcurrent.futures
representation of theJobspecV1
class, which simplifies the integration in other python projects.The text was updated successfully, but these errors were encountered: