Skip to content

Commit 13f35aa

Browse files
author
Peter Amstutz
committed
Add clarification about scattering over empty arrays.
1 parent 1234c09 commit 13f35aa

File tree

1 file changed

+7
-3
lines changed

1 file changed

+7
-3
lines changed

v1.0/Workflow.yml

Lines changed: 7 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -344,13 +344,17 @@ $graph:
344344
345345
The `scatter` field specifies one or more input parameters which will be
346346
scattered. An input parameter may be listed more than once. The declared
347-
type of each input parameter is implicitly wrapped in an array for each
348-
time it appears in the `scatter` field. As a result, upstream parameters
349-
which are connected to scattered parameters may be arrays.
347+
type of each input parameter is implicitly becomes an array of items of the
348+
input parameter type. If a parameter is listed more than once, it becomes
349+
a nested array. As a result, upstream parameters which are connected to
350+
scattered parameters must be arrays.
350351
351352
All output parameter types are also implicitly wrapped in arrays. Each job
352353
in the scatter results in an entry in the output array.
353354
355+
If any scattered parameter is empty at runtime, all outputs are set to
356+
empty arrays and no work is done for the step.
357+
354358
If `scatter` declares more than one input parameter, `scatterMethod`
355359
describes how to decompose the input into a discrete set of jobs.
356360

0 commit comments

Comments
 (0)