-
Notifications
You must be signed in to change notification settings - Fork 68
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
fgsea never ending #19
Comments
Hi Lluís, Does it sitll happen if you set |
Same data: system.time(gseaSizeEffect <- fgsea(grouping, comp1, nperm = 10000))
##
## Timing stopped at: 0.068 0.12 43.18
system.time(gseaSizeEffect <- fgsea(grouping, comp1, nperm = 10000, nproc = 1))
## user system elapsed
## 0.260 0.028 0.289
system.time(gseaSizeEffect <- fgsea(grouping, comp1, nperm = 20000, nproc = 1))
# I had to stop it after ~5 minutes (and restart Rstudio)
# In a R --vanilla session (After loading the previous part of the script):
system.time(gseaSizeEffect <- fgsea(grouping, comp1, nperm = 10000, nproc = 1))
# I had to close the terminal after ~5 minutes
# In a R --vanilla session
#(Only loading the data and some packages: fgsea, reactome.db, org.Hs.eg.db, data.table):
system.time(gseaSizeEffect <- fgsea(grouping, comp1, nperm = 10000, nproc = 1))
# I had to close the terminal after ~5 minutes Thanks for the quick response |
Is it specific for your |
Yes, it seems specific to my data (sorry I should have checked that before). |
I can reproduce this. We'll look into it a bit later. |
Oh 😮 , I didn't expect to be reproducible, I thought it was a problem in my computer 😭 |
It doesn't seem to be driven by the number of permutations by it self, since repeated execution lead to the same outcome.
Then executing the same code
Sometimes I can execute this twice or thrice without an error, sometimes just once. Also reproducible if
|
@ToledoEM Thanks, nice report. |
It works now, however, current algorithm does not properly support equal ranks (zero or not) as the ranking is not full in such case. So be cautious about the results. See #18 |
Thanks for the fix. |
I have some problem for a while, it seems like fgsea never return the results:
So while the 10k permutations takes 0.116 and 0.516 for the system and in total, when I double it it takes much more and I had to stop the function (I had this same function running for 3 days without returning any value), despite being reported that to the user it took less than a second the output wasn't ready after 10 minutes. And a similar thing happened when I used 1k permutation and doubled to 2k.
Sorry I couldn't make it reproducible, I really don't understand what can be triggering this. Here is some information about the data I am testing:
Perhaps the problem is that ~78% of my stats are 0, and so they are equivalent in the position. But when I removed them I also had the same problem.
The
session_info("fgsea")
:The text was updated successfully, but these errors were encountered: