-
Notifications
You must be signed in to change notification settings - Fork 31
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
Missing phasing on some variants #164
Comments
We believe it's a decision of the phasing algorithm. As the last step, Clair3 simply runs Whatshap with default parameters on |
The latest updates show --longphase_for_phasing was added as an option and then updated to enable by default, is that correct? Does that mean longphase is being used instead of whatshap? It looks like longphase has not yet added a feature to phase indels due to their high error rate with ONT in the past. If longphase is being run by default, is there a parameter to change the default back to WhatsHap? |
The naming of the two options |
Ah okay, thank you for the explanation, that makes much more sense. We needed the indel in that screenshot above to be phased so I ended up re-running the merge_output.vcf through Whatshap and added the --indels option. Perhaps that could be a helpful option to include for some users in next releases. Thank you again! |
Hello,
I ran Clair3 R10 model with the --enable_phasing option and noticed not all variants are phased in the final output. The two positions I am looking at are 29 bp apart on the same amplicon. Does this indicate a failure of the phasing algorithm or do I need to change another parameter? I've pasted the VCF output below and attached an IGV screenshot of the region.
chr7 117548606 . A ATG 22.5 PASS F GT:GQ:DP:AF 0/1:22:69:0.2464
chr7 117548628 . G T 22.34 PASS F GT:GQ:DP:AF:PS 1|0:22:69:0.3913:117548628
The text was updated successfully, but these errors were encountered: