-
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
Consensus coverage in diploid mode #29
Comments
You are right. By the way, what is your senario of using this diploid mode? Does the result look good to you? Yan |
Ok, thanks! I'm working on genotyping SVs and, at least from the few examples I opened in IGV, it seems to work quite well: when I clearly see two alleles in the reads, I get two consensus. Since the weights of each consensus are quite important to me, is it possible (using the current available functions) to get the heaviest weighted consensus (in "aploid" mode) and then get a second heaviest consensus? Do you see any easy way to do this? Luca |
I will try to work on that, will get back to you when I have any updates. Yan |
Oh, great! Thanks! Best, |
Hi Luca, Sorry that I didn't update for such a long time. Thanks, |
Hi Yan, In the zip you can also find the IGV screenshots of the two regions I considered (the alignments clearly show some differences between the haplotypes). Let me know if they are a good starting point or if you need anything else. Best, |
Hi, Just pushed the latest version to github, please try out the multiple consensus sequences mode: set -d/--max-n-cons as the desired value. Lines 101 to 111 in bfe4ac0
Yan |
Thanks Yan!! I'll check it out. Best, |
Hi all,
first of all: great library!
I was playing around with diploid mode and I ran into strange segmentation faults (when freeing
cons_cov
). From what I could see, in diploid mode,cons_cov
is not used at all:abPOA/src/abpoa_graph.c
Lines 817 to 818 in 637c79f
So, I'm assuming that it's not possible to get consensus coverage in diploid mode. Is this true?
Thanks,
Luca
The text was updated successfully, but these errors were encountered: