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
Recently, I have tried your "Germline SV calling" pipeline by Delly on human NGS data.
Step 1: Using "delly call" to generate the individual-separated BCF files;
Step 2: Using "delly merge" to generate a unified site list;
Step 3: Using "delly call" again to regenerate the new individual-separated BCF files;
Step 4: Using "bcftools merge" to merge all the new individual-separated BCF files together;
Step 5: Using "delly filter" to filter out bad SVs.
According to the definition of VCF file (http://samtools.github.io/hts-specs/VCFv4.2.pdf), it's easily to understand that "./." stands for "missing allele" , "0/0" stands for "homo-reference allele", "0/1" stands for "heterozygote" and "1/1" stands for "homo-alternative allele"
And then my confusions are:
(1) During Step1, if a SV was coded "./." in one individual-separated BCF file, is the "./." stands for "This SV happened in this individual, but we just don't know its genotype" or "This SV didn't happen in this individual"? (In fact, for many other SV Callers who didn't generate SV genotype, it seems they just use include or exclude SV in the BCF file to tell us weather one individual has one SV or not.)
(2) During Step3+Step4, when we try to merge all the individual-separated BCF file together based on a unified site list, many individuals must don't have some SVs instead of genotype missing, so how did you code those locus? (Did you just remove those SVs away just because some individual don't have them or you just code those locus as "./." ?)
Looking for your response!
Best regards,
Leilei
The text was updated successfully, but these errors were encountered:
The main reason to merge and re-genotype is to get accurate genotypes across the same loci in all samples. This is very powerful for filtering germline SVs and remove redundant SV calls, especially if you have several dozens or hundreds of samples. ./. means that the data is insufficient to make a confident genotype call whereas 0/0 means the data supports hom. reference.
Hi Tobias,
Recently, I have tried your "Germline SV calling" pipeline by Delly on human NGS data.
Step 1: Using "delly call" to generate the individual-separated BCF files;
Step 2: Using "delly merge" to generate a unified site list;
Step 3: Using "delly call" again to regenerate the new individual-separated BCF files;
Step 4: Using "bcftools merge" to merge all the new individual-separated BCF files together;
Step 5: Using "delly filter" to filter out bad SVs.
According to the definition of VCF file (http://samtools.github.io/hts-specs/VCFv4.2.pdf), it's easily to understand that "./." stands for "missing allele" , "0/0" stands for "homo-reference allele", "0/1" stands for "heterozygote" and "1/1" stands for "homo-alternative allele"
And then my confusions are:
(1) During Step1, if a SV was coded "./." in one individual-separated BCF file, is the "./." stands for "This SV happened in this individual, but we just don't know its genotype" or "This SV didn't happen in this individual"? (In fact, for many other SV Callers who didn't generate SV genotype, it seems they just use include or exclude SV in the BCF file to tell us weather one individual has one SV or not.)
(2) During Step3+Step4, when we try to merge all the individual-separated BCF file together based on a unified site list, many individuals must don't have some SVs instead of genotype missing, so how did you code those locus? (Did you just remove those SVs away just because some individual don't have them or you just code those locus as "./." ?)
Looking for your response!
Best regards,
Leilei
The text was updated successfully, but these errors were encountered: