chhylp123
chhylp123
Hifiasm in general doesn’t have coverage-based assumptions. So as long as the reads coming from the regions with uneven coverage are long enough, hifiasm should be fine to assemble through...
It is hard to say. But in most cases, uneven coverage means there might be some issues within the datasets.
Sorry for the late reply. How much larger for each haplotype is it? If the assembly is fragmented, it is common that it is a little bit larger since the...
Sorry for the late reply. Currently the short answer is no. Dual assembly might be the only solution to get two haplotypes.
Yes, I agree with @olekto
Actually another solution is to use fewer CPUs, that might be also helpful to reduce the memory. We would like to release a new version that takes less memory soon.
Hi @ethan-baldwin, I am wondering if you can share the bin files with me? Then I could do a very quick test to fix this issue. This should be a...
Thank you so much @ethan-baldwin! Could you please show me a screenshot for each bin file? Some bin files are not necessary for me to debug. This issue is likely...
@ethan-baldwin Could you please share me `sarracenia.hic.ec.bin`, `sarracenia.hic.ovlp.source.bin`, `sarracenia.hic.ovlp.reverse.bin` and , `sarracenia.hic.hic.lk.bin` with me? It would be better that you can also share the command lines/hifaism version you were using...
Sorry for the late reply since I was too busy during the last a few weeks. Basically, you could have a try to set `--n-hap` to > 2, which will...