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

The process of polishing causes a significant decrease in genome size. #130

Open
xujialupaoli opened this issue Apr 11, 2024 · 8 comments
Open

Comments

@xujialupaoli
Copy link

Hello, thank you for providing such a useful assembly software. I have a question and would like your help.
After nextpolish polished my genome file, my genome size was reduced a lot.
Why does polishing cause a significant decrease in genome size?
In the picture, I sorted out the genome size assembled by nextdenovo, the genome size after purge_dups, and the genome size after nextpolish.
image

@moold
Copy link
Member

moold commented Apr 11, 2024

This may be caused by nextpolish not finishing running.,Could you paste its running log to here?

@xujialupaoli
Copy link
Author

Thank you very much for your reply!
first_polish_log.txt
second_polish_log.txt
I first used quality-filtered ultralong ONT reads and common ONT reads to polish the assembly for three rounds, setting ‘task = best rewrite = yes rerun = 3’ in the parameter config file. The assembly polished by ONT data was then further polished for three rounds with PacBio HiFi reads,setting‘task = best rewrite = yes rerun = 3’ in the parameter config file.

@moold
Copy link
Member

moold commented Apr 11, 2024

It is better to use NextPolish2 to polish your genome (assembly polished by ONT data) with HiFi reads.

@xujialupaoli
Copy link
Author

Thanks for your reply and help!
The genome assembly I assembled through hifiasm using HiFi data is not very good, so I am currently using the results assembled by Nextdenovo, which is better. My data is a bit special, and there should be more errors in the results I assembled using nextdovo.
I have carefully learned about nextpolish2, which you developed. It is suitable for polishing high-quality assembly . Is nextpolish more suitable for my situation?
In addition, I hope to use my HiFi sequencing data for polishing. Because it is difficult to use HiFI data for assembly, I hope to use my hifi data in the polishing process.
Finally,why does polishing result in a significant decrease in genome size?

@moold
Copy link
Member

moold commented Apr 12, 2024

  1. nextpolish2 is suitable for your assembly, so you can have a try.
  2. There may be an unknown bug, but it cannot be fixed unless I can reproduce this bug.

@xujialupaoli
Copy link
Author

Thank you for your reply and help!
I will try using Nextpolish2 to see if it resolves the issue.
Could it be that my HiFi data is somewhat unique, leading to some unknown issues when applying it to Nextpolish? Because I didn't encounter any significant reduction in genome size when processing with ONT data.
image

@moold
Copy link
Member

moold commented Apr 12, 2024

I'm not sure, unless I can reproduce the error.

@xujialupaoli
Copy link
Author

I performed polishing through nextpolish2 and found that it still resulted in a significant reduction in the genome, by about 30M.
Do you know what causes this situation?
Very much looking forward to your reply
image

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