-
Notifications
You must be signed in to change notification settings - Fork 53
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
Try Pyrodigal as a faster and maintained Prodigal alternative #149
Comments
oschwengers
added a commit
that referenced
this issue
Sep 23, 2022
oschwengers
added a commit
that referenced
this issue
Sep 23, 2022
oschwengers
added a commit
that referenced
this issue
Sep 23, 2022
oschwengers
added a commit
that referenced
this issue
Sep 23, 2022
oschwengers
added a commit
that referenced
this issue
Sep 23, 2022
oschwengers
added a commit
that referenced
this issue
Sep 27, 2022
oschwengers
added a commit
that referenced
this issue
Sep 27, 2022
oschwengers
added a commit
that referenced
this issue
Nov 2, 2022
oschwengers
added a commit
that referenced
this issue
Nov 2, 2022
oschwengers
added a commit
that referenced
this issue
Nov 2, 2022
oschwengers
added a commit
that referenced
this issue
Nov 2, 2022
oschwengers
added a commit
that referenced
this issue
Nov 2, 2022
oschwengers
added a commit
that referenced
this issue
Nov 3, 2022
…165) * add pyrodigal dependencies #149 * replace Prodigal by Pyrodigal #149 * remove check for Prodigal binary #149 * refactor pyrodigal training file logic #149 * bump pyrodigal dependency to 2.0.2 #149 * fix closed parameter for circular seqs #149 * remove redundant topology check for edge genes #149 * update readme #149
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Let's try if Pyrodigal might be a suitable, faster and most important actively maintained successor to Prodigal.
The text was updated successfully, but these errors were encountered: