Brian W Davis

See attached log [F1_hfsmtrio.log](https://github.com/chhylp123/hifiasm/files/7313687/F1_hfsmtrio.log)

Here are the yak trioeval results for both haplotypes [yak_trioeval.log](https://github.com/chhylp123/hifiasm/files/7313840/yak_trioeval.log) .

They should be. Could there be another cause?

Sure thing. This is for a canu2.2 assembly with prior-binned reads. Worse contiguity, but even haplotype lengths. [yak_trioeval_2.log](https://github.com/chhylp123/hifiasm/files/7314042/yak_trioeval_2.log)

Let me investigate. I sincerely appreciate your time. Keep this open till I nail down the parental information.

I tried using the (very useful) Hi-C haplotype splitting approach, and it worked very well, so there must be an issue with the parents. Thank you for your help In...

For clarity, I realize that hap1 and hap2 can potentially be mixed parentals chromosome to chromosome. However, due to the divergence between my parent species, the correct haplotype should be...

Has this been resolved? I need to label each cell by barcode in a Seurat object using the cluster IDs generated by souporcell.

> For me it was an empty mappability line in the wig generated by HMMcopy

I confirmed that I receive this error, even when comparing a tumor-normal pair Correcting Tumour Error in (function (classes, fdef, mtable) : unable to find an inherited method for function...