You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
hm, looking at the genome, I am pretty sure it is caused by this giant 500bp of noncoding space between gp2 and gp3
I have the tolerance for noncoding gaps currently hard set at 300bp. Usually there are spurious false positive ORFs that allow the FASTPATH to jump such gaps, but it appears there is not a single possible ORF within that region.
To verify my suspicion, I fudge the genome a little to introduce a tiny ORF between the gp2 and gp3 genes by changing the internal stop codon in the pink/yellow region to an AGA and it allowed phanotate to jump the gap:
I have the gap limit set to 500bp in the phanotate 2.1 version (which also allows it to run successfully on the genome without fudging it), but I haven't gotten around to pushing that version to the main branch here or pypi due to other errors that I was not able to debug since the genomes that crashed it were not publicly available to me. In the meantime I should update the 1.X version to have a large gap.
Running phanotate on some phage gives me this error. The below is from Hubei odonate virus 11:
I have seen the error in phanotate version 1.5.1 (python 3.7 and 3.10) and the latest from github (1.6.3) on python 3.10.
The text was updated successfully, but these errors were encountered: