Normalizes ChIP-seq data using exogenous spike-in (ChIP-Rx with Drosophila chromatin per Orlando 2014 / Egan 2016; E. coli carryover for CUT&RUN/CUT&Tag). Distinguishes RRPM from Rx-Input scaling, integrates with DiffBind / DESeq2 / edgeR / csaw via sizeFactors and DiffBind library-size vectors, applies the Patel et al 2024 *Nat Biotechnol* failure-mode framework, and validates that normalization is applied at the read level (not peak counts). Use when global signal shifts are expected (HDACi, BETi, EZH2i, dosage, target knockdown), when ChIPseqSpikeInFree detects post-hoc shifts, or when validating internal-control regions before publication.
Normalizes ChIP-seq data using exogenous spike-in (ChIP-Rx with Drosophila chromatin per Orlando 2014 / Egan 2016; E. coli carryover for CUT&RUN/CUT&Tag). Distinguishes RRPM from Rx-Input scaling, integrates with DiffBind / DESeq2 / edgeR / csaw via sizeFactors and DiffBind library-size vectors, applies the Patel et al 2024 *Nat Biotechnol* failure-mode framework, and validates that normalization is applied at the read level (not peak counts). Use when global signal shifts are expected (HDACi, BETi, EZH2i, dosage, target knockdown), when ChIPseqSpikeInFree detects post-hoc shifts, or when validating internal-control regions before publication.
"Account for global signal changes that defeat standard normalization" -> Add exogenous reference chromatin (Drosophila for human/mouse ChIP-Rx; E. coli carryover for CUT&RUN/CUT&Tag) at fixed concentration BEFORE IP, derive scaling factors from spike-in read counts, and apply at the read or size-factor level (never to peak counts) to enable quantitative cross-condition comparison.
CLI: align reads to combined target + spike genome; count spike reads via samtools view -c
R (DiffBind integration): dba.normalize(obj, spikein = TRUE)
Post-hoc detection: ChIPseqSpikeInFree (when no spike-in was added)
The fundamental rule: spike-in scaling is applied at the READ level (via size factors or --scaleFactor), never multiplied into peak counts. This is a common implementation error in published spike-in ChIP.
When Spike-In Is Required
Experimental design
Spike-in needed?
HDAC inhibitor -> global H3K27ac increase
Yes
BET inhibitor (JQ1, OTX015) -> global BRD4 / H3K27ac decrease
Yes
EZH2 inhibitor -> global H3K27me3 loss
Yes
DNMT inhibitor -> global 5mC loss; downstream histone mark shifts
Yes
Target factor knockdown / degron
Yes (or matched-input subtraction)
Cell-cycle synchronization / arrest
Yes
Dosage titration
Yes
Standard TF perturbation, local rebinding expected
No (reads-in-peaks RLE works)
Histone mark cross-cell-type comparison
Recommended
CUT&RUN/CUT&Tag standard
E. coli carryover (automatic); deliberate Drosophila for high-stakes
Replicate-only experiment, no condition comparison
No
Why this is necessary: Standard normalization (RLE on reads-in-peaks, TMM on bins) assumes most regions don't change. When the perturbation IS the change-everything-globally biology, these methods force the median log2FC to zero, hiding the real effect.
Spike-In Protocol Taxonomy
Protocol
Spike organism
Added when
Notes
ChIP-Rx (Orlando 2014)
Drosophila S2 nuclei
After lysis, before IP
fixed Drosophila chromatin mass, ~27:1 human:Drosophila genome-copy ratio (Egan 2016)
ChIP-Rx variant (Bonhoure 2014)
Drosophila chromatin
After fragmentation, before IP
Different normalization layer
CUT&RUN/Tag E. coli
E. coli (carryover)
Automatic from bacterial pA-MNase/Tn5
Free; variable across enzyme batches
Heterologous spike-in
Defined yeast / E. coli chromatin
Added at lysis
Less common; defined concentration
xenoChIP
Species swap (mouse cells + human chromatin spike)
Before IP
Niche; specific cancer xenograft contexts
The dominant standard for human/mouse ChIP is Drosophila (ChIP-Rx). Drosophila is genetically distinct enough that mapping is unambiguous, and the genome size (~140 Mb) gives adequate read depth at small chromatin input.
Scaling Factor Calculation
RRPM (Orlando 2014): reference-adjusted reads per million.
scale_factor_i = min(N_spike) / N_spike_i
Apply at the read level. The sample with the fewest spike reads gets scale_factor = 1 (the maximum); others get < 1 (scaled down because they recovered more spike chromatin).
Rx-Input (Fursova 2019): additionally scales by input spike-in to correct IP efficiency variation.
This is more rigorous when input controls are available; required for some inhibitor experiments where IP efficiency itself changes.
Workflow: Drosophila ChIP-Rx Spike-In
Goal: Compute per-sample scaling factors from Drosophila spike-in reads and apply at the read level (not peak counts) to enable quantitative cross-condition ChIP-seq comparison.
Approach: Align reads to combined target + Drosophila genome, count spike reads at high mapq after deduplication, derive RRPM scaling factors (min/each), then apply via DESeq2 sizeFactors, DiffBind spike-in flag, or bamCoverage scaleFactor. Validate against internal-control regions (blacklist).
library(DESeq2)# Read spike-in counts into a vector aligned with sample order
spike_reads <-c(ctrl_1 =145000, ctrl_2 =132000, treat_1 =98000, treat_2 =85000)
scale_factors <-min(spike_reads)/ spike_reads
dds <- DESeqDataSetFromMatrix(counts, coldata, design =~ condition)# DESeq2 expects sizeFactors in INVERSE convention (sample with smallest factor gets largest sizeFactor)
sizeFactors(dds)<-1/ scale_factors
dds <- DESeq(dds, fitType ='parametric')
Workflow: E. coli Spike-In (CUT&RUN/CUT&Tag Automatic)
E. coli DNA from bacterial pA-MNase/pA-Tn5 production is automatic spike-in carryover.
# Combined indexcat hg38.fa ecoli_k12.fa > hg38_ecoli.fa
bowtie2-build hg38_ecoli.fa hg38_ecoli
# Align as in ChIP-Rx; count E. coli reads
ECOLI_READS=$(samtools view -c aln.filt.bam ecoli_chr1)
TOTAL_READS=$(samtools view -c aln.filt.bam)
echo"E. coli fraction: $(echo "scale=4; $ECOLI_READS / $TOTAL_READS" | bc)"# Target: 0.005-0.02 (0.5-2%); IgG: 0.02-0.05 (2-5%)# Scale factor same as ChIP-Rx: min(ecoli) / per_sample_ecoli# Apply at read or sizeFactors level
E. coli carryover is variable between enzyme production batches. For publication-grade cross-condition claims, supplement with deliberate Drosophila spike-in OR use a single enzyme lot across all experiments.
ChIPseqSpikeInFree: Post-Hoc Detection
When no spike-in was added, ChIPseqSpikeInFree (Jin 2020) attempts post-hoc detection of global shifts by analyzing signal-distribution shape changes.
library(ChIPseqSpikeInFree)
samples <- data.frame(
ID =c('ctrl_1','ctrl_2','treat_1','treat_2'),
BAM =c('ctrl_1.bam','ctrl_2.bam','treat_1.bam','treat_2.bam'),
ANTIBODY =rep('H3K27me3',4),
GROUP =c('Control','Control','Treatment','Treatment'))
res <- ChIPseqSpikeInFree(bamFiles = samples$BAM, chromFile ='hg38.chrom.sizes',
metaFile ='metadata.txt', prefix ='spikein_free_out')# Output: per-sample scaling factor + global-shift detection
Limitations: Heuristic; not a substitute for true spike-in. Use as:
Sanity check when spike-in was forgotten
Initial diagnosis before deciding whether spike-in is needed in next experiment
NOT for publication-grade claims
Internal-Control Sanity Check (Mandatory)
After applying spike-in scaling, internal-control regions should show NO signal change:
Region type
Source
Expected behavior post-spike-in
ENCODE blacklist v2
Amemiya 2019
No change (artifact regions)
Constitutive housekeeping promoters
Eisenberg 2013 list (HK genes); U6 snRNA promoter
Minor change only
Custom hyper-ChIPable regions
Top-1% input signal
Stable signal at artifact regions
Untouched chromosome (e.g., chrY in cell types without expression)
Genome
No signal change
# Compute mean signal at blacklist regions per condition; should be stable
bedtools multicov -bams ctrl_1.bam ctrl_2.bam treat_1.bam treat_2.bam \
-bed hg38-blacklist.v2.bed > blacklist_signal.tsv
# Apply scaling factors to per-sample counts; verify no shift across conditions
If internal controls shift after scaling, the normalization is broken. Common causes:
Scaling applied to peak counts instead of read counts
Spike-in reads not deduplicated before scaling
Spike-in genome not mapq-filtered (low-quality alignments inflated counts)
Spike-in saturated (>1M reads); titration not linear
Per-Tool Failure Modes
Scaling factor applied to peak counts instead of read counts
Trigger: Multiplying peak-by-sample count matrix entries by spike-in factor.
Mechanism: Peak counts already integrate over read counts; multiplying them double-corrects.
Symptom: Effect sizes 2-10× larger than expected biology; internal control regions also "shift" artifactually.
Fix: Apply via sizeFactors(dds) (DESeq2), normFactors (edgeR), or DiffBind's dba.normalize(..., library=<numeric vector>, normalize=DBA_NORM_LIB) to supply spike-in-derived library sizes, OR --scaleFactor (bamCoverage for tracks). Never multiply peak-level counts.
Spike-in reads not deduplicated before scaling
Trigger: Counting all aligned reads to spike genome including duplicates.
Mechanism: PCR duplicates of spike-in reads vary independently of input chromatin amount.
Symptom: Scaling factors poorly correlated with library prep batch; high inter-replicate variability.
Fix: Deduplicate with MarkDuplicates; apply ENCODE filter -F 1804 -q 30 before counting spike reads.
Spike-in mapq filter too loose
Trigger: Counting all reads aligning to spike genome.
Mechanism: Low-mapq reads at low-complexity regions (E. coli rRNA, Drosophila satellite) are often misaligned from host genome.
Fix: Apply -q 30 (high mapq) before counting spike reads.
Inverse convention errors with DESeq2 / edgeR
Trigger: Passing scale_factors directly to sizeFactors(dds) without inversion.
Mechanism: DESeq2 / edgeR DIVIDE counts by sizeFactors (normalized = counts / sizeFactor); a read-level spike-in scale factor multiplies reads, so it must be applied as its inverse. Convention difference.
Symptom: Effect sizes inverted (treatment shifted in wrong direction).
--normalizeUsing and --scaleFactor conflict in bamCoverage
Trigger: Passing both for spike-in scaled bigWig.
Mechanism: deepTools multiplies the --scaleFactor value by the factor computed from --normalizeUsing; adding --normalizeUsing therefore reintroduces library-depth normalization on top of the spike-in factor. The default --normalizeUsing None leaves --scaleFactor acting alone.
Fix: Use ONE: --scaleFactor alone for spike-in; --normalizeUsing alone otherwise. Verify via bamCoverage --help.
E. coli carryover inconsistent across enzyme batches
Trigger: Comparing CUT&Tag samples processed with different pA-Tn5 lots.
Mechanism: E. coli carryover varies between bacterial production batches; cross-batch comparison adds artificial variability.
Fix: Use single enzyme lot for cross-condition comparison; OR supplement E. coli with deliberate Drosophila spike-in.
ChIPseqSpikeInFree applied as primary normalization
Trigger: No spike-in was added; ChIPseqSpikeInFree used for publication-grade scaling.
Mechanism: ChIPseqSpikeInFree infers global shift from signal-distribution shape; this is a heuristic, not a measurement.
Fix: Use only as diagnostic. For publication, re-do experiment with deliberate spike-in.
Spike-in titration not verified linear
Trigger: Spike-in concentration too high (>5% of total reads) OR too low (<0.1%).
Mechanism: Outside linear range, scaling factor doesn't reflect actual ratio of input chromatin.
Fix: Verify titration linearity by varying spike-in concentration on a single sample; only use spike-in counts in linear range (typically 0.5-5% of total reads).
Reconciliation
Pattern
Likely cause
Action
Spike-in scaled vs CPM give opposite signs
Global shift; CPM forced to median; spike-in revealed it
Spike-in is correct; CPM is fooled
Scaling factor varies wildly between reps
Spike-in saturated / not in linear range
Verify titration; subsample if needed
Internal-control signal shifts after scaling
Scaling applied wrong layer; reads not dedup'd; mapq too loose
Apply pre-test diagnostic; recompute
ChIPseqSpikeInFree predicts shift but spike-in says no
Both interpretations possible; trust spike-in when available
Spike-in measurement > distribution heuristic
DiffBind spike-in vs manual sizeFactors differ
DiffBind applies inverse convention internally
Verify via dba.normalize(obj, bRetrieve=TRUE)
Common Errors
Error / symptom
Cause
Solution
Spike-in BAM column missing in DiffBind sample sheet
bamSpikeIn (DiffBind 3.x) vs older spikein field
Use spikein = TRUE in dba.normalize() with appropriate column
Drosophila reads on chromosome X include host chrX
Combined genome chromosome naming collision
Prefix Drosophila chroms with dm_ before combining
Scaling factors all close to 1
Spike-in not added at fixed amount
Verify Egan 2016 protocol; titrate the spike-in chromatin mass
Cross-condition results sign-flipped after scaling
Inverse convention bug
sizeFactors(dds) <- 1 / scale_factors
Blacklist signal shifts post-scaling
Normalization broken
Investigate spike-in scaling failure modes (peak-count vs read-level, dedup, mapq)
References
Orlando DA et al 2014 Cell Rep 9:1163 (ChIP-Rx framework)
Egan B et al 2016 PLoS One 11:e0166438 (ChIP-Rx protocol; fixed Drosophila chromatin mass)
Bonhoure N et al 2014 Genome Res 24:1157 (alternative Drosophila spike-in)
Fursova NA et al 2019 Mol Cell 74:1020 (Rx-Input scaling)
Jin H et al 2020 Bioinformatics 36:1270 (ChIPseqSpikeInFree)
Blanco E et al 2021 NAR Genom Bioinform 3:lqab064 (SpikChIP)
2024 NAR Genom Bioinform 6:lqae118 (SpikeFlow)
Patel L, Cao Y, Mendenhall EM, Benner C, Goren A 2024 Nat Biotechnol 42:1343 (spike-in normalization review; common failure modes; PMC12266361)
Stark R & Brown G 2011 Bioconductor (DiffBind with spikein parameter)
Related Skills
chip-seq/peak-calling - Upstream peak calling
chip-seq/chipseq-qc - Spike-in fraction QC
chip-seq/differential-binding - Apply spike-in via DiffBind / DESeq2 / csaw
chip-seq/cut-and-run-tag - E. coli spike-in carryover specifics
chip-seq/super-enhancers - SE calling requires spike-in for cross-condition
