You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardexpand all lines: docs/installation.md
+5-31
Original file line number
Diff line number
Diff line change
@@ -16,40 +16,14 @@ This pipeline requires locally stored genomes in fasta format. To build these, d
16
16
nextflow run marchoeppner/gmo-check -profile standard,singularity --build_references --run_name build_refs --outdir /path/to/references
17
17
```
18
18
19
-
If you do not have singularity on your system, you can also specify docker, podman or conda for software provisioning - see the [usage information](usage.md).
19
+
where `/path/to/references` could be something like `/data/pipelines/references`or whatever is most appropriate on your system.
20
20
21
-
The path specified with `--outdir` can then be given to the pipeline during normal execution as `--reference_base`.
21
+
If you do not have singularity on your system, you can also specify docker, podman or conda for software provisioning - see the [usage information](usage.md).
22
22
23
+
The path specified with `--outdir` can then be given to the pipeline during normal execution as `--reference_base`. Please note that the build process will create a pipeline-specific subfolder (`gmo-check`) that must not be given as part of the `--outdir` argument. Gmo-check is part of a collection of pipelines that use a shared reference directory and it will choose the appropriate subfolder by itself.
23
24
24
25
## Site-specific config file
25
26
26
-
This pipeline requires a site-specific configuration file to be able to talk to your local cluster or compute infrastructure. Nextflow supports a wide
27
-
range of such infrastructures, including Slurm, LSF and SGE - but also Kubernetes and AWS. For more information, see [here](https://www.nextflow.io/docs/latest/executor.html).
28
-
29
-
Please see conf/lsh.config for an example of how to configure this pipeline for a Slurm queue.
30
-
31
-
All software is provided through either Conda environments or Docker containers. Consider a Docker-compatible container engine if at all possible (Docker, Singularity, Podman). Conda environments are built on the fly during pipeline execution and only for a given pipeline run, which tends to slow things down quite a bit. Details on how to specify singularity as your container engine are provided in the config file for our lsh system (lsh.config).
32
-
33
-
With this information in place, you will next have to create an new site-specific profile for your local environment in `nextflow.config` using the following format:
34
-
35
-
```
36
-
37
-
profiles {
38
-
39
-
your_profile {
40
-
includeConfig 'conf/base.config'
41
-
includeConfig 'conf/your_cluster.config'
42
-
includeConfig 'conf/resources.config'
43
-
}
44
-
}
45
-
46
-
```
47
-
48
-
This would add a new profile, called `your_profile` which uses (and expects) conda to provide all software.
49
-
50
-
`base.config` Basic settings about resource usage for the individual pipeline stages.
51
-
52
-
`resources.config` Gives information about the files that are to be used during analysis for the individual human genome assemblies.
53
-
54
-
`your_cluster.config` Specifies which sort of resource manager to use and where to find e.g. local resources cluster file system (see below).
27
+
If you run on anything other than a local system, this pipeline requires a site-specific configuration file to be able to talk to your cluster or compute infrastructure. Nextflow supports a wide range of such infrastructures, including Slurm, LSF and SGE - but also Kubernetes and AWS. For more information, see [here](https://www.nextflow.io/docs/latest/executor.html).
55
28
29
+
Site-specific config-files for our pipeline ecosystem are stored centrally on [github](https://github.com/marchoeppner/configs). Please talk to us if you want to add your system
Copy file name to clipboardexpand all lines: docs/software.md
+19-1
Original file line number
Diff line number
Diff line change
@@ -7,4 +7,22 @@ Version 0.24, doi: 10.1093/bioinformatics/bty560, [PubMed](https://pubmed.ncbi.n
7
7
Version 1.19, doi: 10.1093/bioinformatics/btw354, [PubMed](https://pubmed.ncbi.nlm.nih.gov/27312411/)[github](https://github.com/MultiQC/MultiQC)
8
8
9
9
**Samtools**
10
-
Version 1.19, doi: 10.1093/bioinformatics/btp352, [PubMed](https://pubmed.ncbi.nlm.nih.gov/19505943/)[github](https://github.com/samtools/samtools)
10
+
Version 1.19, doi: 10.1093/bioinformatics/btp352, [PubMed](https://pubmed.ncbi.nlm.nih.gov/19505943/)[github](https://github.com/samtools/samtools)
11
+
12
+
**Vsearch**
13
+
Version 2.27.0, doi: 10.7717/peerj.2584, [PubMed](https://pubmed.ncbi.nlm.nih.gov/27781170/)[github](https://github.com/torognes/vsearch)
14
+
15
+
**Ptrimmer**
16
+
Version 1.3.3, doi: 10.1186/s12859-019-2854-x, [PubMed](https://pubmed.ncbi.nlm.nih.gov/31077131/)[github](https://github.com/DMU-lilab/pTrimmer)
17
+
18
+
**Bwa-mem2**
19
+
Version 2.2.1, doi: 10.1109/IPDPS.2019.00041, [IEEE Explore](https://ieeexplore.ieee.org/document/8820962)[github](https://github.com/bwa-mem2/bwa-mem2)
20
+
21
+
**Freebayes**
22
+
Version 1.3.6, [ArXiv](http://arxiv.org/abs/1207.3907)[github](https://github.com/freebayes/freebayes)
23
+
24
+
**Blast**
25
+
Version 2.15, doi: 10.1016/S0022-2836(05)80360-2, [PubMed](https://pubmed.ncbi.nlm.nih.gov/2231712/)[NCBI]https://blast.ncbi.nlm.nih.gov/doc/blast-help/downloadblastdata.html
26
+
27
+
**Bedtools**
28
+
Version 2.31.1, doi: 10.1093/bioinformatics/btq033, [PubMed](https://pubmed.ncbi.nlm.nih.gov/20110278/)[github](https://github.com/arq5x/bedtools2)
0 commit comments