Yes, your details are correct with a few caveats. Disk based: By default, KAnalyze fills a memory buffer (k-mer "segment"), sorts and counts it, then dumps it to disk. Then the memory buffer is cleared and the next set of k-mers are counted. Instead of dumping the buffer to disk, it can move it to another place in memory (Option --nodumpseg) and re-allocate the memory buffer. This mode is not recommended unless the machine has lots of memory to work with. In Java, this is also less efficient because...
KAnalyze 2.0.0 has been released!
KAnalyze 2.0.0 has been released!
Completed k-mer utility conversion and unit tes...
Merge branch 'stdio' into prefilter
Pre-1.0.0 build (NOT to be released!). Testing ...
Merge branch 'dev' into prefilter
Filter code in place. Modules need code to run it.