You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We merged approximately 1000 samples using two different approaches: the SVIMMER + Graphtyper combo and SURVIVOR. After noticing some discrepancies between the outputs from these two methods, we extracted a single sample to investigate the differences more closely. The following is a snippet of what we observed,
here, "_G" is for the columns of Graphtyper & "_S" is for those of SURVIVOR.
As we see from the table above, for the variants called at the same POS, Graphtyper and SURVIVOR give 2 different Genotypes completely.
Also, We did not find any read supports in these locations in the sample's bam file.
What is particularly worrisome is that Graphtyper confidently calls a homozygous genotype at these positions, whereas SURVIVOR reports the genotype as missing.
Can you please provide some insights, that might help us figure out what is happening here?
Thank you
The text was updated successfully, but these errors were encountered:
Hello @hannespetur
We merged approximately 1000 samples using two different approaches: the SVIMMER + Graphtyper combo and SURVIVOR. After noticing some discrepancies between the outputs from these two methods, we extracted a single sample to investigate the differences more closely. The following is a snippet of what we observed,
here, "_G" is for the columns of Graphtyper & "_S" is for those of SURVIVOR.
As we see from the table above, for the variants called at the same POS, Graphtyper and SURVIVOR give 2 different Genotypes completely.
Also, We did not find any read supports in these locations in the sample's bam file.
What is particularly worrisome is that Graphtyper confidently calls a homozygous genotype at these positions, whereas SURVIVOR reports the genotype as missing.
Can you please provide some insights, that might help us figure out what is happening here?
Thank you
The text was updated successfully, but these errors were encountered: