Closed snayfach closed 5 years ago
I tracked down the bug and it was a combination of two things: 1) there was a +1 offset error that caused an ORF to be connect to itself and 2) I had changed the error message that fastpathz outputs from a single line to multiple, which caused the Negative Cycle error to not be caught by PHANOTATE
I have fixed both, and pushed updates to the repo. Thanks for the help : )
Thanks for looking into this. Do you think this bug affected the output of runs that completed without errors? Should I re-run the tool on my data now that the bug is fixed?
Nope the bug should not have affected any runs that ran properly. To test I ran 4,373 phage genomes from PATRIC through PHANOTATE with the old version and the new version and the output from both were 100.00% identical : )
Occasionally, phanotate gives the error:
Here is the 1.9Kb sequence that generates the error: https://www.dropbox.com/s/bv56zgc0ohf0w1z/test2.fna?dl=0
Prodigal runs fine and identifies 5 genes on this sequence.
Any ideas what could be wrong?