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

evaluation for QV in haplotypes #140

Open
DayTimeMouse opened this issue Oct 2, 2024 · 3 comments
Open

evaluation for QV in haplotypes #140

DayTimeMouse opened this issue Oct 2, 2024 · 3 comments

Comments

@DayTimeMouse
Copy link

Hi,

Thank you for developing this nice tool.

I have obtained hap1.fa and hap2.fa using hifiasm(HiFi +HiC reads). Next, I would like to evaluate the QV and completeness of each haplotype.

However, I am uncertain about which reads to use to build the meryl databases. Should I use haplotype-specific reads or all HiFi reads?

When I use all HiFi reads to assess the QV and completeness of each haplotype, the QV is 48, and the completeness is 90.26%. In contrast, when I use haplotype-specific reads, the QV is 36, and the completeness is 99.40%.

Best regards.

@arangrhie
Copy link
Contributor

arangrhie commented Oct 10, 2024

Hi @DayTimeMouse,

Use all HiFi reads.
Completeness is measured based on num. kmers found in the assembly / found in the reads. That means, if you are using haplotype-specific reads, your denominator will be only half the genome.

Best,
Arang

@DayTimeMouse
Copy link
Author

Hi @arang,

But I am still confused about using all HiFi reads to evaluate QV and completeness. Because I want to evaluate each haplotype not primary genome.

@arangrhie
Copy link
Contributor

arangrhie commented Oct 25, 2024

Run merqury with the two fasta files as input - such as merqury.sh read.meryl hap1.fa hap2.fa out.
The QV file will contain QV for each haplotype and all together (both haplotypes).

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