Closed soungalo closed 2 years ago
Found the bad record. It's this one, strating at line 398592:
An-1__chr2_12990458-12991147 EVM gene 0 463 . + . ID=ATAN-2G49800;Note=protein_coding_gene
An-1__chr2_12990458-12991147 EVM mRNA 0 463 . + . ID=ATAN-2G49800.1;Parent=ATAN-2G49800
An-1__chr2_12990458-12991147 EVM CDS 0 272 . + 0 ID=ATAN-2G49800.1.cds1;Parent=ATAN-2G49800.1
An-1__chr2_12990458-12991147 EVM CDS 356 463 . + 0 ID=ATAN-2G49800.1.cds2;Parent=ATAN-2G49800.1
An-1__chr2_12990458-12991147 EVM exon 0 272 . + . ID=ATAN-2G49800.1.exon1;Parent=ATAN-2G49800.1
An-1__chr2_12990458-12991147 EVM exon 356 463 . + . ID=ATAN-2G49800.1.exon2;Parent=ATAN-2G49800.1
For some reason, it has a 0 start coordinate, which is illegal in gff. Since I wrote the script that created this gff - totally my bad. Still, it'd be nice to have a more meaningful error message pointing to the problematic record.
I think this is addressed in v0.11, but added a regression test in https://github.com/daler/gffutils/pull/191 to ensure this doesn't show up again in the future.
Now addressed in v0.11.
Hello, I am using python 3.8.6 and gffutils 0.10.1. When loading a specific gff3 file, I get the error message:
sqlite3.InterfaceError: Error binding parameter 11 - probably unsupported type.
. I've seen in past issues that this used to happen with very large chromosomes, but I understand that this has been fixed, and also my genome doesn't have any large chromosomes. Interestingly, I have another very similar gff file, for which everything works fine. Here's what I did:And here are the two gff files: gff_1.gff3.gz gff_2.gff3.gz
Any idea what's wrong with gff_2.gff3?
Thanks!