-
Notifications
You must be signed in to change notification settings - Fork 18
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
Remove low coverage bases from consensus sequence? #67
Comments
I guess you mean the consesus called by abPOA may not be as accurate as you expected? |
Hi Yan, Here is a section of the MSA output from abPOA (everything at default). I outlined the expected behaviour in green box and unexpected in red. Cheers |
Thanks for the clarification! I can re-add this option. |
Hi Yan, Thanks so much for your swift response! I don't know if you have benchmarked the performance of two consensus algo, here is my findings: Sequences are generated with fixed and independent errors You may close this issue. Cheers, |
Hi Jiaan, Thanks for the information. Actually I wasn't aware of this "input-number-dependent" performance difference. |
Hi Yan, (1) I randomly subset sequences from a reference fasta (E.coli etc.) as templates. The length of the templates can be 1K to 5K; but the consensus accuracy is independent of the length anyway. (2) Simlord to insert errors into the templates https://bitbucket.org/genomeinformatics/simlord/src/master/.
-n 10 for 10 repeats; -t 0.18 for overall error rate (3) Generate consensus sequence with abPOA: (4) I use edit distance (a python package) to calculate read accuracy. https://pypi.org/project/editdistance/
Cheers |
Hi Yan,
I use abPOA to generate a consensus from four sequences. Here is the distribtuion of n_seq / n_cov in each base in the consensus sequence. My question is, is there a way to remove low coverage bases? For this consensus sequence, the coverage should be 0.25/0.5/0.75/1; however, the low coverage bases at 0.25 are clearly errors from the input sequences.
Cheers,
Jiaan
The text was updated successfully, but these errors were encountered: