On Mon, Sep 7, 2009 at 4:47 PM, Andrew Piskorski wrote:
> On Sat, Sep 05, 2009 at 08:31:18PM +0200, Peter Juhasz wrote:
>
>> I don't understand how is this possible. Maybe there is an issue of
>> thread-safety with the R backend, meaning that the two R *interpreter*
>> instances are talking to the
On Mon, Sep 07, 2009 at 05:36:38PM +0200, Peter Juhasz wrote:
> But please see http://www.perlmonks.org/index.pl?node_id=793907 ,
> where I posted my R code in its simplest form along with an example
> run which exhibits the symptoms I originally wrote about.
Ah, your two-process serialization is
On Sat, Sep 05, 2009 at 08:31:18PM +0200, Peter Juhasz wrote:
> I don't understand how is this possible. Maybe there is an issue of
> thread-safety with the R backend, meaning that the two R *interpreter*
> instances are talking to the same backend that's capable of processing
> only one thing at
On Sep 5, 2009, at 2:31 PM, Peter Juhasz wrote:
Reposting from R-help:
Dear R experts,
please excuse me for writing to the mailing list without subscribing.
I have a somewhat urgent problem that relates to R.
I have to process large amounts of data with R - I'm in an
international collaborat
Reposting from R-help:
Dear R experts,
please excuse me for writing to the mailing list without subscribing.
I have a somewhat urgent problem that relates to R.
I have to process large amounts of data with R - I'm in an
international collaboration and the data processing protocol is fixed,
that
