Some sequencing protocols provide different length forward and reverse reads (e.g, 100 bases in the forward, 200 in the reverse). evSeq currently assumes that both forward and reverse reads are the same length. Only sequencing runs with same-sized readlengths should currently be analyzed. There are some hacky ways to get around this, but they're not really tested. Future updates should resolve.
Some sequencing protocols provide different length forward and reverse reads (e.g, 100 bases in the forward, 200 in the reverse). evSeq currently assumes that both forward and reverse reads are the same length. Only sequencing runs with same-sized readlengths should currently be analyzed. There are some hacky ways to get around this, but they're not really tested. Future updates should resolve.