Skip to content

Commit cb59092

Browse files
committed
Update outputs in docs
1 parent 6ce7096 commit cb59092

File tree

1 file changed

+4
-4
lines changed

1 file changed

+4
-4
lines changed

docs/output.md

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -120,7 +120,7 @@ If multiple libraries/runs have been provided for the same sample in the input s
120120

121121
</details>
122122

123-
[UMI-tools](https://github.com/CGATOxford/UMI-tools) deduplicates reads based on unique molecular identifiers (UMIs) to address PCR-bias. Firstly, the UMI-tools `extract` command removes the UMI barcode information from the read sequence and adds it to the read name. Secondly, reads are deduplicated based on UMI identifier after mapping as highlighted in the [UMI-tools dedup](#umi-tools-dedup) section.
123+
[UMI-tools](https://github.com/CGATOxford/UMI-tools) and [UMICollapse](https://github.com/Daniel-Liu-c0deb0t/UMICollapse) deduplicate reads based on unique molecular identifiers (UMIs) to address PCR-bias. Firstly, the UMI-tools `extract` command removes the UMI barcode information from the read sequence and adds it to the read name. Secondly, reads are deduplicated based on UMI identifier after mapping as highlighted in the [UMI dedup](#umi-dedup) section.
124124

125125
To facilitate processing of input data which has the UMI barcode already embedded in the read name from the start, `--skip_umi_extract` can be specified in conjunction with `--with_umi`.
126126

@@ -305,7 +305,7 @@ The original BAM files generated by the selected alignment algorithm are further
305305

306306
![MultiQC - SAMtools mapped reads per contig plot](images/mqc_samtools_idxstats.png)
307307

308-
### UMI-tools dedup
308+
### UMI dedup
309309

310310
<details markdown="1">
311311
<summary>Output files</summary>
@@ -314,7 +314,7 @@ The original BAM files generated by the selected alignment algorithm are further
314314
- `<SAMPLE>.umi_dedup.sorted.bam`: If `--save_umi_intermeds` is specified the UMI deduplicated, coordinate sorted BAM file containing read alignments will be placed in this directory.
315315
- `<SAMPLE>.umi_dedup.sorted.bam.bai`: If `--save_umi_intermeds` is specified the BAI index file for the UMI deduplicated, coordinate sorted BAM file will be placed in this directory.
316316
- `<SAMPLE>.umi_dedup.sorted.bam.csi`: If `--save_umi_intermeds --bam_csi_index` is specified the CSI index file for the UMI deduplicated, coordinate sorted BAM file will be placed in this directory.
317-
- `<ALIGNER>/umitools/`
317+
- `<ALIGNER>/umitools/` (UMI-tools only)
318318
- `*_edit_distance.tsv`: Reports the (binned) average edit distance between the UMIs at each position.
319319
- `*_per_umi.tsv`: UMI-level summary statistics.
320320
- `*_per_umi_per_position.tsv`: Tabulates the counts for unique combinations of UMI and position.
@@ -323,7 +323,7 @@ The content of the files above is explained in more detail in the [UMI-tools doc
323323

324324
</details>
325325

326-
After extracting the UMI information from the read sequence (see [UMI-tools extract](#umi-tools-extract)), the second step in the removal of UMI barcodes involves deduplicating the reads based on both mapping and UMI barcode information using the UMI-tools `dedup` command. This will generate a filtered BAM file after the removal of PCR duplicates.
326+
After extracting the UMI information from the read sequence (see [UMI-tools extract](#umi-tools-extract)), the second step in the removal of UMI barcodes involves deduplicating the reads based on both mapping and UMI barcode information. UMI deduplication can be carried out either with [UMI-tools](https://github.com/CGATOxford/UMI-tools) or [UMICollapse](https://github.com/Daniel-Liu-c0deb0t/UMICollapse), set via the `umi_dedup_tool` parameter. The output BAM files are the same, though UMI-tools has some additional outputs, as described above. Either method will generate a filtered BAM file after the removal of PCR duplicates.
327327

328328
### picard MarkDuplicates
329329

0 commit comments

Comments
 (0)