... | ... | @@ -129,6 +129,11 @@ The above discussion assumes that the entire workflow of the user is being manag |
|
|
|
|
|
---
|
|
|
|
|
|
## johnt comments 05-Jan-2018
|
|
|
I think this is a good starting point for designing the workflow manager.
|
|
|
* The thing we need next is probably a representative NEAMS workflow(s) outlined with the approach described here, to go with the surface water workflow. It would also be useful to further refine the SLAC workflow discussed elsewhere.
|
|
|
* Also that -- and this might already be implied -- I'll reinforce my thinking that each task is defined by its inputs and outputs, and that the workflow tracks the data consumed by each task and the data produced by each task. (Initially these data are probably files somewhere in the desktop-cumulus-HPC environment, but we should also be able to support things like PDM/database content in the future.)
|
|
|
|
|
|
## johnt comments 07-Nov-2016
|
|
|
|
|
|
This is a good enumeration of CMB modules for performing workflows. And the extension to external workflow execution is great.
|
... | ... | |