Question: Handling replicates in Chip-seq
1
gravatar for chaudharyc61
5 months ago by
chaudharyc6110
chaudharyc6110 wrote:

Hello everyone,

I have three replicates for my ChIP-seq data, i did peak calling using MACS2, now i was thinking to get the common peaks from all the replicates which in my sense can be called as significance peaks. Now i have some questions 1. Which tool or algorithm should i use to do that and also i used "bedtools intersect" for getting overlapping peaks but the problem is after getting final bed file with common peaks i'm getting some redundancy in the file as intersection was done as per coordinates of the peaks and also for motif analysis which summit position should be used as after intersection it is very tough to understand. 2. As all the files has different summit position which summit positions should be used for motif analysis.

Thanx

chip-seq replicates • 248 views
ADD COMMENTlink modified 5 months ago by ATpoint26k • written 5 months ago by chaudharyc6110

I would recomment to use a "consenus" peak set which contains peaks found at least in two of your replicates. Here is a description of how to: https://ro-che.info/articles/2018-07-11-chip-seq-consensus

ADD REPLYlink written 4 months ago by sim.j.baum50
1
gravatar for ATpoint
5 months ago by
ATpoint26k
Germany
ATpoint26k wrote:

bedtools intersect would indeed be a reasonable choice, e.g.

bedtools intersect -a 1.narrowpeak -b 2.narrowpeak -u | bedtools intersect -a - -b 3.narrowpeak -u | cut -f1-3 > reproducible.bed

If you want summits (given that the center position of reproducible.bed does not serve as a sufficient proxy) you can merge all three replicates at more or less equal contribution (equal number of reads each) and call peaks on this. Then intersect this peak file with reproducible.bed to get summits that more or less represent the "average" in the dataset.

ADD COMMENTlink modified 5 months ago • written 5 months ago by ATpoint26k
Please log in to add an answer.

Help
Access

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