-
Notifications
You must be signed in to change notification settings - Fork 6
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
conon alignment giving likelihood = 0 error #19
Comments
I'm having the same issue with the same error. I saw an older issue brought up, but the resolution was using a new version, i.e. v1.70427 #12 |
Thanks for the response. I will try using the latest version. Since I posted this I have also started to use CANOPY instead since, according to the publication, it seems like a more robust aligner compared to PRANK and it seems to work well. |
Found a (hopeful) solution. The development branch version of prank (prank-170703) does not throw this error. I'm assuming the conda recipe package which lists 170427-1 and 170427-2 uses one of these development branch versions that are not the stable version. Anyways, this should solve future problems hopefully! |
Anyone still reading this? :-) I have the same problem, prank v.170427. Where can I find this newer version? Kind regards, |
You can find it on the wasabi website: http://wasabiapp.org/download/prank/development/ Installation instructions can be found at this link. http://wasabiapp.org/software/prank/prank_installation/ |
Hi - many thanks for the link! That solved my issue. Kind regards, |
Hi :) |
Hi,
I am using PRANK v.170427.
I am having trouble with codon alignment. When I execute the line of code
prank -d=OG0017868.ffn -o=prank_test_out -F -codon
I get the following errors
This happens for every multiple alignment iteration. I am only using 4 sequences. When I run the code without performing codon alignment, it works perfectly.
Do you know what might be wrong? Attached you can find my fasta file. The suffix was originally .ffn but I changed it to .txt so I could attach here.
OG0017868.txt
.
Thank you.
The text was updated successfully, but these errors were encountered: