Hu Jiang
Hu Jiang
For short reads, see #29
Hi, first, thank you for your good suggestions. However, SNP and INDEL are hard to distinguish for NextPolish, because NextPolish correct error-bases using kmers, so NextPolish does not distinguish between...
Not test, but you can try it.
1. The max memory required by NextPolish is depending on the value of `-p`, each sub-process required 2-5Gb RAM depending on the mapped data depth. So 64 Gb of Ram...
In theory, NextPolish will skip polished contigs, so it should not have duplicate IDs, I need more time to debug it. By now, it is more safer to remove `pb.asm.nextpolish1.fa`...
Hi, I do not familiar with docker, so you can follow [here](https://nextpolish.readthedocs.io/en/latest/QSTART.html#installation) to have a try.
Hi, the available memory of your system is not enough, maybe you need to try a system with more available memory.
I do not test, but you can try to set `-max_depth` to control haw many reads are used to polish, see [here](https://nextpolish.readthedocs.io/en/latest/OPTION.html)
Is your genome assembled with hifi? If it is, there is no need to polish it using subreads, but you can polish it use HIFI reads. Btw, because these results...