Skip to content

Commit 87dfc35

Browse files
authored
Merge pull request #41 from qbic-pipelines/d4straub-ampliseq-readme
Update ampliseq.md
2 parents 0419737 + 23f324d commit 87dfc35

File tree

1 file changed

+8
-11
lines changed

1 file changed

+8
-11
lines changed
Lines changed: 8 additions & 11 deletions
Original file line numberDiff line numberDiff line change
@@ -1,35 +1,32 @@
11
# 16S amplicon sequencing
22

3-
This is how to perform 16S amplicon analyses.
3+
This is how to perform 16S amplicon analyses. A video explanation of the biology, the bioinformatics problem and the analysis pipeline can be found for version 2.1.0 in the [nf-core bytesize talk 25](https://nf-co.re/events/2021/bytesize-25-nf-core-ampliseq).
44

55
## Ampliseq pipeline
66

77
To perform 16S amplicon sequencing analyses we employ the [nf-core/ampliseq](https://github.com/nf-core/ampliseq) pipeline.
88

99
### Quick start
1010

11-
* Latest stable release `-r 2.1.0`
11+
* Latest stable release `-r 2.1.1`
1212

1313
A typical command would look like this
1414

1515
```bash
16-
nextflow run nf-core/ampliseq -profile cfc -r 2.1.0 \
16+
nextflow run nf-core/ampliseq -profile cfc -r 2.1.1 \
1717
--input “data” \
1818
--FW_primer "GTGYCAGCMGCCGCGGTAA" \
1919
--RV_primer "GGACTACNVGGGTWTCTAAT" \
2020
--metadata "metadata.tsv" \
21-
--trunc_qmin 35 \
22-
--classifier_removeHash
21+
--trunc_qmin 35
2322
```
2423

25-
See [here](https://nf-co.re/ampliseq/1.2.0/parameters#manifest) the info on how to create the `metadata.tsv` file.
24+
Sequencing data can be analysed with the pipeline using a folder containing `.fastq.gz` files with [direct fastq input](https://nf-co.re/ampliseq/2.1.1/usage#direct-fastq-input) or [samplesheet input](https://nf-co.re/ampliseq/2.1.1/usage#samplesheet-input), also see [here](https://nf-co.re/ampliseq/2.1.1/parameters#input).
2625

27-
If data are distributed on multiple sequencing runs, please use `--multipleSequencingRuns` and note the different requirements for metadata file and folder structure in the [pipeline documentation](https://nf-co.re/ampliseq/1.2.0/parameters#multiplesequencingruns)
28-
29-
### Known bugs
26+
See [here](https://nf-co.re/ampliseq/2.1.1/parameters#metadata) the info on how to create the `metadata.tsv` file.
3027

31-
* All versions include a known bug that is why the `--classifier_removeHash` param should be used.
28+
If data are distributed on multiple sequencing runs, please use `--multipleSequencingRuns` and note the different requirements for metadata file and folder structure in the [pipeline documentation](https://nf-co.re/ampliseq/1.2.0/parameters#multiplesequencingruns)
3229

3330
## Reporting
3431

35-
There are no details about reporting yet.
32+
There are no details about reporting yet. Please refer to the [output documentation](https://nf-co.re/ampliseq/2.1.1/output).

0 commit comments

Comments
 (0)