Question: bigWig tracks inconsistent with MACS2 callpeak
gravatar for lida
12 days ago by
lida10 wrote:

Hi, all

Recently, I have been dealing with some H3K27me3 ChIP-seq data. I used MACS2 to callpeak (with --broad ) and visualized the bw files (converted from bam) in IGV.

For me, this entire window seems possessed H3K27me3 modification, but the MACS2 just take the high signal region as H3K27me3 peak.

What I want to do is to get genes with H3K27me3 modification. If I take MACS2 as reference it may overlook some genes with low level H3K27me3 modification.

My question is how do yours handling this broad peak issues? Do we have better peakcallers for broad peaks like H3K27me3?

Thanks in advance


chip-seq macs2 • 113 views
ADD COMMENTlink written 12 days ago by lida10

Can you post your full MACS2 command, and are any of those tracks input or some sort of negative control?

ADD REPLYlink written 12 days ago by rpolicastro4.0k

Sure, my MACS2 command is macs2 callpeak -t <IP.bam> -c <Input.bam> -f BAM -g dm -p 0.01 -B --outdir macs_res --min-length 3000 --nomodel --extsize 300 --broad

This is input and IP samples

ADD REPLYlink modified 11 days ago • written 11 days ago by lida10
Please log in to add an answer.


Use of this site constitutes acceptance of our User Agreement and Privacy Policy.
Powered by Biostar version 2.3.0
Traffic: 1255 users visited in the last hour