1
1
# Quick Start
2
2
3
- This section will show you a brief overview of what is CWL and where you
3
+ This section will show you a brief overview of what CWL is, and where you
4
4
can learn more about it. No previous knowledge of CWL is required, but you
5
5
must be comfortable following instructions for the command-line.
6
6
@@ -20,20 +20,20 @@ with comments:
20
20
```
21
21
22
22
The example above is just a wrapper for the ` echo ` command-line tool.
23
- Running the workflow above with the default input values, produces the
23
+ Running the workflow above with the default input values will produce the same result as the
24
24
command-line ` echo "Hello World" ` .
25
25
26
26
``` {note}
27
- There is a distinction in CWL between a command-line tool and a workflow. But
28
- for the sake of simplicity we are using the term “workflow” here. You will learn
27
+ In CWL, there is a distinction between a command-line tool and a workflow. But
28
+ for the sake of simplicity, we are using the term “workflow” here. You will learn
29
29
more about this in the [basic concepts](basic-concepts.md) section.
30
30
```
31
31
32
32
## Installing a CWL runner
33
33
34
34
` cwltool ` is an implementation of the CWL specification. It is also the
35
- CWL * Reference Runner* for the specification, and compliant with the
36
- latest version of the specification, {{ cwl_version }}. You can install
35
+ CWL * Reference Runner* for the specification, and it is compliant with the
36
+ latest version of the specification: {{ cwl_version }}. You can install
37
37
` cwltool ` using ` pip ` :
38
38
39
39
``` {code-block} console
@@ -68,8 +68,8 @@ to how you would change the argument of the `echo` base command:
68
68
```
69
69
70
70
Another way of passing values to your workflow input parameters is via an
71
- * Inputs Object* . This is a file containing the input fields with the
72
- corresponding values. This file can be written in JSON or YAML. For example:
71
+ * Inputs Object* . This is a file containing the input fields with their
72
+ corresponding values. The Inputs Objects file can be written in JSON or YAML. For example:
73
73
74
74
``` {literalinclude} /_includes/cwl/hello_world-job.json
75
75
:language: json
@@ -85,9 +85,9 @@ You can use this Inputs Object file now to execute the “Hello World” workflo
85
85
```
86
86
87
87
``` {note}
88
- We used a similar file name for the workflow and for the inputs object files.
88
+ We used a similar file name for the workflow and for the Inputs Object files.
89
89
The *-job.json* suffix is very common in Inputs Object files, but it is not
90
- a requirement. You can choose any name for your workflows and inputs object
90
+ a requirement. You can choose any name for your workflows and Inputs Object
91
91
files.
92
92
```
93
93
0 commit comments