On applying spike-in-derived scaling factors to ChIP-seq data: adjust for background signal (input) or not?
0
0
Entering edit mode
18 days ago
kalavattam ▴ 280

In a previous post, I asked about the computation and application of spike-in derived scaling factors in ChIP-seq data processing. (See below for a summary of the method described in the post’s answer.)

If I understand correctly, these scaling factors should be applied to the ratio of IP to input coverage (e.g., with deepTools bamCompare, which can compute the ratio of two BAM files). This ratio represents the relative enrichment of protein-DNA interactions captured in the immunoprecipitation reaction, adjusted for background signal by the input. In contrast, applying the scaling factor directly to IP coverage alone (e.g., using deepTools bamCoverage) fails to account for variability in background signal. This approach—applying the scaling factor to IP-only coverage—has been described in these posts.

Is this understanding correct? How do other ChIP-seq researchers typically apply spike-in scaling factors in their analyses?

Method described in the previous post's answer:
To compute a spike-in-derived scaling factor for a given sample, take the following steps:

  1. Calculate the percentage of exogenous spike-in read alignments in the immunoprecipitate (IP) BAM file.
  2. Calculate the percentage of exogenous spike-in read alignments in the corresponding input BAM file.
  3. Compute the scaling factor by dividing the input spike-in percentage by the IP spike-in percentage, i.e., scaling factor = (input spike-in pct) / (IP spike-in pct)
  4. If comparing a group of samples, adjust the scaling factors by dividing each by the largest scaling factor in the group. This adjustment sets the maximum scaling factor to 1, ensuring consistent scaling across samples while preventing artificial signal inflation.
spike-in deepTools normalization ChIP-seq scaling-factor • 318 views
ADD COMMENT

Login before adding your answer.

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