<p>Assuming a diploid genome, usually, we aim to build a monoploid reference, representing a single haplotype.</p>
<p>Practically speaking, we need to include only one of the two k-mers that are representing heterozygous sites, however, we would desire all the homozygous k-mers to be included exactly once.</p>
<p>Looking at your plot, I would guess 1n coverage is somewhere around 18x, and 2n about 36x. If that's right, your plot is suggesting that your assembly contains lots of uncollapsed haplotypes, which is quite understandable given very high heterozygosity you estimated with genomescope. This is also supported by many homozygous k-mers are there twice (the blue bump). These are probably regions in between heterozygous sites, or flanking them.</p>
<p>Anyway, I would recommend something like <a href="https://bmcbioinformatics.biomedcentral.com/articles/10.1186/s12859-018-2485-7" rel="nofollow noreferrer">purge haplotigs</a> to collapse haplotypes into single monoploid reference and redo the plot. The blue bump should disappear and the black and red distributions should have about the same height around 18x, while nearly all the 36x k-mers should be red (once).</p>
<p>Also, if the interpretation of the plot still would not be clear, you can check this <a href="https://youtu.be/XJW-mgmkgk0?list=PL-_gg7O4EMWbFLTdqr501tjNJ1xq43BqA&amp;t=764" rel="nofollow noreferrer">part of a lecture by Lucía Campos-Dominguez</a> on the topic (it's a different software called KAT she talks about, but it is using the same principle as Mercury).</p>

CC BY-SA 4.0
2021-12-14T23:26:53.027Z
Hi Kamil, thank you for your informative reply. You are exactly right about the 1n = 18, although not sure how you get that so accurate ;-). I do have another Merqury kmer plot with a very low blue peak near the 4n location rather than the 2n location, while the red peak at the same 2n. And this happens for another species genome assembly. Is that normal? Because that makes the blue peak at 2n look weired.
Life_Searching_Steps
CC BY-SA 4.0
2021-12-15T04:26:09.313Z
I will post another question. Thank you!
Life_Searching_Steps
CC BY-SA 4.0
2021-12-07T18:18:47.163Z
2021-12-07T18:18:47.163Z
Kamil S Jaron
<p>The attached figure is generated based on Illumina reads from multiple individuals compared to genome assembly. Looks like there are a lot of kmers are reads only (grey colored). Also, a blue peak (2x kmers), does it represents high heterozygosity? GenomeScope gives 1.5% of heterozygosity result. But it seems the blue peak normally should be near the 70x on the x-axis<a href="https://i.sstatic.net/IpLZN.png" rel="nofollow noreferrer"><img src="https://i.sstatic.net/IpLZN.png" alt="enter image description here" /></a>. Thanks.</p>

<genome><assembly><illumina><k-mer>
Understand this Kmer plot from Merqury?
# Understand this Kmer plot from Merqury?

(Asked by: username_0 on 2021-12-07)

The attached figure is generated based on Illumina reads from multiple individuals compared to genome assembly. Looks like there are a lot of kmers are reads only (grey colored). Also, a blue peak (2x kmers), does it represents high heterozygosity? GenomeScope gives 1.5% of heterozygosity result. But it seems the blue peak normally should be near the 70x on the x-axis[![enter image description here](https://i.sstatic.net/IpLZN.png)](https://i.sstatic.net/IpLZN.png). Thanks.

**Tags:** genome, assembly, illumina, k-mer

---

## 1 answers

### Answer by username_1 on 2021-12-07. Score: 1 | Accepted answer

Assuming a diploid genome, usually, we aim to build a monoploid reference, representing a single haplotype.

Practically speaking, we need to include only one of the two k-mers that are representing heterozygous sites, however, we would desire all the homozygous k-mers to be included exactly once.

Looking at your plot, I would guess 1n coverage is somewhere around 18x, and 2n about 36x. If that's right, your plot is suggesting that your assembly contains lots of uncollapsed haplotypes, which is quite understandable given very high heterozygosity you estimated with genomescope. This is also supported by many homozygous k-mers are there twice (the blue bump). These are probably regions in between heterozygous sites, or flanking them.

Anyway, I would recommend something like [purge haplotigs](https://bmcbioinformatics.biomedcentral.com/articles/10.1186/s12859-018-2485-7) to collapse haplotypes into single monoploid reference and redo the plot. The blue bump should disappear and the black and red distributions should have about the same height around 18x, while nearly all the 36x k-mers should be red (once).

Also, if the interpretation of the plot still would not be clear, you can check this [part of a lecture by Lucía Campos-Dominguez](https://youtu.be/XJW-mgmkgk0?list=PL-_gg7O4EMWbFLTdqr501tjNJ1xq43BqA&t=764) on the topic (it's a different software called KAT she talks about, but it is using the same principle as Mercury).

> **Comments:**
> **username_0**: Hi Kamil, thank you for your informative reply. You are exactly right about the 1n = 18, although not sure how you get that so accurate ;-). I do have another Merqury kmer plot with a very low blue peak near the 4n location rather than the 2n location, while the red peak at the same 2n. And this happens for another species genome assembly. Is that normal? Because that makes the blue peak at 2n look weired.  
> **username_0**: I will post another question. Thank you!  

---

