Add --position argument to external subcommand for customising the UMI placement #15
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Proposed change
This PR introduces a new argument,
--position
, to theexternal
sub-command ofumi-transfer
. The--position
argument allows users to specify where the UMI is inserted, with the following options:On a technical level, all read processing is now moved to a separate module. This will also be useful, should we extend the tool by
umi-transfer inline
, which would partly perform the reverse action (extract the UMI from the read instead of pasting the two together).Motivation
Sarek supports the use of consensus reads to increase the accuracy of variant calls. Consensus reads are formed by identifying, grouping and collapsing duplicate reads that originate from the same DNA molecule. Sequencing errors are corrected in the process and therefore the number of artifactual variant calls reduced.
Sarek uses fgbio for consensus read formation and processing. While the tool supports using UMIs from external files, the pipeline's sample sheet doesn't allow for a third FastQ file as input. Hence, UMIs must be integrated to the read first.
Outlook
Possibly, this change justifies a v1.6 release?