First off, many thanks to the authors for a fantastic tool.
I have an issue with running krakenuniq-build with the --max-db-size option. I'm getting an enormous number of messages along the lines of:
kmer found in sequence w/ taxid 1002994464 that is not in database
I'm running in an HPC environment and so far the log is 3.5Tb and growing.
Presumably these messages are related to kmers that are being removed to shrink the database?
But is there a way to turn the messages off, as I'm running out of space...
Also, at what point in the process are these occurring? It looks like the database is built, so is this just a check at the end?
Hi,
First off, many thanks to the authors for a fantastic tool.
I have an issue with running krakenuniq-build with the --max-db-size option. I'm getting an enormous number of messages along the lines of: kmer found in sequence w/ taxid 1002994464 that is not in database
I'm running in an HPC environment and so far the log is 3.5Tb and growing.
Presumably these messages are related to kmers that are being removed to shrink the database?
But is there a way to turn the messages off, as I'm running out of space...
Also, at what point in the process are these occurring? It looks like the database is built, so is this just a check at the end?
Many thanks, Richard