Chip-Seq Cancer Cell Lines
2
1
Entering edit mode
5.3 years ago

Hi We have done Chip-seq H3k27m3 data on cancer cell lines resistant to cisplatin. We have chips-eq of parent (non-resistant) cell lines with 3 replicates and 3 input replicates. Furthermore, we have chip-seq of resistant cell lines with 3 replicates and 3 input replicates.

Q1: After Alignment step, should I call the peaks separate for each input and experiment replicate and then i should find the common peaks between all the replicates of input and experiment?
Q2: Ultimately i want to find differential peaks between parent vs resistant cell lines. How can I achieve this? Should I use homer?

Thanks

ChIP-Seq • 1.4k views
ADD COMMENT
1
Entering edit mode
5.3 years ago
colin.kern ★ 1.1k

Q1: After Alignment step, should I call the peaks separate for each input and experiment replicate and then i should find the common peaks between all the replicates of input and experiment?

There isn't a standard approach that everyone takes. ENCODE has an IDR (Irreproducible discovery rate) pipeline to get a combined set of peak calls from replicates, but it's mainly for TF ChIP-seq. I've used it for narrow marks like H3K4me3 and it works ok, but I don't think you'll get much from it with a broad mark like H3K27me3. I've seen people just keep peaks with >50% overlap between replicates. I've also just seen people combine their alignments from all replicates into a single bam and do peak calling on that. I think the first method is more stringent, so you'll get less false positives but probably miss some true positives.

Q2: Ultimately i want to find differential peaks between parent vs resistant cell lines. How can I achieve this? Should I use homer?

You can just look at the peak calls and compare peaks that are called in one group and not called in the other. If you get interesting results from that, then great. Otherwise, there are various tools out there to look at differential levels of enrichment. Macs2 has a diffpeak operation, there's a fairly new tool called NormR that does differential enrichment. I've also seen papers that call peaks, get the read counts within each peak, and then do a standard DEG-like analysis using, for example, EdgeR or DESeq2.

ADD COMMENT
0
Entering edit mode

Hi Colin Thanks. after searching different blogs, It seems that people do peak calling on each replicate separately followed by intersection of all the replicates.

I see people use diffbind for differential analysis that accounts for Biological replicates.

ADD REPLY
0
Entering edit mode

Hi Colin, Do you know where I can find more information about different types of TF-ChIP-seq peaks from ENCODE as the following. I want to know exactly the difference between them:

peaks and background as input for IDR
conservative IDR thresholded peaks
optimal IDR thresholded peaks
pseudoreplicated IDR thresholded peaks
peaks
ADD REPLY
1
Entering edit mode
5.3 years ago
ATpoint 85k

I recommend using a dedicated peak caller that makes use of replicate information and inputs such as PePr. macs is fine but does not use replicate information. IDR after macs is possible for sharp peaks (so not HeK27me3) but by default it only accepts n=2 rather than n=3 so you would need custom approaches which is not necessary when using PePr right away. For differential analysis, PePr has a command for this as well which might be interesting if you have little or no experience with differential analysis software such as csaw/edgeR, DiffBind or DESeq2. The latter tools have outstanding documentation, go read them to get a background. I would prefer running PePr on both the conditions of your experiment and then merge the peaks, followed by creation of a count matrix which you can analyze, e.g. with csaw.

Alternatively, csaw has a strategy (read manual) that uses sliding windows to avoid the necessity of peak calling at all. I still prefer calling peaks separately as one often requires a list of peaks for other purpose like clustering etc.

ADD COMMENT

Login before adding your answer.

Traffic: 1254 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