Support for QSEQ parsing.

This relates to issue #389.  @audy, @wasade.

Added parse_qseq, QseqIterator, support in the factory for .qseq and .qseq.gz.  Added unit tests.

For Sequence ID, I am using: "machine_name"_"run_number":"lane_number":"tile_number":"x":"y"#"index"/"read".  Example: CRESSIA_242:1:2204:1453:1918#0/1.  Do you agree?

I set qual_id to seq_id.  Do you agree?


Would it be better to raise an exception?

--austin

> On Aug 7, 2014, at 23:02, Laurent Luce <notifications@github.com> wrote:
> 
> In skbio/parse/sequences/qseq.py:
> 
> > +from skbio.core.exception import RecordError
> > +from skbio.util.io import open_file
> > +
> > +from .fastq import ascii_to_phred64
> > +
> > +
> > +def parse_qseq(infile, strict=True):
> > +    r"""Generator of sequence ids, sequences, quals and other records
> > +    from a qseq file.
> > +
> > +    Parameters
> > +    ----------
> > +    infile : open file object or str
> > +        An open qseq file or a path to a qseq file.
> > +
> > +    strict : bool
> Removed strict for now. I can add it back when someone has a use case for it.
> 
> —
> Reply to this email directly or view it on GitHub.