Conversation
… a PSI/J spec of a libEnsemble run, and run that spec on a system
…ubmit to crawl for calling script if matching script not found in current directory
…for calling script
Member
Author
|
Getting started:
|
Member
Author
|
Probably ready for the first round of feedback. Still WIP of course |
shuds13
reviewed
Jun 15, 2022
Member
shuds13
left a comment
There was a problem hiding this comment.
Following the discussion/demo, I am happy with how this is going so far. It currently is working for
local comms on the tested platforms. Looks like we need a psi/j update for mpi4py comms.
We can decide best location for utility scripts.
Member
Author
|
This iteration may be sufficient for a portable multiprocessing solution. As has been stated, extensions to PSI/J (which I'm looking into) will be necessary to support MPI comms. Thoughts? |
Member
Author
|
shuds13
approved these changes
Jul 14, 2022
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Addresses #807
Introduces a new pair of utilities for preparing and launching libEnsemble workflows onto almost any machine and almost any scheduler, using a PSI/J backend. Should help alleviate some responsibility of maintaining batch submission scripts and determining how to submit jobs on each system.
liberegisterCreates an initial, platform-independent PSI/J representation of a libEnsemble run. Run this utility on a calling script in a familiar manner:
liberegister run_libe_forces.py --comms local --nworkers 4This will produce a
run_libe_forces.jsonserialization from PSI/J, conforming to their specification:This json file is easy to make but also easy to share for use by anyone else using libEnsemble.
libesubmitFurther parameterizes a PSI/J serialization then submits the resulting Job to the specified scheduler. (for example):
libesubmit run_libe_forces.json -q debug -A project -s slurmThis will also produce a Job-specific serialization, like
8ba9de56.run_libe_forces.json:If
libesubmitis run on a.jsonserialization fromliberegisterand can't find the specified calling script, it'll help find matching candidate scripts: