Getting started with gkno
See the instructions
on how to download and install gkno
and the instructions
to determine how to use the help options in gkno
to find the pipeline that is most relevant to your analysis. If no pipelines exist that perform the tasks required, you can either construct your own pipeline using the provided instructions
or contact me at AlistairNWard@gmail.com or on Twitter at @AlistairNWard.
Executing a pipeline
Executing a pipeline is simple; all we need is to run gkno and tell it the pipeline we want to use. When running a pipeline for the first time, it is a good idea to look at the help information and see exactly what the pipeline does (the workflow), what arguments it accepts, and in particular, what parameter sets
There is a set of arguments that can be applied to any pipeline that perform functions that are pipeline independent. This includes functions such as selecting or creating parameter sets, allowing parallel execution of tasks etc. To see a list of these commands, use the
argument. Click below to see all of the available commands, or a more detailed description is provided here
- Print all available pipelines to screen.
- Display all available help categories.
- Define the path to the directory in which the configuration file(s) resides.
- Display debugging information.
- Flag to stop execution of the Makefile after gkno is run.
- Do not log this run of gkno.
- Flag to disable reordering of values supplied to linked arguments.
- Name of the file to which a full visual depiction of the pipeline graph will be output.
- A full and reduced version of the pipeline graph will be output to files beginning with this value and appended with '-full' and '-reduced'.
- Name of the file to which a reduced visual depiction of the pipeline graph will be output. This is the form of the pipeline shown on the webpage for the pipeline.
- Export a parameter set to a configuration file of this name.
- Print help information for gkno arguments.
- Print requested help message.
- Path for input files if not defined. Default: current directory.
- Append this text to all makefiles generated in this execution of gkno.
- If any of the long form arguments are supplied with a list of valuess causing one or more tools to require multiple iterations, if this is set to true, multiple makefiles are generated. If set to false [default], a single makefile will be generated.
- The number of parallel jobs to be used (only valid in conjunction with the --internal-loop option).
- Path for output files if not defined. Default: current directory.
- Generate a stdout and stderr for each task.
- Remove a user-generated parameter set.
- Write out json files for use with the web page.