Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

the conflict about the pheatmap and multibigwigsummary results #1296

Open
liuyu988 opened this issue Mar 11, 2024 · 1 comment
Open

the conflict about the pheatmap and multibigwigsummary results #1296

liuyu988 opened this issue Mar 11, 2024 · 1 comment

Comments

@liuyu988
Copy link

liuyu988 commented Mar 11, 2024

hi, everyone!
I recently analyzed the chip-seq data for histone marks. I am very confused with the results for pheatmap and multibigwigsummary results.
I plotted the enrichment level in the same genomic regions for WT and KO condition. from the profile or heatmap, I can get the conclusion that the average signal in WT will be higher than the ones in KO for some regions. however, I calculated the average scores for these regions by multibigwigsummary function, but I got the opposite result. To check the result, I observed the signal by IGV software. the observations were same as the heatmap, but opposite with the multibigwigsummary.

my code is as follow:

multiBigwigSummary:

multiBigwigSummary BED-file
--bwfiles WT.bw KO.bw
--BED file.bed
-out all.scores.npz --outRawCounts all.scores.tab
-p 35

plotHeatmap:

computeMatrix scale-regions -p 35 -S WT.bw KO.bw \
     -R file.bed -b 0 -a 0 -m 10000 --missingDataAsZero  -o all.mat.gz

plotHeatmap -m all.mat.gz -o all.pdf --interpolationMethod bicubic

my results:

igv
图片 1

multiBigwigSummary:

chr start end KO WT
chr4 155293554 155315474 24.22877 10.359672

could any one help me ? thanks a lot !
best wishes!
Yu

@WardDeb
Copy link
Member

WardDeb commented Mar 27, 2024

Are you sure you haven't flipped any labels somewhere ? The order in your multibigwigsummary is reversed from what your original command implies, and it seems to be post processed in some matter. If not, please share some example files to replicate the problem.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants