I have a human sample from HPRC (HG01099) where it seems there is incorrect alignment between haplotypes. Here is the region post-resolution:
You can see utig4-1010 is connected to a paternal and maternal haplotype. There is another region (with node utig4-103[01]) where two maternal nodes merge into a single maternal node. Going back to the HiFi-only graph this is the structure in the area:
I tried to label the HiFi nodes w/their utig4 assignments. You can see that there is a resolution here which would connected paternal to paternal and both maternal to their correct counterpart. However, one of the maternal paths is being broken and instead is connected to the paternal path through utig1-46519. GraphAligner has strong support for the path from utig1-44125 to utig1-36366 (24 reads) vs either utig1-42180 (2) or utig1-42179 (0). However, re-mapping the same reads w/winnowmap gives no support for this path. All the reads aligned from utig1-44125 to utig1-36366 instead align to utig1-46520 and utig1-36366. The hapmers are a bit noisy since these are ONT reads but when I take strongly paternal reads, they are mapped by graphaligner to this path (6 reads) and not by winnowmap, implying they are likely from the paternal haplotype. The results are the same with GraphAligner w/the diploid heuristic as well, the two GraphAligner commands I ran were:
I have a human sample from HPRC (HG01099) where it seems there is incorrect alignment between haplotypes. Here is the region post-resolution: You can see utig4-1010 is connected to a paternal and maternal haplotype. There is another region (with node utig4-103[01]) where two maternal nodes merge into a single maternal node. Going back to the HiFi-only graph this is the structure in the area:
I tried to label the HiFi nodes w/their utig4 assignments. You can see that there is a resolution here which would connected paternal to paternal and both maternal to their correct counterpart. However, one of the maternal paths is being broken and instead is connected to the paternal path through utig1-46519. GraphAligner has strong support for the path from utig1-44125 to utig1-36366 (24 reads) vs either utig1-42180 (2) or utig1-42179 (0). However, re-mapping the same reads w/winnowmap gives no support for this path. All the reads aligned from utig1-44125 to utig1-36366 instead align to utig1-46520 and utig1-36366. The hapmers are a bit noisy since these are ONT reads but when I take strongly paternal reads, they are mapped by graphaligner to this path (6 reads) and not by winnowmap, implying they are likely from the paternal haplotype. The results are the same with GraphAligner w/the diploid heuristic as well, the two GraphAligner commands I ran were:
and
The asm, relevant reads, and alignments are on the globus share under graphaligner.