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
Since GTDBtk is using Prodigal, I was wondering if maybe you have thought about switching to Pyrodigal?
In case you haven't came across the Prodigal bug yet: A typo in the node scoring function causes Prodigal to apply a score penalty to any candidate gene located on the reverse strand. It's patched already, but there's no official patch release: hyattpd/Prodigal#88
I think since release 2.0.0 Pyrodigal is a reliable, faster and most important actively maintained version of or successor to Prodigal.
You might want to think about giving it a try. 😉
Greetings,
Linda
The text was updated successfully, but these errors were encountered:
It is definitely worth taking a closer look at Pyrodigal, as it is becoming more and more popular, many people and tools are currently switching to it.
Hi,
Since
GTDBtk
is usingProdigal
, I was wondering if maybe you have thought about switching to Pyrodigal?In case you haven't came across the Prodigal bug yet: A typo in the node scoring function causes Prodigal to apply a score penalty to any candidate gene located on the reverse strand. It's patched already, but there's no official patch release: hyattpd/Prodigal#88
I think since release 2.0.0 Pyrodigal is a reliable, faster and most important actively maintained version of or successor to Prodigal.
You might want to think about giving it a try. 😉
Greetings,
Linda
The text was updated successfully, but these errors were encountered: