search for: makeclusterpsock

...75565.html). However, the solutions posted on SO, GH or R-devel do not work in my case. So far, I unsuccessfully tested ? 1. Couple of reboots 2. Adding 192.0.0.1 to /etc/hosts 3. Using R.app instead of RStudio.app 4. Turn off the firewall Following Hendriks advice, ?cl <- future::makeClusterPSOCK(1L, verbose = TRUE, timeout = 60)? gives (note: without adding the timeout parameter, R just hangs): > Sys.setenv(LANGUAGE='en') > cl <- future::makeClusterPSOCK(1L, verbose = TRUE, timeout = 60) [local output] Workers: [n = 1] ?localhost? [local output] Base port: 11867 [local out...

...No such file or directory > > but '-' works: > > $ nice -19 date > Sun Dec 3 20:01:31 PST 2017 > > Neither 'nice --help' nor 'man help' mention the use of a +n option. > > > WORKAROUND: As a workaround, you can use: > > cl <- future::makeClusterPSOCK(2L, rscript = c("nice", > "--adjustment=10", file.path(R.home("bin"), "Rscript"))) > > which is backward compatible with parallel::makePSOCKcluster() but > provides you with more detailed control. Try adding verbose = TRUE to > see what the ex...

...case. > > So far, I unsuccessfully tested ? > > 1. Couple of reboots > 2. Adding 192.0.0.1 to /etc/hosts > 3. Using R.app instead of RStudio.app > 4. Turn off the firewall > > Following Hendriks advice, ?cl <- future::makeClusterPSOCK(1L, verbose = TRUE, timeout = 60)? gives (note: without adding the timeout parameter, R just hangs): >> Sys.setenv(LANGUAGE='en') >> cl <- future::makeClusterPSOCK(1L, verbose = TRUE, timeout = 60) > [local output] Workers: [n = 1] ?localhost? > [local o...

...th > parallel::makeCluster(), so that you don't happen to pick up > snow::makeCluster() if 'snow' is attached and ahead of parallel on the > search() path. > > * Try creating a single background worker, i.e. parallel::makeCluster(1L). > > * Try with cl <- future::makeClusterPSOCK(1L, verbose = TRUE), which > gives the same thing, but it also show you some details on what it > does internally; that may give some clues where it stalls. > > /Henrik > > On Sat, Feb 10, 2018 at 12:11 PM, T. Florian Jaeger > <fjaeger at ur.rochester.edu> wrote: >>...

Hi all, I can't get the functionality of the package parallel to work. Specifically, makeCluster() hangs when I run it. I first noticed the problem when trying to run Rstan with multiple cores and the traced it back to the core package parallel. The following results in R hanging after the call to makeCluster. library(parallel) # Calculate the number of cores no_cores <-

...ut using '+', e.g. $ nice +19 date nice: +19: No such file or directory but '-' works: $ nice -19 date Sun Dec 3 20:01:31 PST 2017 Neither 'nice --help' nor 'man help' mention the use of a +n option. WORKAROUND: As a workaround, you can use: cl <- future::makeClusterPSOCK(2L, rscript = c("nice", "--adjustment=10", file.path(R.home("bin"), "Rscript"))) which is backward compatible with parallel::makePSOCKcluster() but provides you with more detailed control. Try adding verbose = TRUE to see what the exact call looks like. /H...

...your R code. All that it takes is to fix this is to update: cmd <- paste(rshcmd, "-l", user, machine, cmd) to something like: cmd <- paste(rshcmd, if (length(user) == 1L) paste("-l", user), machine, cmd) This is one example of what I've patched in parallelly::makeClusterPSOCK() over the years. Another is the use of reverse tunneling in SSH - that completely avoids the need to know and specify your public IP and reconfiguring the firewalls from the remote server back to your local machine so that the worker can connect back to your local machine. Not many users have th...

Hi all, Is it possible to use the 'renice' option together with parallel clusters of type 'PSOCK'? The help page for parallel::makeCluster is not specific about which options are supported on which types and I am getting the following message when passing renice = 19 : > cl <- parallel::makeCluster(2, renice = 19) nice: ?+19?: No such file or directory Kind regards,

...SO, GH or R-devel do not work in my case. > > So far, I unsuccessfully tested ? > > 1. Couple of reboots > 2. Adding 192.0.0.1 to /etc/hosts > 3. Using R.app instead of RStudio.app > 4. Turn off the firewall > > Following Hendriks advice, ?cl <- future::makeClusterPSOCK(1L, verbose = TRUE, timeout = 60)? gives (note: without adding the timeout parameter, R just hangs): >> Sys.setenv(LANGUAGE='en') >> cl <- future::makeClusterPSOCK(1L, verbose = TRUE, timeout = 60) > [local output] Workers: [n = 1] ?localhost? > [local output] Base port...

...-vanilla, but make sure to try with parallel::makeCluster(), so that you don't happen to pick up snow::makeCluster() if 'snow' is attached and ahead of parallel on the search() path. * Try creating a single background worker, i.e. parallel::makeCluster(1L). * Try with cl <- future::makeClusterPSOCK(1L, verbose = TRUE), which gives the same thing, but it also show you some details on what it does internally; that may give some clues where it stalls. /Henrik On Sat, Feb 10, 2018 at 12:11 PM, T. Florian Jaeger <fjaeger at ur.rochester.edu> wrote: > Hi all, > > I can't get th...

...is to update: > > cmd <- paste(rshcmd, "-l", user, machine, cmd) > > to something like: > > cmd <- paste(rshcmd, if (length(user) == 1L) paste("-l", user), machine, cmd) > > This is one example of what I've patched in > parallelly::makeClusterPSOCK() over the years. Another is the use of > reverse tunneling in SSH - that completely avoids the need to know and > specify your public IP and reconfiguring the firewalls from the remote > server back to your local machine so that the worker can connect back > to your local machine. No...

On Mon, 31 Oct 2016, Henrik Bengtsson wrote: > Thank you for looking into this Luke. > > On Thu, Oct 27, 2016 at 9:26 AM, <luke-tierney at uiowa.edu> wrote: >> On unix, unless event polling is enabled Sys.sleep just waits in a >> select() call (with a SIGINT handler in place) so the elapsed time >> isn't checked until after the select call is complete.

Hi all, Henrik Bengtsson has done some fantastic work with {future} and, more importantly, greatly improved constructing and deconstructing a parallelized environment within R. It was with great joy that I saw Henrik slowly split off some functionality of {future} into {parallelly} package. Reading over the package?s README, he states: > The functions and features added to this package are