-
Notifications
You must be signed in to change notification settings - Fork 8
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
Error with parallel processing with multidog #16
Comments
Hey @stephenrkeller, thanks for trying out the dev version of Hmm, could you try running the vignette code with the following settings from the future::plan(future::sequential)
mout <- multidog(refmat = refmat,
sizemat = sizemat,
ploidy = ploidy,
model = "norm",
nc = NA) This will let me see if the issue is because of the parallelization, or because I introduced a bug in the changes I made a couple weeks ago. Some other possibilities:
|
Thanks for the quick reply, David! I tried your suggestions. Here's the output from the first suggestions changing the settings on 'future':
And for the second example following the vignette using 'multicore':
All those packages are up to date. Thanks for the help here! |
Sorry about this. I guess my only other idea is to try out the version on CRAN --- it's possible that the issue is with the |
OK, thanks taking a look at it David. I'll revert back to using the stable release version for now. |
Hi David,
I'm trying to get multidog running on my Unix server (Ubuntu 18.04.4 LTS; 32 cores; 64Gb Mem). When I go to run the example data ("uitdewilligen) using code identical to the multidog vignette, and specifying nc = 2, I get the following error:
Versions:
-R version 3.4.4 (running R either interactive at the commandline or in Rscript; both produce the same error)
-updog 2.1.0
-future 1.21.0
I assume this relates to how the parallel processing is being implemented on my system. When I run a test with flexdog, everything is fine and I get expected outputs.
FYI, there isn't a lot of load on the system right now, so I don't think it's a memory issue. Any help would be greatly appreciated.
Thanks!
Steve
The text was updated successfully, but these errors were encountered: