average coverage, chip-seq
2
0
Entering edit mode
6.5 years ago

Hi

I need to determine average coverage in ChiP-seq peaks. I tried to use bedtools multicov with sorted bam-file with mapped reads and bed-file with peaks. Default minimum overlap of a read and a peak is 1 bp. What minimum overlap (in percent) should I use?

coverage ChIP-Seq • 3.7k views
ADD COMMENT
1
Entering edit mode
6.5 years ago
Ryan Dale 4.9k

Depending on your peak caller, you may have metrics like total number of reads or peak summit height that you could summarize directly from the BED file of called peaks. These numbers are likely to be more accurate since they are usually calculated after shifting the reads by the average fragment size (see Fig 1 in the SPP paper if this is unclear) and may already be normalized to input and library size.

That said, 1-bp overlap seems to be the most commonly used for interval overlaps (in the absence of any biological arguments saying otherwise).

ADD COMMENT
0
Entering edit mode

Thanks for the explanation. I have one more question, if I have narrowPeak file from ENCODE (SPP might be used to call peaks), how can I get the tag density or binding affinity in the peak region?

ADD REPLY
0
Entering edit mode

The format description is here: http://genome.ucsc.edu/FAQ/FAQformat.html#format12

So field 7 gets you the average enrichment over the peak while field 9 gives the FDR.

ADD REPLY
0
Entering edit mode
6.5 years ago

Honestly, I haven't done it for ChIP-seq but did it for WGS CNVs. There is a tool called CNV-seq which takes 2 columns of your SAM file, determines the window size and bins the reads across the genome. Even though it is for CNVs I think you can still use it to look at the average coverage as well.

There is also another software CHANCE which would give you an estimation of the percentage of the genome enriched for your signal if you feed it control and treatment BAM/SAM files.

Hope this helps!

ADD COMMENT

Login before adding your answer.

Traffic: 1349 users visited in the last hour
Help About
FAQ
Access RSS
API
Stats

Use of this site constitutes acceptance of our User Agreement and Privacy Policy.

Powered by the version 2.3.6