Question: Differential Peak Analysis from ENCODE Pipeline normalized outputs
0
gravatar for sjquon
12 months ago by
sjquon0
sjquon0 wrote:

I processed my ChIP-seq and ATAC samples using the ENCODE pipeline (https://github.com/ENCODE-DCC/chip-seq-pipeline2 and https://github.com/ENCODE-DCC/atac-seq-pipeline). These pipelines gives outputs such as aligned bam files, bigwig files for signal normalized to control, and IDR filtered big bed peak files.

When my samples are not normalized, they have an efficiency difference so that some samples overall have higher peaks than others. The ENCODE pipeline corrects this problem by correcting to controls, but to my knowledge that output is a bigwig file. I am concerned that if I look at differential peaks using the bam files to look for enrichment, then many peaks will be lost due to the efficiency difference. On the other hand, I can't seem to find any programs where I can use a bigwig file and a peak file to calculate differential peaks.

Does anyone have any good strategies for calculating differential peaks from the normalized outputs of the ENCODE pipeline?

chip-seq encode atac • 589 views
ADD COMMENTlink modified 12 months ago by ATpoint40k • written 12 months ago by sjquon0
0
gravatar for ATpoint
12 months ago by
ATpoint40k
Germany
ATpoint40k wrote:

The ENCODE pipeline corrects this problem by correcting to controls

I do not know the ENCODE pipeline but I find this unlikely. YOu have to normalize between samples, not to any controls as these controls (in ChIP-seq) are typically only used for peak calling to distinguish signal (= true immunoprecipitation by the antibody) from noise (=unspecific binding to the antibody, IgG control). Typically one calls peaks over the samples, creates a count matrix and then uses tools like edgeR or DESeq2 for normalization and differential analysis. This can be done from BAM files using e.g. featureCounts after peak calling with macs2. Don't use these bigwig files. Differential analysis should start from raw counts, see the manuals from edgeR and DESeq2 for details. Don't ever make conclusions by comparing browser tracks directly from BAM files as they are completely un-normalized and any difference you see can be due to different sequencing depth. It is not informative to do that without normalization. Normalized bigwigs (at least normalized for depth) can be done by bamCoverage from deeptools.

ADD COMMENTlink modified 12 months ago • written 12 months ago by ATpoint40k
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: 1754 users visited in the last hour