You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It would be nice to get some more information back from readers when they fail to parse. If I know why the reader is failing, I might be able to correct the problem.
Current Behavior
Here are some current error messages:
ERROR: GFF3.Reader file format error on line 1 ~>"191\tgene"
ERROR: BED.Reader file format error on line 1 ~>".\t-\tFLAI"
Possible Solution / Implementation
I think these messages could be a bit more helpful, using the information available to the parser. Some useful things to know would be:
What field caused the error?
What values would be expected?
What spec is being followed for this file format? This could maybe just be handled in the docs, but it would be nice to have a link to the spec somewhere.
Context
I was trying to read a gtf file, then a bed file when I got the errors above. The bed file had been converted from the gtf using convert2bed. Both of these files work fine with bedtools, igv, and bedops. So what's going on? If the error message described what value didn't match what expression, I'd could try and fix the file and move on. Instead it becomes a search though source code.
Expected Behavior
It would be nice to get some more information back from readers when they fail to parse. If I know why the reader is failing, I might be able to correct the problem.
Current Behavior
Here are some current error messages:
Possible Solution / Implementation
I think these messages could be a bit more helpful, using the information available to the parser. Some useful things to know would be:
Context
I was trying to read a gtf file, then a bed file when I got the errors above. The bed file had been converted from the gtf using
convert2bed
. Both of these files work fine withbedtools
,igv
, andbedops
. So what's going on? If the error message described what value didn't match what expression, I'd could try and fix the file and move on. Instead it becomes a search though source code.Your Environment
The text was updated successfully, but these errors were encountered: