Description & Motivation
I have this situation:
I will cycling submit batches of VASP jobs. Each job may consume different time. I want to handle each VASP result right after it finished, and submit the next VASP job according to that previous result.
I need to submit each job one-by-one, but not waiting for the previous job until it is done. If the run_submission can be changed to async, then there may be a way to achieve the above needs.
- the submission will wait a long time for the results
- add control on the check interval, because there is no need to wait that long in short job
Pitch
- add
Submission.async_run_submission async method
- add
check_interval argument
Additional context
Known bugs:
In LazyLocalContext, the async func runs well, but fail in slurm/pbs system.
Results will be deleted before retrieved if setting clean=True in slurm/pbs system. But setting clean=False will raise error if the same job is submitted again (e.g. running unittest in local).
Description & Motivation
I have this situation:
I will cycling submit batches of VASP jobs. Each job may consume different time. I want to handle each VASP result right after it finished, and submit the next VASP job according to that previous result.
I need to submit each job one-by-one, but not waiting for the previous job until it is done. If the
run_submissioncan be changed to async, then there may be a way to achieve the above needs.Pitch
Submission.async_run_submissionasync methodcheck_intervalargumentAdditional context
Known bugs:
In LazyLocalContext, the async func runs well, but fail in slurm/pbs system.
Results will be deleted before retrieved if setting
clean=Truein slurm/pbs system. But settingclean=Falsewill raise error if the same job is submitted again (e.g. running unittest in local).