Bug Bulletin: we have identified a bug that affects indexing when producing gzipped VCFs. This will be fixed in the upcoming 3.2 release; in the meantime you need to reindex gzipped VCFs using Tabix.

(BP2.2) Calling Variants with UnifiedGenotyper [RETIRED]

Geraldine_VdAuweraGeraldine_VdAuwera Posts: 5,235Administrator, GSA Member admin

This article is now obsolete as UnifiedGenotyper is no longer part of our recommended Best Practices workflow. It should only be used for calling variants on non-diploid organisms. We are working on enabling HaplotypeCaller to handle non-diploid organisms, so hopefully it will replace UG in this aspect as well in the near future.

This article is part of the Best Practices workflow documentation. See http://www.broadinstitute.org/gatk/guide/best-practices for the full workflow.

Although we generally recommend using the HaplotypeCaller for calling variants, in some cases it is not possible to do so, as explained in the FAQs. In those cases (i.e. when you're processing a high number of samples together, working with non-diploid organisms or with pooled samples) you should use the UnifiedGenotyper instead.

The Unified Genotyper calls SNPs and indels separately by considering each variant locus independently. The model it uses to do so has been generalized to work with data from organisms of any ploidy.

Post edited by Geraldine_VdAuwera on

Geraldine Van der Auwera, PhD

This discussion has been closed.