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

Difference of AT/GC dropout metric explanation between commands

0

4 comments

  • Avatar
    Gökalp Çelik

    Hi JYoung Lee

    Those are 2 separate metrics (There are no distinct tools with those names.) that report AT_DROPOUT and GC_DROPOUT for different purposes. 

    HsMetrics and TargettedPcrMetrics report these values as how each sample is biased their AT and GC rich regions are in terms of coverage and readcount. 

    GcBiasSummaryMetrics report these values as how each lane in an sequencer is different in terms of AT and GC content within. 

    Using similar naming is what is really causing the confusion but don't worry. They are for 2 different purposes and yet are not comparable. 

    I hope this helps. 

    0
    Comment actions Permalink
  • Avatar
    JYoung Lee

    Thank you for your explanation, Gökalp Çelik.

    Then would it be correct to understand them as follows?
    1)
    GC/AT Dropouts for GcBiasSummaryMetrics measure depletion of reads in high/low GC regions.

    2-1)
    GC/AT Dropouts for HsMetric and TargetedPcrMetrics measure how narrow the covered region( with aligned read >1) is, compared to the number of reads aligned in that region.

    2-2)
    and "a" means the following

    a : proportion of regions that are of certain GC content and covered by at least 1 read relative to total target territory

    0
    Comment actions Permalink
  • Avatar
    Gökalp Çelik

    For 1) this measure is per lane of a flowcell. 

    For 2) Exactly. 

     

    0
    Comment actions Permalink
  • Avatar
    JYoung Lee

    Thank you for your clarification!

    0
    Comment actions Permalink

Please sign in to leave a comment.

Powered by Zendesk