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

How to deal with extremely high mapping rate? #699

Open
oddguyeee opened this issue Aug 31, 2024 · 3 comments
Open

How to deal with extremely high mapping rate? #699

oddguyeee opened this issue Aug 31, 2024 · 3 comments

Comments

@oddguyeee
Copy link

I use hifiasm with HiFi reads to construct primary contigs, and scaffolding with 3ddna pipeline. Although I obtain a relatively complete genome, with 92.9% of busco and 95% of primary contigs, the extremely high mapping rate was found by mapping HiFi reads to final assembly. According to log file, the homozygous and heterozygous read coverage threshold were 36 and 18, respectively, as showed in k-mer plot. How can I reset the assembly parameters?
image

@kiratalreja3
Copy link

Those could be centromeric/satellite repeat regions. If so, the higher mapping rate is expected. Use tools like Flagger/Inspector to check the collapsed & duplicated regions of the assembly.

@oddguyeee
Copy link
Author

Thank you @kiratalreja3 ,

In addition, I have another question that the draft assembly from hifiasm with default parameters show a relatively low busco, 95%, How I can I improve this index?

@kiratalreja3
Copy link

If you have PacBio subreads data, run DeepConsensus for error-correction before assembly with hifiasm. Also make sure you run adapter trimming. After the assembly is done, you can use Inspector/similar tools to perform error correction. Then, after 3DDNA - consider using a gap filling tool like TGS GapCloser to fill the scaffolding gaps. These are some strategies that I use.

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