-
Notifications
You must be signed in to change notification settings - Fork 39
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
Differences in pvalues in MONSTER #335
Comments
Hey @violafanfani cc @taraeicher , They're the same because transition matrices are symmetrical. Marouen |
I take that back |
But I am expecting the results to be only very slightly different because the statistic measures deviation from the identity matrix. So for a given matrix, comparing the columns to those of a null or the rows to the rows of the same null matrix are similar statistics. I am thinking they might be equal even but for consistency, let's change it. |
I am not super familiar, so I can only tell you what I observed. The results are heavily different, which is something we can also expect by looking at figure 2 in the paper (https://pubmed.ncbi.nlm.nih.gov/29237467/#&gid=article-figures&pid=fig-2-uid-1). You can see that the TM is behaving different on the columns and the rows, TM are not symmetrical (at all). |
@violafanfani Yes, I took back my comment about symmetry. Can you post some p-values for TFs with each function? |
It is not just the values of rows vs columns, the functions also compares rows or columns to a null distribution of rows or columns. Line 674 in 9dd9438
Line 751 in 9dd9438
|
From my experiment on yeast cell cycle test data, it is very (very) different. I get as significant TFs that are in the middle of the dTFI plot |
Can you post them heree? |
I am uploading the dTFI figure with the TF significant at pval<0.05, old: is the code on netzoor to compute pvalues, whole the other file is the one where I use the pvals computed as in the dTFI figure. In the logs there I also print the first 10 pvals in the two cases, Old (monsterCalculateTmPValues(res, method = 'z-score')): Correct (monsterCalculateTmPValues(res, method = 'z-score') with axis =2): old_monster_figure.pdf |
Wow this is really different! Thanks for finding this 👍 💯 |
I am trying to measure the pvalues for each TF and I started using the "monsterCalculateTmPValues".
However, after getting some confusing results I checked the code in the function and compared it to the one inside "monsterdTFIPlot" and they differ at least here:
ssodm <- apply(res@tm,2,function(x){t(x)%*%x})
ssodm <- apply(res@tm,1,function(x){t(x)%*%x})
netZooR/R/MONSTER.R
Line 756 in 9dd9438
Which one is correct? Can you check if this is a mistake or a desired function?
The text was updated successfully, but these errors were encountered: