Documentation should mention details regarding input reads parsing

[cerebis]

It seems that the format of input reads is determined by file extension. I would encourage you to document this behaviour.

Also, this is brittle and should ideally encompass multiple conventions for extension syntax to be robust. A better "automagic" approach would be to inspect the begging file contents for a match to either header format.

In the end, you might find it simpler to assume a format and give users the option to declare the other.

Separate issue, but I am being lazy

GZIP read files do not appear to be supported? This really awkward with today's sequencer yields.

[Dreycey]

@cerebis

These are great suggestions. I'll start by adding the current functionality to the README, and expand upon this by using an "automatic" approach that considers the first few initial sequences. Also, the suggestion of allowing for gzip makes a lot of sense. I'll add this functionality with the automatic tuning