# HG changeset patch
# User jjohnson
# Date 1613950834 0
# Node ID 900cd28657689b05f8acb36034967fd34da42943
"planemo upload commit 61f6c8e7f32f170ad7e66e46dd74e8c5d361a722"
diff -r 000000000000 -r 900cd2865768 fgbio_group_reads_by_umi.xml
--- /dev/null Thu Jan 01 00:00:00 1970 +0000
+++ b/fgbio_group_reads_by_umi.xml Sun Feb 21 23:40:34 2021 +0000
@@ -0,0 +1,108 @@
+
+ Groups reads together that appear to have come from the same original molecule
+
+ macros.xml
+
+
+ fgbio --version
+
+
+
+
+
+
+
+
+
+
+
+
+ If not specified then all UMIs must have the same length,
+ otherwise discard reads with UMIs shorter than this length
+ and allow for differing UMI lengths.
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ output_counts == True
+
+
+
+ = min-map-q. Paired-end reads must have both reads mapped to the same chromosome with both reads having mapping quality >= min-mapq. (Note: the MQ tag is required on reads with mapped mates).
+
+This is done with the expectation that the next step is building consensus reads, where it is undesirable to either:
+
+ - Assign reads together that are really from different source molecules
+ - Build two groups from reads that are really from the same molecule
+ - Errors in mapping reads could lead to both and therefore are minimized.
+
+Grouping of UMIs is performed by one of three strategies:
+
+ - identity: only reads with identical UMI sequences are grouped together. This strategy may be useful for evaluating data, but should generally be avoided as it will generate multiple UMI groups per original molecule in the presence of errors.
+ - edit: reads are clustered into groups such that each read within a group has at least one other read in the group with <= edits differences and there are inter-group pairings with <= edits differences. Effective when there are small numbers of reads per UMI, but breaks down at very high coverage of UMIs.
+ - adjacency: a version of the directed adjacency method described in umi_tools that allows for errors between UMIs but only when there is a count gradient.
+ - paired: similar to adjacency but for methods that produce template with a pair of UMIs such that a read with A-B is related to but not identical to a read with B-A. Expects the pair of UMIs to be stored in a single tag, separated by a hyphen (e.g. ACGT-CCGG). The molecular IDs produced have more structure than for single UMI strategies, and are of the form {base}/{AB|BA}. E.g. two UMI pairs would be mapped as follows AAAA-GGGG -> 1/AB, GGGG-AAAA -> 1/BA.
+
+edit, adjacency and paired make use of the --edits parameter to control the matching of non-identical UMIs.
+
+By default, all UMIs must be the same length. If --min-umi-length=len is specified then reads that have a UMI shorter than len will be discarded, and when comparing UMIs of different lengths, the first len bases will be compared, where len is the length of the shortest UMI. The UMI length is the number of [ACGT] bases in the UMI (i.e. does not count dashes and other non-ACGT characters). This option is not implemented for reads with UMI pairs (i.e. using the paired assigner).
+
+http://fulcrumgenomics.github.io/fgbio/tools/latest/GroupReadsByUmi.html
+ ]]>
+
+
diff -r 000000000000 -r 900cd2865768 macros.xml
--- /dev/null Thu Jan 01 00:00:00 1970 +0000
+++ b/macros.xml Sun Feb 21 23:40:34 2021 +0000
@@ -0,0 +1,56 @@
+
+ 1.3.0
+ 0
+
+
+ fgbio
+
+
+
+ (([1-9][0-9]*[TBMS])*([+]|[1-9][0-9]*)[TBMS])
+ @READ_STRUCTURE_PATTERN@(\s@READ_STRUCTURE_PATTERN@)*
+
+ ^@READ_STRUCTURES_PATTERN@$
+
+
+ ^[A-Za-z][A-Za-z]$
+
+
+
+
+
+
+
+
+
+
+ pairs much like the CIGAR string in BAM files. Four kinds of operators are recognized:
+
+ T identifies a template read
+ B identifies a sample barcode read
+ M identifies a unique molecular index read
+ S identifies a set of bases that should be skipped or ignored
+
+The last pair may be specified using a + sign instead of number to denote “all remaining bases”. This is useful if, e.g., fastqs have been trimmed and contain reads of varying length. For example to convert a paired-end run with an index read and where the first 5 bases of R1 are a UMI and the second five bases are monotemplate you might specify:
+
+::
+
+ --input r1.fq r2.fq i1.fq --read-structures 5M5S+T +T +B
+
+Alternative if you know your reads are of fixed length you could specify:
+
+::
+
+ --input r1.fq r2.fq i1.fq --read-structures 5M5S65T 75T 8B
+
+
+]]>
+
+
+
+
+
+