Is the same order when using p value or q value for compareCluster analysis?
1
0
Entering edit mode
12 months ago
Lu.Lu • 0

Hey,

I'm so confused about a simple question, hope you guys could help me!

So I do a GO analysis using compareCluster as I compared my down-regulated genes and up-regulated genes. I'm wondering whether the order is the same if I use p value or q value to plot the GO results? or the basic question is the rank order the same when use p value or q value?

This pictures I plotted using dotplot function, and ggplot2 separately.

enter image description here

enter image description here

Clusterprofiler q-value p-value compareCluster • 925 views
ADD COMMENT
1
Entering edit mode
12 months ago
seidel 11k

Adjusting P-values inflates the values but does not change the order of the values. You can test this by plotting the the P-values and the Q-values against each other. In cases where some sets of P-values are identical, it's not clear how to control the sorting order. Are you explicitly determining the order in each of your plots?

ADD COMMENT
1
Entering edit mode

Since qvalues/FDR can have ties (for example large pvalues can often have FDR of 1) it would depend on how ties are broken by the ordering method. I would order by pvalue but report FDR/q.

ADD REPLY
0
Entering edit mode

yes, you are right! I also found that, the large p values have FDR of 1.

ADD REPLY
0
Entering edit mode

Thanks so much for your kind reply! I understand this now, but from my data, it seems they are different, the first one is sorting by p value, the second one is sorting by q value, look at "signal release". enter image description here

enter image description here so I was so confused!

and yes, I want to have a final plot that should be like this, enter image description here

do you have some ideas to do that?

ADD REPLY

Login before adding your answer.

Traffic: 1728 users visited in the last hour
Help About
FAQ
Access RSS
API
Stats

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

Powered by the version 2.3.6