Since my computer memory is 8 GB, I cannot trained the silva, so I used V3V4 classifier trained with sklearn 0.21.2. I am using QIIME2-2019.7 that is compatible with sklearn 0.21.2.
When I entered to following command to create taxonomy.qza :
qiime feature-classifier classify-sklearn --i-classifier silva_132_99_v3v4_q2_2019-7.qza --i-reads rep_seqs.qza --o-classification taxonomy.qza
Hi @arne! Is there any more to that error message? Or maybe a logfile you can share?
I haven't run into this myself, but a quick forum search tells me this could still be a memory issue.
How much memory have you allocated to your Virtualbox? You might try increasing the memory available to it.
Another alternative, if that doesn't work and you don't have access to a computer with more memory is:
@arne, The error message is just telling you that --p-reads-per-batch isn't a parameter for fit-classifier-naive-bayes. --p-reads-per-batch is an option for the classify-sklearn command you were trying to run in your original post.
The same command is still being killed in the output you just posted, likely for the same reason as before. fit-classifier-naive-bayes has a similar chunk-size parameter you can adjust to trade more time for lower memory needed. Pass an integer smaller than the default 20,000 if you decide to use it. Maybe start with 1000, and experiment from there?
Nice! A new error message means progress!
I’m not sure what you mean by “clean the junk file”, and haven’t spent any time with VirtualBox yet, so don’t know if it offers any special features for cleaning up a system.
If I were you, I’d probably just remove any files I don’t need for this analysis, or move them off the virtualbox image. There’s no special command to delete QIIME 2 Artifacts/Visualizations - they’re just zip archives, and can be deleted like anything else (after backing them up elsewhere if you’ll need them in future).
If you’re still short on space, you could add some extra space to your virtualbox, or look up how to free up disk space in VirtualBox and whatever linux distro you’re running on the virtualbox (Looks like Ubuntu if you’re using our image). Temp files are probably deleted by the system when you reboot, but if this is a heavily-used system, there could be some stuff cluttering your apt-cache or something?
Finally, if you’re just not sure where all your space went, this bash command will give you a sorted list of the largest files on your system, which might help you find candidates for removal. du -S | sort -n -r |more
Good luck!
Chris
p.s. If you have multiple cores available to your virtualbox image, setting classify-sklearn's --p-n-jobs parameter to the number of available cores will save you some time.