When a bad read gets parsed, matchbox produces error: error parsing an input read. This error is unhelpful, and should at least tell you the ID or number of the bad read, or line number of the parse error.
Additionally, when you run matchbox on a file which is not gzipped, but which is wrongly named eg reads.fq.gz, matchbox throws error: error parsing an input read. This error should tell you that it was a gzip-related error (because internally, we know this).
The same error is thrown in the inverse case when a file is gzipped, but is wrongly named eg reads.fq. This case is trickier because we no longer know the garbledness is gzip-related unless we choose to explicitly check, but would also be good to handle.
When a bad read gets parsed, matchbox produces
error: error parsing an input read. This error is unhelpful, and should at least tell you the ID or number of the bad read, or line number of the parse error.Additionally, when you run matchbox on a file which is not gzipped, but which is wrongly named eg
reads.fq.gz, matchbox throwserror: error parsing an input read. This error should tell you that it was a gzip-related error (because internally, we know this).The same error is thrown in the inverse case when a file is gzipped, but is wrongly named eg
reads.fq. This case is trickier because we no longer know the garbledness is gzip-related unless we choose to explicitly check, but would also be good to handle.