1 $base: "http://arvados.org/cwl#"
3 cwl: "https://w3id.org/cwl/cwl#"
4 cwltool: "http://commonwl.org/cwltool#"
6 - $import: https://w3id.org/cwl/CommonWorkflowLanguage.yml
8 - name: cwltool:LoadListingRequirement
10 extends: cwl:ProcessRequirement
15 doc: "Always 'LoadListingRequirement'"
24 symbols: [no_listing, shallow_listing, deep_listing]
26 - name: RunInSingleContainer
28 extends: cwl:ProcessRequirement
31 Indicates that a subworkflow should run in a single container
32 and not be scheduled as separate steps.
36 doc: "Always 'arv:RunInSingleContainer'"
48 local_output_dir: Use regular file system local to the compute node.
49 There must be sufficient local scratch space to store entire output;
50 specify this with `outdirMin` of `ResourceRequirement`. Files are
51 batch uploaded to Keep when the process completes. Most compatible, but
52 upload step can be time consuming for very large files.
54 keep_output_dir: Use writable Keep mount. Files are streamed to Keep as
55 they are written. Does not consume local scratch space, but does consume
56 RAM for output buffers (up to 192 MiB per file simultaneously open for
57 writing.) Best suited to processes which produce sequential output of
58 large files (non-sequential writes may produced fragmented file
59 manifests). Supports regular files and directories, does not support
60 special files such as symlinks, hard links, named pipes, named sockets,
64 - name: RuntimeConstraints
66 extends: cwl:ProcessRequirement
69 Set Arvados-specific runtime hints.
73 doc: "Always 'arv:RuntimeConstraints'"
80 Size of file data buffer for Keep mount in MiB. Default is 256
81 MiB. Increase this to reduce cache thrashing in situations such as
82 accessing multiple large (64+ MiB) files at the same time, or
83 performing random access on a large file.
87 Preferred backing store for output staging. If not specified, the
88 system may choose which one to use.
90 - name: PartitionRequirement
92 extends: cwl:ProcessRequirement
95 Select preferred compute partitions on which to run jobs.
99 doc: "Always 'arv:PartitionRequirement'"
108 - name: APIRequirement
110 extends: cwl:ProcessRequirement
113 Indicates that process wants to access to the Arvados API. Will be granted
114 limited network access and have ARVADOS_API_HOST and ARVADOS_API_TOKEN set
119 doc: "Always 'arv:APIRequirement'"
124 - name: IntermediateOutput
126 extends: cwl:ProcessRequirement
129 Specify desired handling of intermediate output collections.
133 doc: "Always 'arv:IntermediateOutput'"
140 If the value is greater than zero, consider intermediate output
141 collections to be temporary and should be automatically
142 trashed. Temporary collections will be trashed `outputTTL` seconds
143 after creation. A value of zero means intermediate output should be
144 retained indefinitely (this is the default behavior).
146 Note: arvados-cwl-runner currently does not take workflow dependencies
147 into account when setting the TTL on an intermediate output
148 collection. If the TTL is too short, it is possible for a collection to
149 be trashed before downstream steps that consume it are started. The
150 recommended minimum value for TTL is the expected duration of the