Genome Analysis Toolkit

Variant Discovery in High-Throughput Sequencing Data

GATK process banner

Need Help?

Search our documentation

Community Forum

Hi, How can we help?

Developed in the Data Sciences Platform at the Broad Institute, the toolkit offers a wide variety of tools with a primary focus on variant discovery and genotyping. Its powerful processing engine and high-performance computing features make it capable of taking on projects of any size. Learn more

Values for QD annotation not detected for ANY training variant in the input callset. VariantAnnotator may be used to add these annotations.

Answered
0

7 comments

  • Avatar
    Genevieve Brandt (she/her)

    Hi tahi,

    One of the annotations you are using to build your VariantRecalibrator model is QD (-an QD) but you have not added QD to your VCF file. 

    You can add annotations to your VCF file with the gatk tool VariantAnnotator. The tool documentation page is here: https://gatk.broadinstitute.org/hc/en-us/articles/4418054223003-VariantAnnotator

    Please let me know if you have any further questions.

    Best,

    Genevieve

    0
    Comment actions Permalink
  • Avatar
    Wondessen Ayalew

    Dear Dr, Genevieve Brandt,

    I got the same problem form GATK4.3.0. Based on your suggestion, I run "VariantRecalibrator model" and the problem still persists. Is there any other way to fix such problem? or Does hard filtering avoid such issue? Thank you!

     Here is the error message

    Values for QD annotation not detected for ANY training variant in the input callset. VariantAnnotator may be used to add these annotations.

    0
    Comment actions Permalink
  • Avatar
    Laura Gauthier

    Wondessen Ayalew,

    GenotypeGVCFs generates the QD annotation by default.  What command did you use to generate the VCF you're supplying as input to VariantRecalibrator?  If you've run GenotypeGVCFs, but excluded QD, you can calculate it with VariantAnnotator.

    0
    Comment actions Permalink
  • Avatar
    Emila Mańko

    Hi all,

    I am getting the same error after using the VariantRecalibrator. I have checked training set and my input VCF and both have QD present in the annotations. Do you have any idea what could cause it and how to solve it?

    Thanks in advance,

    Emilia

    My log file:

    Using GATK jar gatk4-4.1.4.1-1/gatk-package-4.1.4.1-local.jar
    Running:
        java -Dsamjdk.use_async_io_read_samtools=false -Dsamjdk.use_async_io_write_samtools=true -Dsamjdk.use_async_io_write_tribble=false -Dsamjdk.compression_level=2 -jar gatk4-4.1.4.1-1/gatk-package-4.1.4.1-local.jar VariantRecalibrator -R <ref> -V <vcf> --resource:pf_crosses,known=false,training=true,truth=true,prior=15.0 <training_vcf> -an QD -an FS -an SOR -an DP --max-gaussians 8 --mq-cap-for-logit-jitter-transform 70 -mode SNP -O <ouput>.snps.recal --tranches-file Pv4_2195_merge_2023_08_02.snps.tranches --rscript-file <output>.snps.plots.R
    12:52:14.589 INFO  NativeLibraryLoader - Loading libgkl_compression.so from jar:file: gatk4-4.1.4.1-1/gatk-package-4.1.4.1-local.jar!/com/intel/gkl/native/libgkl_compression.so
    Aug 03, 2023 12:52:14 PM shaded.cloud_nio.com.google.auth.oauth2.ComputeEngineCredentials runningOnComputeEngine
    INFO: Failed to detect whether we are running on Google Compute Engine.
    12:52:14.749 INFO  VariantRecalibrator - ------------------------------------------------------------
    12:52:14.749 INFO  VariantRecalibrator - The Genome Analysis Toolkit (GATK) v4.1.4.1
    12:52:14.749 INFO  VariantRecalibrator - For support and documentation go to https://software.broadinstitute.org/gatk/
    12:52:14.749 INFO  VariantRecalibrator - Executing as gabbie@s9 on Linux v5.4.0-153-generic amd64
    12:52:14.749 INFO  VariantRecalibrator - Java runtime: OpenJDK 64-Bit Server VM v1.8.0_332-b09
    12:52:14.750 INFO  VariantRecalibrator - Start Date/Time: August 3, 2023 12:52:14 PM UTC
    12:52:14.750 INFO  VariantRecalibrator - ------------------------------------------------------------
    12:52:14.750 INFO  VariantRecalibrator - ------------------------------------------------------------
    12:52:14.750 INFO  VariantRecalibrator - HTSJDK Version: 2.21.0
    12:52:14.750 INFO  VariantRecalibrator - Picard Version: 2.21.2
    12:52:14.750 INFO  VariantRecalibrator - HTSJDK Defaults.COMPRESSION_LEVEL : 2
    12:52:14.750 INFO  VariantRecalibrator - HTSJDK Defaults.USE_ASYNC_IO_READ_FOR_SAMTOOLS : false
    12:52:14.750 INFO  VariantRecalibrator - HTSJDK Defaults.USE_ASYNC_IO_WRITE_FOR_SAMTOOLS : true
    12:52:14.750 INFO  VariantRecalibrator - HTSJDK Defaults.USE_ASYNC_IO_WRITE_FOR_TRIBBLE : false
    12:52:14.751 INFO  VariantRecalibrator - Deflater: IntelDeflater
    12:52:14.751 INFO  VariantRecalibrator - Inflater: IntelInflater
    12:52:14.751 INFO  VariantRecalibrator - GCS max retries/reopens: 20
    12:52:14.751 INFO  VariantRecalibrator - Requester pays: disabled
    12:52:14.751 INFO  VariantRecalibrator - Initializing engine
    12:52:14.991 INFO  FeatureManager - Using codec VCFCodec to read file file://<training_vcf>
    12:52:15.017 INFO  FeatureManager - Using codec VCFCodec to read file file://<vcf>
    12:52:15.052 INFO  VariantRecalibrator - Done initializing engine
    12:52:15.054 INFO  TrainingSet - Found pf_crosses track:        Known = false   Training = true         Truth = true    Prior = Q15.0
    12:52:15.061 WARN  GATKVariantContextUtils - Can't determine output variant file format from output file extension "recal". Defaulting to VCF.
    12:52:15.079 INFO  ProgressMeter - Starting traversal
    12:52:15.079 INFO  ProgressMeter -        Current Locus  Elapsed Minutes    Variants Processed  Variants/Minute
    12:52:15.084 INFO  ProgressMeter -             unmapped              0.0                     0              0.0
    12:52:15.084 INFO  ProgressMeter - Traversal complete. Processed 0 total variants in 0.0 minutes.
    12:52:15.088 INFO  VariantRecalibrator - Shutting down engine
    [August 3, 2023 12:52:15 PM UTC] org.broadinstitute.hellbender.tools.walkers.vqsr.VariantRecalibrator done. Elapsed time: 0.01 minutes.
    Runtime.totalMemory()=2152202240
    ***********************************************************************

     

    A USER ERROR has occurred: Bad input: Values for QD annotation not detected for ANY training variant in the input callset. VariantAnnotator may be used to add these annotations.

     

    ***********************************************************************
    Set the system property GATK_STACKTRACE_ON_USER_EXCEPTION (--java-options '-DGATK_STACKTRACE_ON_USER_EXCEPTION=true') to print the stack trace.

    0
    Comment actions Permalink
  • Avatar
    Laura Gauthier

    Hi Emila Mańko,

    It's suspicious to me that it says zero variants processed and I have a theory.  Can you confirm that there is at least one variant in your training VCF that is also in your input VCF?  You could do that with GATK's SelectVariants supplying one with -V and one with -conc.

    -Laura

    0
    Comment actions Permalink
  • Avatar
    Emila Mańko

    Hi Laura,

    Thank you for such quick response and sorry for delay on my side. I can confirm that we have quite good overlap between training set and input VCF confirmed both with GATK SelectVariants and bcftools.

    We tried to manipulate around the VariantRecalibrator parameters and decreasing max-gaussians argument seems to bypass the error which probably is not ideal solution. Although from the error itself it seemed that something might be wrong with the input VCF itself... Any ideas what else we should be looking into to forsee this type of errors in the future?

    Thank you!

    Emilia

    0
    Comment actions Permalink
  • Avatar
    Laura Gauthier

    Hi Emila Mańko

    I've seen a decrease in the max gaussians argument help when the error is no negative training data, but that's not what your log shows.  It's going to be hard to further debug without seeing any of the data.  Would you be able to share a small portion of the VCF so I could try to reproduce the error?

    -Laura

    0
    Comment actions Permalink

Please sign in to leave a comment.

Powered by Zendesk