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

VariantFiltration

Answered
0

7 comments

  • Avatar
    Genevieve Brandt (she/her)

    Hi ThierryGrange,

    The error message that exits the command for both GATK versions is the same:

    java.lang.NumberFormatException: For input string: "0.00"

    It is most likely occurring from an issue with your command. The MQRankSum10 filter has -filter ReadPosRankSum > 3. The 3 is being read as a string. If you change it to 3.0, it should fix this error message.

    Here is more information about JEXL expressions in GATK: https://gatk.broadinstitute.org/hc/en-us/articles/360035891011-JEXL-filtering-expressions

    There have been a few changes in VariantFiltration since GATK 4.1.2.0, which might be why you are seeing a different stack trace message. See if the fix I mentioned above helps the command run, and then let me know if you would like more information as well regarding the warnings.

    Best,

    Genevieve

     

    0
    Comment actions Permalink
  • Avatar
    Thierry Grange

    Thanks for noticing the problem. It started.properly using GATK 4.1.2.0. With 4.1.9.0, it seems to proceed but it writes in the log

    WARN JexlEngine - ![0,9]: 'MQRankSum > 10.0;' undefined variable MQRankSum
    WARN JexlEngine - ![0,14]: 'ReadPosRankSum > 3.0;' undefined variable ReadPosRankSum

    at every position. I am not sure it will proceed properly to the end given this error message so I preferred to use GATK 4.1.2.0 as the log is more as I am used to.

    Thanks for your help.

    Best

    Thierry

    0
    Comment actions Permalink
  • Avatar
    Genevieve Brandt (she/her)

    Hi Thierry,

    I would recommend using the more recent version of GATK because we have made some updates to VariantFiltration since 4.1.2.0.

    The log warning messages are just warnings, indicating that the annotation does not exist at those sites. Sometimes annotations cannot be calculated at certain sites, it does not mean there is an issue.

    The MQRankSum and ReadPosRankSum are not calculated at sites where there are no heterozygous individuals. The mix of ref and alt reads are needed to calculate these values. This is most likely why you see this warning at some of your sites. It would be fine to proceed with these warnings because you also have other filters in your command.

    I found this information at our legacy forum site, but rewrote it here for other users who get these warnings in the future. See this link to find the original text at the legacy forum site: https://sites.google.com/a/broadinstitute.org/legacy-gatk-forum-discussions/2017-01-18-2016-08-11/8323-Why-do-MQRankSum-and-ReadPosRankSum-not-appear-in-some-vcf-file-entries

    Best,

    Genevieve

     

    0
    Comment actions Permalink
  • Avatar
    sanjeevksh

    Hi Genevieve,

    I also get such warnings for QD filter but only for few iterations (log provided below). I trust this is okay but still your confirmation will help.   

    Kind regards,

    Sanjeev

    12:45:31.689 INFO IntervalArgumentCollection - Processing 88663952 bp from intervals
    12:45:31.694 INFO VariantFiltration - Done initializing engine
    12:45:31.794 INFO ProgressMeter - Starting traversal
    12:45:31.795 INFO ProgressMeter - Current Locus Elapsed Minutes Variants Processed Variants/Minute
    12:45:35.801 WARN JexlEngine - ![0,2]: 'QD < 2.0;' undefined variable QD
    12:45:41.876 INFO ProgressMeter - ST4.03ch01:1606030 0.2 31000 184523.8
    12:45:52.049 INFO ProgressMeter - ST4.03ch01:3113185 0.3 66000 195526.6
    12:46:02.257 INFO ProgressMeter - ST4.03ch01:4919474 0.5 103000 202875.7
    12:46:12.265 INFO ProgressMeter - ST4.03ch01:7510765 0.7 141000 209048.9
    12:46:22.374 INFO ProgressMeter - ST4.03ch01:11128057 0.8 183000 217090.4
    12:46:32.420 INFO ProgressMeter - ST4.03ch01:14472881 1.0 223000 220701.0
    12:46:42.553 INFO ProgressMeter - ST4.03ch01:17237870 1.2 268000 227253.5
    12:46:45.314 WARN JexlEngine - ![0,2]: 'QD < 2.0;' undefined variable QD
    12:46:52.630 INFO ProgressMeter - ST4.03ch01:20794730 1.3 313000 232325.1
    12:47:02.700 INFO ProgressMeter - ST4.03ch01:23409726 1.5 357000 235630.6
    12:47:12.868 INFO ProgressMeter - ST4.03ch01:27205716 1.7 401000 238045.8
    12:47:17.241 WARN JexlEngine - ![0,2]: 'QD < 2.0;' undefined variable QD
    12:47:22.965 INFO ProgressMeter - ST4.03ch01:30944830 1.9 445000 240172.7
    12:47:33.016 INFO ProgressMeter - ST4.03ch01:33150597 2.0 488000 241542.3
    12:47:43.201 INFO ProgressMeter - ST4.03ch01:35710172 2.2 532000 242911.3
    12:47:53.319 INFO ProgressMeter - ST4.03ch01:37751639 2.4 575000 243774.9
    12:48:03.416 INFO ProgressMeter - ST4.03ch01:40991337 2.5 621000 245745.9
    12:48:13.487 INFO ProgressMeter - ST4.03ch01:44373341 2.7 664000 246394.4
    12:48:23.692 INFO ProgressMeter - ST4.03ch01:46978725 2.9 707000 246775.7
    12:48:33.868 INFO ProgressMeter - ST4.03ch01:49758934 3.0 752000 247814.1
    12:48:43.915 INFO ProgressMeter - ST4.03ch01:53352745 3.2 796000 248594.6
    12:48:54.101 INFO ProgressMeter - ST4.03ch01:55476603 3.4 839000 248832.2
    12:49:04.138 INFO ProgressMeter - ST4.03ch01:58080475 3.5 882000 249219.4
    12:49:14.222 INFO ProgressMeter - ST4.03ch01:60423711 3.7 923000 248981.7
    12:49:24.456 INFO ProgressMeter - ST4.03ch01:62452241 3.9 963000 248344.2
    12:49:31.313 WARN JexlEngine - ![0,2]: 'QD < 2.0;' undefined variable QD
    12:49:34.577 INFO ProgressMeter - ST4.03ch01:64472664 4.0 1002000 247629.6
    12:49:44.607 INFO ProgressMeter - ST4.03ch01:66229834 4.2 1040000 246823.7
    12:49:54.717 INFO ProgressMeter - ST4.03ch01:68087542 4.4 1078000 246004.5
    12:50:03.323 WARN JexlEngine - ![0,2]: 'QD < 2.0;' undefined variable QD
    12:50:04.911 INFO ProgressMeter - ST4.03ch01:70284047 4.6 1117000 245390.2
    12:50:15.109 INFO ProgressMeter - ST4.03ch01:72134705 4.7 1155000 244604.9
    12:50:15.256 WARN JexlEngine - ![0,2]: 'QD < 2.0;' undefined variable QD
    12:50:16.325 WARN JexlEngine - ![0,2]: 'QD < 2.0;' undefined variable QD
    12:50:25.111 INFO ProgressMeter - ST4.03ch01:73737193 4.9 1192000 243832.6
    12:50:35.355 INFO ProgressMeter - ST4.03ch01:75379330 5.1 1230000 243115.0
    12:50:45.480 INFO ProgressMeter - ST4.03ch01:77011718 5.2 1267000 242345.0
    12:50:55.511 INFO ProgressMeter - ST4.03ch01:78473744 5.4 1304000 241693.3
    12:50:58.613 WARN JexlEngine - ![0,2]: 'QD < 2.0;' undefined variable QD
    12:51:05.583 INFO ProgressMeter - ST4.03ch01:79954532 5.6 1341000 241051.2
    12:51:15.606 INFO ProgressMeter - ST4.03ch01:81396719 5.7 1378000 240481.0
    12:51:25.853 INFO ProgressMeter - ST4.03ch01:82841016 5.9 1416000 239960.7
    12:51:35.870 INFO ProgressMeter - ST4.03ch01:84271130 6.1 1453000 239456.2
    12:51:44.919 WARN JexlEngine - ![0,2]: 'QD < 2.0;' undefined variable QD
    12:51:45.890 INFO ProgressMeter - ST4.03ch01:85589325 6.2 1490000 238976.7
    12:51:55.899 INFO ProgressMeter - ST4.03ch01:87145632 6.4 1527000 238529.1
    12:51:56.739 WARN JexlEngine - ![0,2]: 'QD < 2.0;' undefined variable QD
    12:52:05.261 INFO ProgressMeter - ST4.03ch01:88587959 6.6 1561835 238165.7
    12:52:05.262 INFO ProgressMeter - Traversal complete. Processed 1561835 total variants in 6.6 minutes.
    12:52:05.278 INFO VariantFiltration - Shutting down engine
    [10 July 2021 12:52:05 BST] org.broadinstitute.hellbender.tools.walkers.filters.VariantFiltration done. Elapsed time: 6.59 minutes.
    Runtime.totalMemory()=778567680

    0
    Comment actions Permalink
  • Avatar
    Genevieve Brandt (she/her)

    Hi sanjeevksh,

    Each annotation is different so for your case you'll want to look at the QualByDepth documentation to make sure it might not occur at all locations: https://gatk.broadinstitute.org/hc/en-us/articles/360056968272-QualByDepth

    This annotation only is applied at sites where there is a variant allele genotyped. So, if you have a file containing some sites where there is the reference allele, then that would explain your warnings. You can double check that the QD annotation occurs where you expect by inspecting some variant sites and making sure that they have the QD annotation.

    Hope this helps!

    Genevieve

    0
    Comment actions Permalink
  • Avatar
    sanjeevksh

    Hi Genevieve,

    Thank you for your feedback, this is very helpful!

    Kind regards,

    Sanjeev 

    0
    Comment actions Permalink
  • Avatar
    Genevieve Brandt (she/her)

    No problem!

    0
    Comment actions Permalink

Please sign in to leave a comment.

Powered by Zendesk