Closed mtisza1 closed 8 months ago
Ah, a week ago or so ago I increased the distance threshold during the ORF connection step from 300bp to 500bp to fix a situation where gaps in the ORFs of the genome broke the path through the genome, but I forgot to also increase the distance in the code that should have found those gaps above the threshold and connected ORFs across the gap (not sure why it didn't to catch the gaps, probably an off-by-one error on my part)
Just fixed both distance thresholds to match and pushed the new version to pypi and here : )
$ phanotate.py -V
1.6.5
$ phanotate.py input.fasta | head
#id: uParvo_sus_pigfeces_SRR11413591_3481
#START STOP FRAME CONTIG SCORE
3 383 + uParvo_sus_pigfeces_SRR11413591_3481 -5.187465E+01
3240 835 - uParvo_sus_pigfeces_SRR11413591_3481 -2.416964E+27
Wow thanks for the quick fix! I'll close this.
Hi,
On certain sequences (perhaps because they have large gaps between ORFs),
phanotate v1.6.4
throws an error. This is not observed withphanotate v1.5.1
, which returns ORF predictions.The sequence below was used as the input. Notably, this contig is not predicted to belong to a phage genome, and therefore this may be the intended behavior of
phanotate
.Best,
Mike