-
Notifications
You must be signed in to change notification settings - Fork 36
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
Disrepancy GSEA results when using by="DOSE" or by="fgsea" #18
Comments
I would expect some difference due to randomness of the algorithms. You The difference should be smaller if you increase number of permutations. On Mon, Nov 14, 2016, 13:26 Guido Hooiveld [email protected] wrote:
|
Thanks Alexey for your comments. |
I have a similar problem but for me the gsea results change run by run. The pathways who were on the top of list are not the same when I re-run . What did I wrong ? |
Hi, I don't know whether I should ask here, or at the maintainer of
fgsea
(@assaron), but after analyzing the example DOSE dataset using the GSEA algorithm implemented in eitherDOSE
orfgsea
, I noticed the results are IMO quite different. I realize that the results are permutation based, and that the results are therefore expected not to be 100% identical, but i find the observed differences quite large. Could you maybe comment on this whether this is expected? Thanks, GuidoFull code below, but main outcome:
gseDO(geneList,by="DOSE")
identified 162 significantly regulated gene setsgseDO(geneList,by="fgsea")
identified 149 significantly regulated gene setsBut overlap is only 138!
Unique for 'DOSE' are 24 gene sets, for 'fgsea' 11.
Also the top regulated Gene Sets are completely different... ??
As said before, I expected some differences, but NOT because 2 different implementations of the same algorithm were used, but rather because of the permutations (that are random).
The text was updated successfully, but these errors were encountered: