nomarlizing sequencing depth when use macs2 bdgbroadpeaks
Hey
I was wondering when I use macs2 bdgbroadpeaks to call broad peaks on bedgraph file (which is converted from bigwig file that is converted from bam file by our collaborator, don't ask me why they did this and they couldnt find the original bam file), how do I normalize the sequencing depth by million like macs2 callpeak options. And i notice the only output from this is the bed file:
macs2 bdgbroadcall -i fileNameExample.bw.bedGraph --o-prefix fileNameExample.bw.bedGraph
0 answers
No answers yet.
Log in to answer this question.
More posts like this
-
difference between macs2 callpeak using bam and bed file
written by QX •
-
1 is not found in chromosome sizes file
written by Aki •
-
macs2 bdgpeakcall only gives a few peaks
written by baijiangshan9726 •
-
bigWig tracks inconsistent with MACS2 callpeak
written by lida •
-
macs2 bdgbroadcall reporting problem
written by mabdelhalim82 •
-
Normalizing ChIP-seq and ATAC-seq data?
written by star
-
Macs2: predicted fragment length less than 2*tag length
written by langya •
-
macs2 callpeak error
written by jolin0701-dy
-
MACS2 Broad peaks output BED format
written by haithem.barbour •
-
normalize on chip-seq data
written by catherine
It's expecting the input file to be appropriately normalized, if I remember correctly. If you know the original depth (or can at least eye-ball it) then you could use wiggletools to scale the file until you get something reasonable.
can they find the FASTQ files? If not, they'll be in trouble upon submission anyway as they are going to be required by most journals to submit the raw data to a repository
You'll most likely be much better off to re-do the alignment and do things properly