Hello,
I was able to run the MEDI build pipeline without getting an error message (although I had to use the K2 functions instead of kraken2-build as I otherwise had rsync problems).
While I am able to run the quant script now and MEDI will produce an output, I believe that there could be an issue with my database size. I specified a max size of 500GB in my script; however, my final hash.k2d file was roughly 354GB and the database.kraken is 155GB.
I would imagine that this could impact the sensitivity of the results as I ran a few test samples an the only food matches in the output were Teas.
Is this an issue you have experienced or do you have any thoughts on why there is a large database size mismatch?
Thank you in advance,
Hello,
I was able to run the MEDI build pipeline without getting an error message (although I had to use the K2 functions instead of kraken2-build as I otherwise had rsync problems).
While I am able to run the quant script now and MEDI will produce an output, I believe that there could be an issue with my database size. I specified a max size of 500GB in my script; however, my final hash.k2d file was roughly 354GB and the database.kraken is 155GB.
I would imagine that this could impact the sensitivity of the results as I ran a few test samples an the only food matches in the output were Teas.
Is this an issue you have experienced or do you have any thoughts on why there is a large database size mismatch?
Thank you in advance,