Nathaniel Smith wrote:
> On Thu, Mar 12, 2009 at 9:51 AM, Mark Larsen wrote:
>> I took your advice and implemented using "Parallel Python". Can you comment
>> on your choice of pyprocessing? It seems like a simple re-write to switch
>> over.
>
> I use pyprocessing partly because it gave me the
On Thu, Mar 12, 2009 at 9:51 AM, Mark Larsen wrote:
> I took your advice and implemented using "Parallel Python". Can you comment
> on your choice of pyprocessing? It seems like a simple re-write to switch
> over.
I use pyprocessing partly because it gave me the impression that it
was more tune
Thanks Nathaniel!
> Spawn multiple Python processes, each of which uses rpy2 to load
R, and talk to them over any Python-level IPC library.
The latter is really a huge improvement over the former, because there
are great IPC libraries for python -- e.g., the pyprocessing library
(included by defau
On Wed, Mar 11, 2009 at 1:04 PM, Mark Larsen wrote:
>
> I realize this has been hammered to death, but I can't seem to get my head
> around it.
>
> Is the mapping from rpy (or rpy2) to R a one-to-one?
Yes.
> Can either invoke multiple R processes from a single python program?
No (at least not
I realize this has been hammered to death, but I can't seem to get my head
around it.
Is the mapping from rpy (or rpy2) to R a one-to-one? Can either invoke
multiple R processes from a single python program?
In the past I've used python threads and piped stdin/stdout to multiple R
processes to t
