Closed lijing28101 closed 7 years ago
My input scripts assume the attribute column is formatted as .*ID=([^;]+).*Parent=([^;]+).*
, where the ID tag is the name of the feature and Parent the name of its parent. This follows the GFF3 specification.
Your GFF file is also formatted according to specifications, but changes the order of ID and Parent. This is a bug on my side, since the tags are not required to be in any particular order.
There is a second issue, though, that your bug report reveals. On my test data, the ID was also the name of the feature (e.g. AT1G1010). Whereas in your files, the ID is an integer key. The GFF specification says only that the ID must be unique to the feature, so both approaches are fine and fagin
should be able to deal with them.
I'll code up a better parser. Thanks for the bug report!
OK, I've implemented a new GFF parser. Try pulling the latest release from master and rerunning the analysis.
I've made a few more bug fixes and cleaned up the scripts. Now everything works on my system and should have the flexibility to handle yours.
I'll close the issue.
When I use Glycine max GFF file
and the command
I get the error message
I am using
Fagin v0.6.0
Here is my system info