https://dev.arvados.org/https://dev.arvados.org/favicon.ico?15576888422016-09-02T19:27:57ZArvadosArvados - Bug #9932: [CWL] Document best practiceshttps://dev.arvados.org/issues/9932?journal_id=426682016-09-02T19:27:57ZPeter Amstutzpeter.amstutz@curii.com
<ul><li><strong>Assigned To</strong> set to <i>Peter Amstutz</i></li></ul> Arvados - Bug #9932: [CWL] Document best practiceshttps://dev.arvados.org/issues/9932?journal_id=427522016-09-06T14:52:27ZBryan Coscabcosca@curii.com
<ul></ul><pre>
L7:"CWL workflow best practices library":https://github.com/common-workflow-language/workflows and "dockstore":http://dockstore.org
L11: Avoid s/including/declaring/ @InlineJavascriptRequirement@ (nitpicky but it follows you saying declare in L9)
L43: Similarly, you can get the designated output directory using $(runtime.outdir).
L79: Don't s/specifying/specify/ resource
L109: has to s/complete/wait/ for all samples to complete before @step2@ can start +computing+ on any samples.
L134: Instead, scatter over a subworkflow. In this pattern, a sample can proceed -from- to @step2@ as soon as @step1@ is done, independently of any other samples. The subworkflow can also be put in a separate CWL workflow file.
Example:
</pre>
<p>otherwise LGTM. We can add new things later when we think of them.</p> Arvados - Bug #9932: [CWL] Document best practiceshttps://dev.arvados.org/issues/9932?journal_id=427822016-09-06T21:00:11ZPeter Amstutzpeter.amstutz@curii.com
<ul><li><strong>Status</strong> changed from <i>New</i> to <i>Resolved</i></li></ul><p>Applied in changeset arvados|commit:5aaaed7d7b1287c0133dd66c9492d6df62790288.</p>