New feature: allow user to collapse R1 and R2 in the same UMI group to separate consensus reads #22
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Hi dynast team:
Thanks for developing this amazing tool.
I added a new feature to the
dynast consensustool. Users can add one extra tag--separate-r1-r2to collapse R1 and R2 to separate consensus reads, while maintaining the same qname (SHA256 hash for the UMI group) for both of them. After collapsing, the R1 consensus will have flag 65 (read paired, first in pair), and the R2 consensus will have flag 129 (read paired, second in pair).Running
dynast consensuswithout specifying--separate-r1-r2will have the same result as before, i.e. R1 and R2 will be collapsed together.I updated the source code and added a help message. I also updated the version from 1.0.1 to 1.0.2beta in this pull request.
Best,
Qirong