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

Incorporating quality scores for ASE counts #18

Open
rmagoglia opened this issue Nov 10, 2016 · 2 comments
Open

Incorporating quality scores for ASE counts #18

rmagoglia opened this issue Nov 10, 2016 · 2 comments

Comments

@rmagoglia
Copy link

Curious what others think about this - when we find a read overlapping a SNP and we can match it to its parent of origin, should we be checking the quality score of that base in the read (and have it pass a certain quality threshold) before counting that read towards the total counts for that parental allele? To me this seems more in keeping with other methods (e.g. mpileup) and might yield more reliable results.

@petercombs
Copy link
Contributor

I think that's a reasonable idea, and it wouldn't even be that hard to implement. I am skeptical that it would necessarily change a whole lot, since my understanding is that the vast majority of Illumina bases are of very high quality . Unless you have a some evidence pointing towards a lot of reads getting mis-categorized, I don't think it's worth your time.

@tehranchi
Copy link
Collaborator

Yep, that's what I do. It won't change "a lot" percentage wise but it will likely have an effect on the false positives regarding ASE calls.

On Nov 10, 2016, at 2:53 PM, Peter Combs [email protected] wrote:

I think that's a reasonable idea, and it wouldn't even be that hard to implement. I am skeptical that it would necessarily change a whole lot, since my understanding is that the vast majority of Illumina bases are of very high quality . Unless you have a some evidence pointing towards a lot of reads getting mis-categorized, I don't think it's worth your time.


You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.

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

3 participants