Skip to content
Prev 1758 / 2152 Next

Is combining mclapply and gbm tasks possible using R-3.0.1 ?

I think the problem has more to do with the version of gbm that you're
using, not the version of R.  Looking over gbm 2.1 briefly, it looks
like it always creates a cluster object and does the cross validation
with parLapply, even when you specify n.cores = 1.  That explains why
you see the messages from your .Rprofile within the mclapply tasks.
The error messages from socketConnection may be happening because
you're creating four cluster objects on the same machine at about the
same time, resulting in port collisions.  If you had any control over
how the cluster object was created by gbm, you might be able to
specify different ports for the different mclapply tasks, but it
doesn't look like gbm has made any provision for that kind of control.

If this is important to you, I think you should either back off to an
older version of gbm, or talk to the package maintainer.  I don't
think the package expects you to call gbm using mclapply.

- Steve

On Wed, Aug 21, 2013 at 5:45 AM, Patrick Connolly
<p_connolly at slingshot.co.nz> wrote: