When forward and reverse reads are in agreement on the events (eg. deletion)
amplicanConsensus will mark forward event as TRUE indicating that he
In cases where forward and reverse read agree only partially, for example,
they share the same start of the deletion, but they have different end
amplicanConsensus will pick the version of
read with higher alignment score, in situation where both of the reads
overlap expected cut site, otherwise both events will be rejected and marked
FALSE. When there are events only on one of the strands they will be
(data.frame) Contains relevant events in GRanges style.
(data.frame) Should be table containing at least positions of primers in the amplicons and their identifiers
(character) Specifies which metadata column of
(boolean) Allows to relax consensus rules. When TRUE will allow Indels that are not confirmed by the other strand (when both are used).
In situation where you have only forward or only reverse reads don't use this function and assign all TRUE to all of your events.
Consensus out of the forward + reverse reads is required for
(bolean vector) Where TRUE means that given event represents consensus out of forward and reverse reads.
1 2 3 4 5
Add the following code to your website.
For more information on customizing the embed code, read Embedding Snippets.