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

Filtering based on MAPQ after WASP #43

Closed
ghost opened this issue Apr 6, 2016 · 2 comments
Closed

Filtering based on MAPQ after WASP #43

ghost opened this issue Apr 6, 2016 · 2 comments

Comments

@ghost
Copy link

ghost commented Apr 6, 2016

Hi all,

I implemented WASP to reduce mapping biases and reference biases.
My question is: Is it still recommended to implement an additional filtering step based on MAPQ 10 or 20 of reads after WASP's pipeline or this will cause an underestimation of read counting and excessive reads loss ? In am wondering if the additional filtering I implemented is causing loss of power to detect true expression data.

Best
anto
kings College London

@gmcvicker
Copy link
Collaborator

Hi Anto,

My opinion is that filtering on MAPQ10 or MAPQ20 should be fine and should not result in the loss of an excessive number of reads.

One caveat is that the mapping quality of a read could potentially differ depending on what allele is present in a read. Therefore, to avoid bias I would recommend doing the MAPQ filtering as part of both the initial mapping (Step 1) and remapping (Step 3) steps of the pipeline.

Hope this helps,

Graham

@ghost
Copy link
Author

ghost commented Apr 11, 2016

Hi Graham,

many thanks. I have done as you recommended, providing as additionally filtering for properly paired
reads.
Thanks,
antonino

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