Add support for asynchronous workers #149
Open
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Purpose
This PR enables workers to be added while a calibration is already underway.
To-do
redirect_stderr(stdout)
to worker logger funcContent
expr
field to PBSManager and SlurmManager. Thisexpr
is evaluated just after the worker is initialized. This can be set viaSlurmManager(nprocs; expr)
. This enables workers to be initialized and load code asynchronously, without relying on@everywhere
.Distributed.create_worker(manager::Union{SlurmManager, PBSManager},...)
in order to ensure the expression gets evaluated before any other code.run_worker_iteration
to check for newly added workers for each forward model run. The function now gets initial workers, then makes a vector of work (fwd model calls). While this vector is not empty, we check for new workers, and if workers are available we assign one unit of work to the worker. If no workers are available, wait for workersPrevious workflow:
New workflow: