Problem with peak calling using hiddenDomains: entire chr12 lacking peaks.
Entering edit mode
12 months ago

Hi, I have a problem processing ChiP-Seq data. I have two datasets of H3K9me3 replicates aligned to the reference genome mm39. For peak calling, I used hiddenDomains.

About my problem: replicate A shows peaks on all chromosomes after peak calling, replicate C shows no peaks on Chr12. The .bw files of both replicas show reads on Chr12.

The manual of hiddenDomains says that you can change the parameters, and min.prob in case of problems. Testing different values of the three parameters (especially setting lower or higher) did not fix my problem with replica C.

In hidden domain it is stated that the peaks of each chromosome are called independently. However, when I remove ChrX and ChrY of the .bam files before peak calling, replicate A shows marginal changes, and with replicate C I additionally lose the peaks of Chr4.

To visualize my problem: On the igv snapshot below, replica A is blue, replica C is red. The top lane for each replicate shows the .bw file. The track below is the .bed file I got by peak calling with all the chromosomes, and the bottom track for each replicate is the .bed file I got by peak calling after removing ChrX and ChrY. IGV Browser View of .bw and .bed files after peak calling of replicates using hiddenDomains.

Does anyone who is familiar with peak calling with hiddenDomains or has ever had the problem of not being able to get peaks for certain regions despite existing reads in the .bw files and could help me?

Many thanks in advance!

Troubleshooting hiddendomain ChiP-Seq peakcalling • 365 views
Entering edit mode
12 months ago

I have fixed the problem yet. hiddenDomains uses the R package depmixS4 to estimate parameters for the hidden markov models. It seems that for some chromosomes the transition probabilities between the state "enriched" and "depleted" are estimated by depmixS4 to be 0.5 each. This results in chromosomes in which no peaks are called. I changed the seed for files where this problem occurred from 1 to 2, which fixed the problem.


Login before adding your answer.

Traffic: 2598 users visited in the last hour
Help About
Access RSS

Use of this site constitutes acceptance of our User Agreement and Privacy Policy.

Powered by the version 2.3.6