|
7 | 7 | * [Updating the pipeline](#updating-the-pipeline) |
8 | 8 | * [Reproducibility](#reproducibility) |
9 | 9 | * [Main arguments](#main-arguments) |
10 | | - * [`-profile`](#-profile-single-dash) |
11 | | - * [`docker`](#docker) |
12 | | - * [`awsbatch`](#awsbatch) |
13 | | - * [`standard`](#standard) |
14 | | - * [`binac`](#binac) |
15 | | - * [`cfc`](#cfc) |
16 | | - * [`uzh`](#uzh) |
17 | | - * [`none`](#none) |
18 | | - * [`--reads`](#--reads) |
19 | | - * [`--singleEnd`](#--singleend) |
20 | | -* [Reference Genomes](#reference-genomes) |
21 | | - * [`--genome`](#--genome) |
22 | | - * [`--fasta`](#--fasta) |
23 | 10 | * [Job Resources](#job-resources) |
24 | 11 | * [Automatic resubmission](#automatic-resubmission) |
25 | 12 | * [Custom resource requests](#custom-resource-requests) |
26 | 13 | * [AWS batch specific parameters](#aws-batch-specific-parameters) |
27 | | - * [`-awsbatch`](#-awsbatch) |
28 | | - * [`--awsqueue`](#--awsqueue) |
29 | | - * [`--awsregion`](#--awsregion) |
30 | 14 | * [Other command line parameters](#other-command-line-parameters) |
31 | | - * [`--outdir`](#--outdir) |
32 | | - * [`--email`](#--email) |
33 | | - * [`-name`](#-name-single-dash) |
34 | | - * [`-resume`](#-resume-single-dash) |
35 | | - * [`-c`](#-c-single-dash) |
36 | | - * [`--max_memory`](#--max_memory) |
37 | | - * [`--max_time`](#--max_time) |
38 | | - * [`--max_cpus`](#--max_cpus) |
39 | | - * [`--plaintext_emails`](#--plaintext_emails) |
40 | | - * [`--sampleLevel`](#--sampleLevel) |
41 | | - * [`--multiqc_config`](#--multiqc_config) |
| 15 | +* [Adjustable parameters for nf-core/eager](#adjustable-parameters-for-nf-coreeager) |
42 | 16 |
|
43 | 17 | ## General Nextflow info |
44 | 18 | Nextflow handles job submissions on SLURM or other environments, and supervises running the jobs. Thus the Nextflow process must run until the pipeline is finished. We recommend that you put the process running in the background through `screen` / `tmux` or similar tool. Alternatively you can run nextflow within a cluster job submitted your job scheduler. |
@@ -116,7 +90,6 @@ Use this parameter to choose a configuration profile. Profiles can give configur |
116 | 90 | * `test` |
117 | 91 | * A profile with a complete configuration for automated testing |
118 | 92 | * Includes links to test data so needs no other parameters |
119 | | ->>>>>>> TEMPLATE |
120 | 93 | * `none` |
121 | 94 | * No configuration at all. Useful if you want to build your own config from scratch and want to avoid loading in the default `base` config profile (not recommended). |
122 | 95 |
|
@@ -155,9 +128,18 @@ A normal glob pattern, enclosed in quotation marks, can then be used for `--read |
155 | 128 |
|
156 | 129 | ## Reference Genomes |
157 | 130 |
|
158 | | -The pipeline config files come bundled with paths to the illumina iGenomes reference index files. If running with docker or AWS, the configuration is set up to use the [AWS-iGenomes](https://ewels.github.io/AWS-iGenomes/) resource. |
| 131 | +### `--fasta` |
| 132 | +If you prefer, you can specify the full path to your reference genome when you run the pipeline: |
| 133 | + |
| 134 | +```bash |
| 135 | +--fasta '[path to Fasta reference]' |
| 136 | +``` |
| 137 | +> If you don't specify appropriate `--bwa_index`, `--fasta_index` parameters, the pipeline will create these indices for you automatically. Note, that saving these for later has to be turned on using `--saveReference`. |
159 | 138 |
|
160 | 139 | ### `--genome` (using iGenomes) |
| 140 | + |
| 141 | +The pipeline config files come bundled with paths to the illumina iGenomes reference index files. If running with docker or AWS, the configuration is set up to use the [AWS-iGenomes](https://ewels.github.io/AWS-iGenomes/) resource. |
| 142 | + |
161 | 143 | There are 31 different species supported in the iGenomes references. To run the pipeline, you must specify which to use with the `--genome` flag. |
162 | 144 |
|
163 | 145 | You can find the keys to specify the genomes in the [iGenomes config file](../conf/igenomes.config). Common genomes that are supported are: |
@@ -189,14 +171,6 @@ params { |
189 | 171 | } |
190 | 172 | ``` |
191 | 173 |
|
192 | | -### `--fasta` |
193 | | -If you prefer, you can specify the full path to your reference genome when you run the pipeline: |
194 | | - |
195 | | -```bash |
196 | | ---fasta '[path to Fasta reference]' |
197 | | -``` |
198 | | -> If you don't specify appropriate `--bwa_index`, `--fasta_index` parameters, the pipeline will create these indices for you automatically. Note, that saving these for later has to be turned on using `--saveReference`. |
199 | | -
|
200 | 174 | ### `--bwa_index` |
201 | 175 |
|
202 | 176 | Use this to specify a previously created BWA index. This saves time in pipeline execution and is especially advised when running multiple times on the same cluster system for example. You can even add a resource specific profile that sets paths to pre-computed reference genomes, saving even time when specifying these. |
|
0 commit comments