Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Genotyping of fragments with discordant bases #5

Open
andurill opened this issue Feb 10, 2020 · 0 comments
Open

Genotyping of fragments with discordant bases #5

andurill opened this issue Feb 10, 2020 · 0 comments

Comments

@andurill
Copy link
Contributor

In the current version of GBCM, when a discordant base in encountered between reads in a fragment, and one of the base is "N", its not taken into REF or ALT genotyping. For example, in the screenshot below, the discordant base between the 2 reads in a fragment is highlighted - "T" in one read and "N" in the other. This fragment was excluded from ALT genotype count. While this is the desired behaviour in cases where specificity is important, it will be useful to have an option to prioritize sensitivity. Adding an optional argument that will enable counting these fragments towards genotype counts will be very useful. To elaborate, using this reference case, if the base at the position in one of the reads in the fragment is "N" and the other is "T", it should count towards alt genotyping in the sensitivity mode. Whereas if one is "N", and the other is "G", it should count towards ref genotyping.

If however, neither of the bases is "N", and there is discordance between the reads, that fragment should be excluded from genotyping, even under the sensitivity setting (this is the current behaviour and should be retained).

GBCM_fragment_count_discordant_bases

Test data available on the juno server.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant