Le 08/07/2017 à 00:54, Duncan Murdoch a écrit :
I have now committed changes to R-devel (rev 72898) that seem to catch large and small errors. They only give a warning if the error happens when the
connection is closed, because that can happen asynchronously
For this asynchronous behavior, woul
On 10/07/2017 4:54 AM, Serguei Sokol wrote:
Le 08/07/2017 à 00:54, Duncan Murdoch a écrit :
I have now committed changes to R-devel (rev 72898) that seem to catch large
and small errors. They only give a warning if the error happens when the
connection is closed, because that can happen asynch
Le 10/07/2017 à 11:19, Duncan Murdoch a écrit :
On 10/07/2017 4:54 AM, Serguei Sokol wrote:
Le 08/07/2017 à 00:54, Duncan Murdoch a écrit :
I have now committed changes to R-devel (rev 72898) that seem to catch large
and small errors. They only give a warning if the error happens when the
con
On 10/07/2017 5:34 AM, Serguei Sokol wrote:
Le 10/07/2017 à 11:19, Duncan Murdoch a écrit :
On 10/07/2017 4:54 AM, Serguei Sokol wrote:
Le 08/07/2017 à 00:54, Duncan Murdoch a écrit :
I have now committed changes to R-devel (rev 72898) that seem to catch large
and small errors. They only giv
Le 10/07/2017 à 13:13, Duncan Murdoch a écrit :
On 10/07/2017 5:34 AM, Serguei Sokol wrote:
Le 10/07/2017 à 11:19, Duncan Murdoch a écrit :
On 10/07/2017 4:54 AM, Serguei Sokol wrote:
Le 08/07/2017 à 00:54, Duncan Murdoch a écrit :
I have now committed changes to R-devel (rev 72898) that seem
On 10/07/2017 9:00 AM, Serguei Sokol wrote:
Le 10/07/2017 à 13:13, Duncan Murdoch a écrit :
On 10/07/2017 5:34 AM, Serguei Sokol wrote:
Le 10/07/2017 à 11:19, Duncan Murdoch a écrit :
On 10/07/2017 4:54 AM, Serguei Sokol wrote:
Le 08/07/2017 à 00:54, Duncan Murdoch a écrit :
I have now commi
Hi,
I am working on some code to have a background R process running that I can
submit data to, check computation progress, and retrieve results later. I am
aware that "parallel" does a lot of that - however, "parallel" shuts down the
nodes when I quit the master process. On the contrary, I wou
You might find the https://github.com/r-lib/processx package useful.
Also, the dev version of https://github.com/r-lib/callr might be
useful. (The CRAN version of callr does not support background
processes.)
Gabor
On Mon, Jul 10, 2017 at 6:12 PM, Stravs, Michael
wrote:
> Hi,
>
> I am working o
Hi all,
I believe that 'do.call' shows inconsistent/undocumented behavior when its
'what' argument is of the format "pkg::fun". The documentation (?do.call)
suggests that
what: either a function or a non-empty character string naming the function
to be called.
Thus, I expected that all fou
On 10/07/2017 3:37 PM, Schlaepfer, Daniel wrote:
Hi all,
I believe that 'do.call' shows inconsistent/undocumented behavior when its 'what'
argument is of the format "pkg::fun". The documentation (?do.call) suggests that
what: either a function or a non-empty character string naming the func
>The function Rmpi::mpi.bcast.cmd() calls eventually something along the
lines of
>
>> scmd <- scmd <- substitute(cmd)
>> arg <- list(...)
>> scmd.arg <-serialize(list(scmd=scmd, arg=arg), NULL)
>> if (length(scmd.arg$args) > 0)
>>do.call(as.character(scmd.arg$scmd), scmd.arg$args, envir =
.Glo
As a follow up to this, Martin Maechler suggested that I write a small script
that allows this to be tested on Windows from R. The attached script
demonstrates creating and mounting a very small (4 MiB) VHD to a path on the
system (in this case c:/smallmount) and then calling write.csv with a la
12 matches
Mail list logo
