Skip to content

Commit 49e4c1a

Browse files
authored
doc improvemnts (#3434)
1 parent 64a0c80 commit 49e4c1a

File tree

3 files changed

+8
-9
lines changed

3 files changed

+8
-9
lines changed

CHANGELOG.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -11,7 +11,7 @@ Deployed on September 23rd, 2024
1111
* Initial changes in `qiita_client` to have more accurate variable names: `QIITA_SERVER_CERT` -> `QIITA_ROOTCA_CERT`. Thank you @charles-cowart!
1212
* Added `get_artifact_html_summary` to `qiita_client` to retrieve the summary file of an artifact.
1313
* Re-added github actions to `https://github.com/qiita-spots/qiita_client`.
14-
* `Woltka v0.1.4, paired-end` superseded `Woltka v0.1.4` in `qp-woltka`; [more information](https://qiita.ucsd.edu/static/doc/html/processingdata/woltka_pairedend.html). Thank you to @qiyunzhu for the benchmarks!
14+
* `Woltka v0.1.6, paired-end` superseded `Woltka v0.1.6` in `qp-woltka`; [more information](https://qiita.ucsd.edu/static/doc/html/processingdata/woltka_pairedend.html). Thank you to @qiyunzhu for the benchmarks!
1515
* Other general fixes, like [#3424](https://github.com/qiita-spots/qiita/pull/3424), [#3425](https://github.com/qiita-spots/qiita/pull/3425).
1616

1717

qiita_pet/support_files/doc/source/processingdata/processing-recommendations.rst

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -125,7 +125,7 @@ Note that the command produces up to 5 output artifacts based on the aligner and
125125

126126

127127
.. note::
128-
Woltka 0.1.4 only produces per-genome, per-gene and functional profiles as we are moving
128+
Woltka 0.1.6 only produces per-genome, per-gene and functional profiles as we are moving
129129
to Operational Genomic Units (OGUs), which have higher resolution than taxonomic units
130130
for community ecology, and were shown to deliver stronger biological signals in
131131
downstream analyses. For more information please read: `Phylogeny-Aware Analysis of

qiita_pet/support_files/doc/source/processingdata/woltka_pairedend.rst

Lines changed: 6 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -6,16 +6,16 @@ Benchmarks created by Qiyun Zhu (@qiyunzhu) on Aug 1, 2024.
66
Summary
77
-------
88

9-
I tested alternative read pairing schemes in the analysis of shotgun metagenomic sequencing data. Sequencing reads were aligned against a reference microbial genome database as unpaired or paired, with or without singleton and/or discordant alignments suppressed. A series of synthetic datasets were used in the analysis.
9+
I tested alternative read pairing schemes in the analysis of shotgun metagenomic sequencing data. Sequencing reads were aligned against a reference microbial genome database as unpaired or paired. A series of synthetic datasets were used in the analysis.
1010

11-
The results reveal that treating reads as paired is always advantageous over unpaired. Suppressing singleton alignments further increases the accuracy of results, despite the cost of lower mapping rate. Suppressing discordant alignments has no obvious impact on the result. Regardless of accuracy, the downstream community ecology analyses are not obviously impacted by the choice of parameters.
11+
The results reveal that treating reads as paired is always advantageous over unpaired. Regardless of accuracy, the downstream community ecology analyses are not obviously impacted by the choice of parameters.
1212

13-
Therefore, I recommend the general adoption of paired alignments as a standard procedure. I also endorse suppressing singleton and discordant alignments, but note the favor of further tests on whether they may reduce sensitivity with complex communities.
13+
Therefore, I recommend the general adoption of paired alignments as a standard procedure.
1414

1515
Alignment parameters
1616
--------------------
1717

18-
Sequencing data were aligned using Bowtie2 v2.5.1 in the very sensitive mode against the WoL2 database. They were treated as either unpaired or paired-end:
18+
Sequencing data were aligned using Bowtie2 v2.5.1 in the "very sensitive" mode against the WoL2 database. They were treated as either unpaired or paired-end:
1919

2020
- SE: Reads are treated as unpaired (Bowtie2 input: -U merged.fq)
2121
- PE: Reads are treated as paired (Bowtie2 input: -1 fwd.fq, -2 rev.fq)
@@ -30,11 +30,10 @@ Five synthetic datasets were generated with 25 samples each consisting of random
3030

3131
The results of the five Bowtie2 parameter sets were compared using nine metrics:
3232

33-
Three metrics that only rely on each result.
33+
Two metrics that only rely on each result.
3434

3535
- Mapping rate (%)
3636
- Number of taxa
37-
- Entropy (i.e., Shannon index, but without subsampling)
3837

3938
Six metrics that rely on comparing each result against the ground truth (higher is better):
4039

@@ -59,4 +58,4 @@ The results revealed:
5958
#. PE outperforms SE in all metrics. Most importantly, it reduces false positive rate (higher precision) while retaining mapping rate. Meanwhile, the sensitivity (recall) of identifying true taxa is not obviously compromised (note the y-axis scale).
6059
#. PE.NU the two additional parameters had minimum effect on the result and make the alignment step faster. This may suggest that the additional parameters are safe to use.
6160

62-
Therefore, I would recommend adopting paired alignment in preference to unpaired alignment. I may suggest no mixing as it has improved accuracy, but the potential adverse effect of lower mapping rate may be further explored before making a compelling recommendation. Although not having a visible effect, no discordance may be added for logical coherency.
61+
Therefore, I would recommend adopting paired alignment in preference to unpaired alignment.

0 commit comments

Comments
 (0)