Open carsonhh opened 1 year ago
Same issue here...
Any activity here? The issue on the deepvariant side is closed since this is a GLnexus issue after all. The problem is that it creates issues in downstream analysis. Since ./. (no data) is very different from 0/0 (reference genotype). Software that understands pedigrees and inheritance patterns will see 0/0 as evidence against an an expected inheritance pattern which can cause disease gene candidates to be suppressed in a familial analysis.
When joint calling gVCF files generated by DeepVariant, GLnexus will assign a genotype of 0/0 and a depth (DP) of 0. However without any supporting reads, the genotype should be './.' or nocall?