Re: [Rd] nested parallel workers

2015-03-30 Thread Valerie Obenchain
On 03/30/2015 02:51 PM, Simon Urbanek wrote: On Mar 30, 2015, at 4:40 PM, Valerie Obenchain wrote: On 03/25/2015 07:48 PM, Simon Urbanek wrote: On Mar 25, 2015, at 3:46 PM, Valerie Obenchain wrote: Hi Simon, I'm having trouble with nested parallel workers, specifically, forking inside s

Re: [Rd] nested parallel workers

2015-03-30 Thread Simon Urbanek
On Mar 30, 2015, at 4:40 PM, Valerie Obenchain wrote: > On 03/25/2015 07:48 PM, Simon Urbanek wrote: >> On Mar 25, 2015, at 3:46 PM, Valerie Obenchain >> wrote: >> >>> Hi Simon, >>> >>> I'm having trouble with nested parallel workers, specifically, forking >>> inside socket connections. >>>

Re: [Rd] nested parallel workers

2015-03-30 Thread Valerie Obenchain
On 03/25/2015 07:48 PM, Simon Urbanek wrote: On Mar 25, 2015, at 3:46 PM, Valerie Obenchain wrote: Hi Simon, I'm having trouble with nested parallel workers, specifically, forking inside socket connections. You simply can't by definition - when you fork *all* the workers share the same c

Re: [Rd] nested parallel workers

2015-03-25 Thread Simon Urbanek
On Mar 25, 2015, at 3:46 PM, Valerie Obenchain wrote: > Hi Simon, > > I'm having trouble with nested parallel workers, specifically, forking inside > socket connections. > You simply can't by definition - when you fork *all* the workers share the same connection inherited from the parent, so

[Rd] nested parallel workers

2015-03-25 Thread Valerie Obenchain
Hi Simon, I'm having trouble with nested parallel workers, specifically, forking inside socket connections. When mclapply is called inside a SOCK, PSOCK or FORK worker I get an error in unserialize(). cl <- makeCluster(1, "SOCK") fun = function(i) { library(parallel) mclapply(1:2, sqrt) }