On Nov 11, 2013, at 12:40 PM, Karl Forner wrote:
> Dear all,
>
> I got an issue trying to parse excel files in parallel using XLConnect, the
> process hangs forever.
> Martin Studer, the maintainer of XLConnect kindly investigated the issue,
> identified rJava as a possible cause of the problem
Thanks Malcolm,
But it does seem to solve the problem.
On Mon, Nov 11, 2013 at 6:48 PM, Cook, Malcolm wrote:
> Karl,
>
> I have the following notes to self that may be pertinent:
>
> options(java.parameters=
> ## Must preceed `library(XLConnect)` in order to prevent "Java
>
Karl,
I have the following notes to self that may be pertinent:
options(java.parameters=
## Must preceed `library(XLConnect)` in order to prevent "Java
## requested System.exit(130), closing R." which happens when
## rJava quits R upon trapping INT (control-c), as is do
Dear all,
I got an issue trying to parse excel files in parallel using XLConnect, the
process hangs forever.
Martin Studer, the maintainer of XLConnect kindly investigated the issue,
identified rJava as a possible cause of the problem:
This does not work (hangs):
library(parallel)
require(rJava)
I like to propose a unified/standard system environment variable that
specifies the maximum number of cores an R session should use, e.g.
R_MAX_MC_CORES. This could then be used to *guide* multicore
implementations on the number of cores to use. This is different from
parallel::detectCores().
EN
Thanks Dirk. I'll confess I am mostly trying to follow the practices
outlined in the writing R-extensions manual and books by Chambers and
Gentleman, but have found some conflicting advice on the internet in
various places, and am also trying to build off a previously existing code
base (that at
