maestrowf
maestrowf copied to clipboard
LLNL
A tool to easily orchestrate general computational workflows both locally and on supercomputers
So I've been looking at some of the limitations of the YAML specification as it is, and I've come up with a new structure for it. ``` name: step_name description:...
While running some tests on an MPI enabled LULESH, I encountered a case where when cancelling a study resulted in inaccurate status reported by Maestro. I don't expect that this...
@gonsie mentioned this issue previously, but I wanted to make note of it since this came up again when using the Flux-spectrum adapter. This issue addresses the ability to specify...
The way the current script generation looks is as follows: ``` to_be_scheduled, script_path, restart_path = \ self._write_script(ws_path, step) st = os.stat(script_path) os.chmod(script_path, st.st_mode | stat.S_IXUSR) if restart_path: st = os.stat(restart_path)...
The proposed feature is a logging mechanism for what commands are actually issued to the system. In its simplest form, this could be imagined as a single bash script that...
Just an idea, but maybe the lock files could be stored in /tmp? This way it's a few fewer inodes used in our file systems.
Use `git clone --depth=1` or download an archive (rather than cloning with git). Just as a way to decrease the number of files.
Suggested by @jsemler. I like the proposed suggestions. A few additional suggestions for discussion: `maestro validate ` The ability to easily validate a study spec without needing to setup the...
I have noticed that the execution graph is pickled. Is there a plan for a way to resume a study execution from its last point of failure?
Add machinery for controlling execution order/priority of study steps * Adds weights to the graph to enable selecting between depth first and breadth first (current production mode) execution order. *...
