Skip to content
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

Feature request: More helpful IO error messages #20

Open
ivirshup opened this issue Mar 3, 2020 · 0 comments
Open

Feature request: More helpful IO error messages #20

ivirshup opened this issue Mar 3, 2020 · 0 comments

Comments

@ivirshup
Copy link

ivirshup commented Mar 3, 2020

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:

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.

Your Environment

  [8e4a8c10] BED v0.1.0
  [37cfa864] BioCore v2.0.5
  [af1dc308] GFF3 v0.1.0
  [4f8a0a0a] GenomicAnnotations v0.1.4
  [899a7d2d] GenomicFeatures v2.0.0
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant