-
Notifications
You must be signed in to change notification settings - Fork 11
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
prodigal output not coherent with orf id #86
Comments
Right. I think this is the reading frame. Have you seen any genes with another number than 1? |
yes, it depends of the orfs |
what I did was cutting the first part of the id (for example, "1_1" in "_1") and then paste it to the chr column. |
Is it really sometimes "1_1"? I've only seen "_1". |
OK. The "_n" part doesn't seem to be the reading frame, but a counter for multiple orfs on the same contig. To uniquely identify an orf you hence need to keep the full name, you can't delete anything. What do the corresponding fasta files contain in terms of identifiers? |
Check the names of orfs from |
Solved in PR #87 |
The orf 'id' of prodigal output is weird. Both gff and .fna/.faa output have different names.
As reported in prodigal repository with an issue hyattpd/Prodigal#99 , the orfs get an extra "_1" or similar. this is problematic as none of gff, .fna and featurecounts tables have the same name. it will be impossible then merge the final tables.
I guess that it is an issue inside prodigal, so what we could probably do it is to write an external code (new module for sub workflow) that fix the tables after featurecounts.
The text was updated successfully, but these errors were encountered: