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
Fix typo in score_nodes
function of node.c
#88
Conversation
Does this bug impacts the last release of Prodigal (v2.6.3; Feb, 2016) or is this a bug that has been introduced more recently? Just wondering how concerned I should be about this bug as we use Prodigal extensively. Is there any sense of how much fixing this bug changes the results produced by Prodigal? |
The bug is present in To get a patched version, you have to recompile the code yourself, as there was no release made since then. Otherwise consider checking Pyrodigal, which has the fix included, as well as some more performance improvements. |
Thanks for the bug fix, further information, and putting together Pyrodigal. We will look to move over to Pyrodigal. |
Hi @althonos, with the bug fix do you expect to see fewer or more genes being predicted? We're noticing that the fix result in marker genes that were previously being identified no longer being seen. We are digging deeper, but just hoping you can tell us if the expected result if for less genes to be predicted. |
Hi Donovan, the two fixes both affect the scoring penalization for some nodes while in metagenomic mode, which was before then applied to all start/stop codons on the reverse strand instead of those for "small genes" only (<120bp). I can't say consistently, but i've seen results where two small genes on the forward strand were not predicted anymore and replaced by a single larger gene on the reverse strand, since the fix now made it score higher. This is very circumstantial though. |
Thanks - we'll dig in. |
Hi there!
The latest version of the code contained a typo that was causing the coding penalization to be applied even on large genes of the reverse strand.