Bug #9932

[CWL] Document best practices

Added by Peter Amstutz almost 4 years ago. Updated over 3 years ago.

Status:
Resolved
Priority:
Normal
Assigned To:
Category:
-
Target version:
Start date:
09/06/2016
Due date:
% Done:

100%

Estimated time:
(Total: 0.00 h)
Story points:
-

Subtasks

Task #9943: Review 9932-cwl-styleResolvedBryan Cosca

Associated revisions

Revision 5aaaed7d
Added by Peter Amstutz over 3 years ago

Merge branch '9932-cwl-style' closes #9932

History

#1 Updated by Peter Amstutz almost 4 years ago

  • Assigned To set to Peter Amstutz

#2 Updated by Bryan Cosca over 3 years ago

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:

otherwise LGTM. We can add new things later when we think of them.

#3 Updated by Peter Amstutz over 3 years ago

  • Status changed from New to Resolved

Applied in changeset arvados|commit:5aaaed7d7b1287c0133dd66c9492d6df62790288.

Also available in: Atom PDF