Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

polishing strategy and rounds #43

Open
binlu1981 opened this issue Aug 3, 2020 · 3 comments
Open

polishing strategy and rounds #43

binlu1981 opened this issue Aug 3, 2020 · 3 comments

Comments

@binlu1981
Copy link

Hi,

I have an assembly generated using wtdbg2 which could use wtpos-cns performing polishment. Will I get a better result through performing additional long- or short-reads polishing steps using the NextPolish? Would it produces conflict results using different polishing tools?
How many rounds can reach best status and how to determine?

@moold
Copy link
Member

moold commented Aug 3, 2020

Yes, see our paper, Hu, Jiang, et al. "NextPolish: a fast and efficient genome polishing tool for long read assembly." Bioinformatics (Oxford, England) (2019)

@binlu1981
Copy link
Author

Thanks for quickly reply. Your paper mainly focus on short reads corrections and documented that two rounds is good enough, so I plan to perform one round PacBio long-reads + two round short-reads correction using wtpos-cns, and finally use NextPolish to do two round short-reads correction. Will it work?
The assembly is ~2Gb and short-reads are about 100 Gb. My severs has ~330 Gb memory, is it enough to run NextPolish?

@moold
Copy link
Member

moold commented Aug 3, 2020

The memory is enough, NextPolish does not require much memory. I do not test wtpos-cns, for NextPolish, two round short-reads correction is enough, but if you want a more accurate assembly, you can try more iterations.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants