Detailed progressive bloom filter report about biobloom HOT 3 CLOSED

Sounds great! We definitely need something like that for debugging.

The other thing that will be VERY useful is the information that comes from the repeat filter so we could work on the improvement of repeats recruitment. What about including the number of kmers in the read considered as repeats? We can trace back if the read ends up in the recruited reads even if containing a considerable amount of repeat kmers (this is for the tagged reads)

from biobloom.

Edit proposed. I think I'll have to check the repeat filter meaning we will incur a bit more computational cost but only when we run -P. Shouldn't be a big deal since it is for debugging anyway.

from biobloom.

Code seems to be fine on my end:
Branch https://github.com/bcgsc/biobloom/tree/ntHashBF
80248e0

from biobloom.