In pvec(list(1, 2), FUN, mc.cores=2) FUN sees integer() arguments whereas
pvec(list(1, 2, 3), FUN, mc.cores=2) FUN sees list() arguments; the latter seems
consistent with pvec's description.
This came up in a complicated Bioconductor thread about generics and parallel
evaluation
https://
On 12-10-25 7:18 PM, Ben Bolker wrote:
in src/library/utils/man/relist.Rd, line 50:
objects into a vector representation. \code{relist()}, it's methods and
spurious apostrophe ...
Thanks, will fix.
Duncan Murdoch
__
R-devel@r-project.org m
in src/library/utils/man/relist.Rd, line 50:
objects into a vector representation. \code{relist()}, it's methods and
spurious apostrophe ...
Ben Bolker
__
R-devel@r-project.org mailing list
https://stat.ethz.ch/mailman/listinfo/r-devel
Richard,
that is not what I had in mind :). Also Rserve 0.x doesn't have built-in HTTP,
only the 1.x series does. Unfortunately I don't have any time today to write
example code, but I would suggest using HTTP for both - just have a hook that
simply accepts serialized R object in the body of th
On 25/10/12 7:14 PM, Dan Tenenbaum wrote:
On Thu, Oct 25, 2012 at 8:45 AM, Richard D. Morey wrote:
On 24/10/12 10:55 PM, Simon Urbanek wrote:
The point is that you need a separate monitoring process or threads. That
process can be R, Rserve or any thing else.
Thanks for the tips. This is
On Thu, Oct 25, 2012 at 8:45 AM, Richard D. Morey wrote:
> On 24/10/12 10:55 PM, Simon Urbanek wrote:
>>
>>
>> The point is that you need a separate monitoring process or threads. That
>> process can be R, Rserve or any thing else.
>>
>>
>>
>
> Thanks for the tips. This is what I'm currently conte
On 24/10/12 10:55 PM, Simon Urbanek wrote:
The point is that you need a separate monitoring process or threads. That
process can be R, Rserve or any thing else.
Thanks for the tips. This is what I'm currently contemplating:
1. Main interface starts in user's R session, and opens up the in
On 12-10-25 5:28 AM, Martin Maechler wrote:
Sorry guys, for coming late,
but *please* don't go there.
I've been there years ago,
and found later why the approach is flawed "by design" :
Internationalization / Localization:
- If the warning comes from a "standard R" function,
the warning is
Sorry guys, for coming late,
but *please* don't go there.
I've been there years ago,
and found later why the approach is flawed "by design" :
Internationalization / Localization:
- If the warning comes from a "standard R" function,
the warning is almost surely different in a (say) German
loc
