Add the "auto-detect the current allocation" feature #234
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.
Most of the time, I think that users will only be working with a single cluster scheduler, and thus they can just use the relevant
ClusterManager
directly.However, in some situations, I think that it might be useful to be able to write a single script that is agnostic to the specific cluster scheduler. In those cases, it would be nice to auto-detect which cluster scheduler is active, and then automatically use the correct
ClusterManager
.This PR adds an experimental non-public
addprocs_autodetect_current_scheduler()
function that implements this.Note: The
addprocs_autodetect_current_scheduler()
function should be run from inside an active allocation. So e.g. for Slurm, you would first get an allocation (e.g.sbatch
orsalloc
), and then run this function inside the allocation.