Heads up:
We’re moving the GATK website, docs and forum to a new platform. Read the full story and breakdown of key changes on this blog.
If you happen to see a question you know the answer to, please do chime in and help your fellow community members. We encourage our fourm members to be more involved, jump in and help out your fellow researchers with their questions. GATK forum is a community forum and helping each other with using GATK tools and research is the cornerstone of our success as a genomics research community.We appreciate your help!

Test-drive the GATK tools and Best Practices pipelines on Terra

Check out this blog post to learn how you can get started with GATK and try out the pipelines in preconfigured workspaces (with a user-friendly interface!) without having to install anything.
We will be out of the office for a Broad Institute event from Dec 10th to Dec 11th 2019. We will be back to monitor the GATK forum on Dec 12th 2019. In the meantime we encourage you to help out other community members with their queries.
Thank you for your patience!

Unified Genotyper: Maximum sensitivity

I'm seeing Mendelian errors in small but significant proportion of my unified genotyper calls. For many instances the SNP is called incorrectly as a homozygote even though there are some reads of the second allele. How can I set unified genotyper to be more sensitive ?

Best Answer


  • Geraldine_VdAuweraGeraldine_VdAuwera Cambridge, MAMember, Administrator, Broadie admin

    The best thing you can do is switch to the HaplotypeCaller, unless your organism is not diploid.

  • BlueBlue Member

    I will do, as soon as I've uninstalled java 1.8, or there's space on the cluster. I tried HaplotypeCaller a while ago: it seems to take two weeks for ten samples, but I guess its sensitivity is better than UnifiedGenotyper. I'm still wondering if sensitivity of either caller can be altered, as a command-line argument so that even unlikely SNPs are called? I thought it might be to do with this HC argument --bandPassSigma (The sigma of the band pass filter Gaussian kernel; if not provided defaults to Walker annotated default).

  • Geraldine_VdAuweraGeraldine_VdAuwera Cambridge, MAMember, Administrator, Broadie admin

    The HC was very slow in previous versions, and this was definitely a problem for multisample calling. In the latest version, however, we have a new workflow that consists of single-sample calling with HC in GVCF mode followed by multisample joint genotyping. This gives you the same or better sensitivity as multisample calling but is much faster and can be done incrementally for projects with many samples that become available one at a time or in batches.

    There are various arguments that can tweak sensitivity somewhat, but with the new version and new workflow you shouldn't need to. Are you looking for low-frequency variants?

  • BlueBlue Member

    Thanks for the response. I'm not specifically looking for low-frequency variants.

    I'd like to increase the sensitivity of SNP-calling because:

    1) There are many homozygous Mendelian errors that would be corrected if the presence of a second allele was acknowledged by the calling algorithm.

    2) The count of unique SNPs is low compared to SNPs that occur in two or three samples, or in similar population samples.

    What are the 'various arguments' that maximise sensitivity of HaplotypeCaller ?

Sign In or Register to comment.