|
2 | 2 | Each workflow uses a simple INI file to record which variables it accepts, |
3 | 3 | their types, and default values. For example: |
4 | 4 |
|
5 | | -<pre><code>#!ini |
6 | | -# key=input_file:type=file:display=F:file_meta_type=text/plain |
7 | | -input_file=${workflow_bundle_dir}/Workflow_Bundle_MyHelloWorld/${workflow-version}/data/input.txt |
8 | | -# key=greeting:type=text:display=T:display_name=Greeting |
9 | | -greeting=Testing |
10 | | - |
11 | | -cat=${workflow_bundle_dir}/Workflow_Bundle_MyHelloWorld/${workflow-version}/bin/gnu-coreutils-5.67/cat |
12 | | -echo=${workflow_bundle_dir}/Workflow_Bundle_MyHelloWorld/${workflow-version}/bin/gnu-coreutils-5.67/echo |
13 | | - |
14 | | -# the output directory is a convention used in many workflows to specify a relative output path |
15 | | -output_dir=seqware-results |
16 | | -# the output_prefix is a convention used to specify the root of the absolute output path or an S3 bucket name |
17 | | -# you should pick a path that is available on all cluster nodes and can be written by your user |
18 | | -output_prefix=./ |
19 | | -# manual output determines whether or not SeqWare should enforce the uniqueness of the final directory or not. |
20 | | -# If false, SeqWare places files in a directory specified by output_prefix/output_dir/workflowname_version/RANDOM/<files> |
21 | | -# where RANDOM is an integer. If true, SeqWare places the files at output_prefix/output_dir and may overwrite existing |
22 | | -# files |
23 | | -manual_output=false |
24 | | -</code></pre> |
| 5 | + #!ini |
| 6 | + # key=input_file:type=file:display=F:file_meta_type=text/plain |
| 7 | + input_file=${workflow_bundle_dir}/Workflow_Bundle_MyHelloWorld/${workflow-version}/data/input.txt |
| 8 | + # key=greeting:type=text:display=T:display_name=Greeting |
| 9 | + greeting=Testing |
| 10 | + |
| 11 | + cat=${workflow_bundle_dir}/Workflow_Bundle_MyHelloWorld/${workflow-version}/bin/gnu-coreutils-5.67/cat |
| 12 | + echo=${workflow_bundle_dir}/Workflow_Bundle_MyHelloWorld/${workflow-version}/bin/gnu-coreutils-5.67/echo |
| 13 | + |
| 14 | + # the output directory is a convention used in many workflows to specify a relative output path |
| 15 | + output_dir=seqware-results |
| 16 | + # the output_prefix is a convention used to specify the root of the absolute output path or an S3 bucket name |
| 17 | + # you should pick a path that is available on all cluster nodes and can be written by your user |
| 18 | + output_prefix=./ |
| 19 | + # manual output determines whether or not SeqWare should enforce the uniqueness of the final directory or not. |
| 20 | + # If false, SeqWare places files in a directory specified by output_prefix/output_dir/workflowname_version/RANDOM/<files> |
| 21 | + # where RANDOM is an integer. If true, SeqWare places the files at output_prefix/output_dir and may overwrite existing |
| 22 | + # files |
| 23 | + manual_output=false |
25 | 24 |
|
26 | 25 | You access these variables in the Java workflow using the |
27 | 26 | <tt>getProperty()</tt> method. When installing the workflow the ini file is |
|
0 commit comments