Question: How to Analyze Overlapping Peaks of ChIP-Seq Data using Perl Programming
gravatar for genomics_student
11 months ago by
genomics_student0 wrote:

I have already obtained a narrow peak file of my mouse sample using macs2. Next, I want to analyze now the overlapping peaks between my sample (per chromosome) and the mouse reference genome, specifically in the TSS. In other words, I wanna identify if which peaks lie on the mouse promoter region. I made/split into separate files per chromosome of both my experimental file and the mouse genome using Perl script. Do you have any recommendations on how to proceed, using Perl programming again, on how to identify overlapping peaks in the TSS with my sample file and the reference genome?

ADD COMMENTlink modified 11 months ago • written 11 months ago by genomics_student0
gravatar for colindaven
11 months ago by
Hannover Medical School
colindaven2.3k wrote:

If you have a TSS or alternative epigenomics annotation file of interest (eg from modENCODE) in BED format you can use Bedtools or Bedops to intersect overlapping peaks.

ADD COMMENTlink written 11 months ago by colindaven2.3k
gravatar for Alex Reynolds
11 months ago by
Alex Reynolds30k
Seattle, WA USA
Alex Reynolds30k wrote:

You could get TSS from gene annotations specific to your reference genome, e.g.:

A: Table browser +/- 2Kb of TSS export

Once you have that, you can find set intersections via something like:

$ bedops --element-of 1 peaks.bed tss.bed > peaks_that_overlap_tss.bed

If you'd rather get a calculation of which peaks overlap which TSS, specifically:

$ bedmap --echo --echo-map tss.bed peaks.bed > tss_with_associated_peaks.bed

The difference between bedops and bedmap, very generally, is that bedops does set and interval operations (intersect, difference, etc.), while bedmap does associations between genomic elements in sets ("mapping").

ADD COMMENTlink written 11 months ago by Alex Reynolds30k
Please log in to add an answer.


Use of this site constitutes acceptance of our User Agreement and Privacy Policy.
Powered by Biostar version 2.3.0
Traffic: 1181 users visited in the last hour