The current GATK version is 3.7-0
Examples: Monday, today, last week, Mar 26, 3/26/04

#### Howdy, Stranger!

It looks like you're new here. If you want to get involved, click one of these buttons!

You can opt in to receive email notifications, for example when your questions get answered or when there are new announcements, by following the instructions given here.

#### ☞ Got a problem?

1. Search using the upper-right search box, e.g. using the error message.
3. Include tool and Java versions.
4. Tell us whether you are following GATK Best Practices.
5. Include relevant details, e.g. platform, DNA- or RNA-Seq, WES (+capture kit) or WGS (PCR-free or PCR+), paired- or single-end, read length, expected average coverage, somatic data, etc.
6. For tool errors, include the error stacktrace as well as the exact command.
7. For format issues, include the result of running ValidateSamFile for BAMs or ValidateVariants for VCFs.
8. For weird results, include an illustrative example, e.g. attach IGV screenshots according to Article#5484.
9. For a seeming variant that is uncalled, include results of following Article#1235.

#### ☞ Formatting tip!

Wrap blocks of code, error messages and BAM/VCF snippets--especially content with hashes (#)--with lines with three backticks (  ) each to make a code block as demonstrated here.

**GATK4-BETA.2** is here. That's TWO, as in the second beta release. Be sure to read about the known issues before test driving. See Article#9881 to start and https://github.com/broadinstitute/gatk/blob/master/README.md for details.

# BaseCoverageDistribution

Member
edited June 2013

In the output grp file,

#:GATKReport.v1.1:1
#:GATKTable:3:880:%s:%s:%s:;
#:GATKTable:BaseCoverageDistribution:A simplified GATK table report
Coverage  Count    Filtered
0  2859049   2932784
1   856997    837791
2   288587    276253
3    95618     91703


what's the meaning of the three columns?

Thanks,

Tagged:

I'll have the tool author (@Carneiro) confirm, but as I recall:

1. The first column, Coverage, is the depth of coverage corresponding to the bin (ie the first line is the set of loci that are covered by 0 reads, the second is the set covered by 1 read, etc);

2. The second, Count, is the number of loci in the bin (without any filtering);

3. The third, Filtered, is the number of loci in the bin after applying quality filtering to exclude bad reads.

• Member
edited June 2013

hi, Geraldine,
Thanks for the quick response! Two questions:

1. if the coverage is 2, can I interpret it as the so-called 2x coverage?

2. By your explanation, the Count should > Filtered; why Count < Filtered at coverage 0?

• Member

Well, I found Count < Filtered at some other coverages as well. For example:
 23 7910 8119`

1. The 2x-style expression is a convention to express the overall coverage of a dataset, so I'm not sure it's appropriate to use it in this context. If you do use it, make sure to communicate clearly what you mean, to avoid any unfortunate misunderstandings.

2. Hmm, I may have misremembered. Based on the tech doc it looks like it might be the count of filtered reads (not including good reads). I'll ask @Carneiro to confirm, but I reckon that makes sense. But if so, there's an awful lot of low-quality reads in your data, at least based on the low-value bins you posted...

• Member

Thanks so much, Geraldine! Please confirm!

• Member

Hi Geraldine. Did you get a chance to confirm @blueskypy 's second question - whether the filtered column includes the good reads? I just ran this tool and for most rows, the values for the 3rd column are higher.