Replies: 3 comments 2 replies
-
Hi. Before anything else, what's your I suspect that this has to do with you having a customized doFuture::registerDoFuture()
paths <- foreach(x = 1) %dopar% { .libPaths() }
print(paths) |
Beta Was this translation helpful? Give feedback.
-
Hi Henrik, Thanks for your quick reply. I've now manually installed the packages on the cluster, it's set up the lib destination automatically and I have not done anything with .libpaths() this time around. There is no error (yay!), but I'm back to the original problem, which is that it's hanging on the cluster. This R script takes 33 seconds to run locally, whereas on the cluster I killed it after 2 mins and it made it through just 1 of 30 iterations that had otherwise locally completed in that time. Is this a common issue? Is there a fix? For what it's worth the info:
Thank you, |
Beta Was this translation helpful? Give feedback.
-
Hmm what's the verdict? |
Beta Was this translation helpful? Give feedback.
-
Hello,
I am running an r script which works locally, looks like:
Which works fine locally but when run on the cluster gives,
only after the foreach is called, not on the library import.
I've tried various other calls like
and also
same error... when I tried running sequentially on the cluster it works
So I'm thinking it's a futures framework thing?
Here's some more info
also,
and
Any ideas? Thank you!
Beta Was this translation helpful? Give feedback.
All reactions