This is a crosspost from RSE – Daniel S. Katz's blog, . See the original post here.
I’ve previously written about the concept of workflows, sets of independent tasks connected by data dependencies, being expressed either as data, for example, a Pegasus DAG or CWL document, or as code, for example, a Python program written in Parsl. A workflow expressed as code clearly has advantages: it may be easier to understand and to change, … Continue reading Using workflows expressed as code and workflows expressed as data together