So of all of the sets that I'm working with, they are all 150x2 reads.
I have 2 sets that were done on Novaseq 6000, I believe these are called high quality Mate-Pair reads, as they are in FR orientation. My other sets were done on the Aviti sequencer.
I understand the target read length, and probably overall they are in that range.
So my assumption that give 150bp reads, if after adapter removal most reads that fall below 150bp are likely mergeable, and the BBMerge overlap correction can help correct errors on the ends of the reads. Pairs that remain at 150bp after adapter removal have a length somewhere over 300bp.
It's not my goal to actually merge the reads, but just to do error correction for a better assembly. But maybe merging is OK too??? I do not believe that metaspades can include single reads, so they want paired reads. Apparently Metaspades wants paired reads to be interleaved, as I tried using as separate pairs and when I looked at the corrected reads, half of my reads disappeared. I did again interleaved and it looked like all or most of my reads were present.
I assume that it's best if you can take all of the reads that are intended to be assembled and process with tadpole all together, but if it won't run due to running out of memory, that's my main question. So if I can't run them all at the same time, I wondered about running subsets of the reads for error correction, then combining them back again for assembly.
Not exactly an answer to your question, but it still may be useful.
If you are going to assemble with SPAdes in the end, it does error correction so you probably shouldn't do it beforehand.
A small C program for error correction that does an excellent job, is multithreaded, and likely won't cause memory problems:
https://github.com/lh3/bfc
This normally works for me and is very fast, plus can't remember ever having memory issues.