integer underflow bug? about ntcard HOT 6 OPEN

I think it is an underflow but I thought I fixed this. Just confirming but your filtered.fastq is extremely small right?

from ntcard.

You are right, it should be an underflow instead of an overflow.
The FASTQ has only 3 reads.

from ntcard.

so as I understand the problem is there isn't enough reads to sample and every value should be 0 in that tsv aside from F1 so that is definitely a bug but what is the user's intention in using a file with only three reads?

from ntcard.

so as I understand the problem is there isn't enough reads to sample and every value should be 0 in that tsv aside from F1 so that is definitely a bug but what is the user's intention in using a file with only three reads?

It's easier/better to run an assembler on a file and see if it fails or succeeds to assemble anything rather than predict if/when it will fail or succeed.

from ntcard.

@jowong4
I remember you fixed this issue, right?
need to add an error exception for ntcard on too few read/kmers.

from ntcard.

We had quite a picnic with this bug, in our case it happened because ntCard uses the name of the read to determine the type of the file, not sure why this is even needed.

The offending function is: getftype @ ntcard.cpp

from ntcard.