[Rsiena-help] More flexibility on using Clusters

[George Vega Yon]

Dear Prof. Ripley,

Thanks for your email. After your suggestion I tried setting the
environment variable R_PARALLEL_PORT without success. Will try to submit a
patch via R-forge.

Best,

George G. Vega Yon
+1 (626) 381 8171
http://www.its.caltech.edu/~gvegayon/

On Sat, Jul 16, 2016 at 9:51 AM, Ruth Ripley <ruth at stats.ox.ac.uk> wrote:

> Dear George,
>
> I am not working on RSiena any more, but wrote the R function siena07.
>
> It seems from the help for makePSOCKCluster in the parallel package that
> you can set up the port via an environment variable R_PARALLEL_PORT.
> Have you tried this?
>
> If this does not help, RSiena is on R-forge
> (https://r-forge.r-project.org/R/?group_id=461), and you could ask to
> join the team of developers.
>
> It is also possible to change the source code within a package using the
> functions insertSource() or fixInNamespace().
>
> Hope this helps,
>
> Ruth
>
>
> On 15/07/2016 21:05, George Vega Yon wrote:
> > Hey there,
> >
> > Recently I've started working with the R package -parallel- using
> > multiple machines each one with its own address (host). The connections
> > are not done via port 22 and further depend on username. Here is an
> > example of a PSOCK cluster that I create
> >
> > cl <- makePSOCKcluster(c('localhost', 'machine2.website.com
> > <http://machine2.website.com>' , 'machine3.website.com
> > <http://machine3.website.com>'), user='myusername', rshcmd='ssh -p
> > PORTNUMBER')
> >
> > Notice that I use rshcmd to specify the port number. This last point I
> > cant do in siena07. I know that I can change the default port in ssh and
> > do something like this
> >
> > cl <- makePSOCKcluster(c('localhost', 'myusername at machine2.website.com
> > <mailto:myusername at machine2.website.com>' ,
> > 'myusername at machine3.website.com <mailto:myusername at machine3.website.com
> >'))
> >
> > which solves the issue, but having to change the default port number on
> > my computer isn't the nicest solution either. That said, I wanted to ask
> > if any of you guys have came up with a similar situation and how you
> > solved it.
> >
> > On the side I think it might be a good idea to include a -cl- argument
> > on -siena07- so that the user can build its own cluster and pass it
> > directly to siena07 (just like the boot command in the boot package
> > does). Not a big change to make but very useful. If only I could submit
> > patches to RSiena (like one does via Pull Requests on github) I would
> > love to do so (any way of doing that?).
> >
> > Best,
> >
> > George G. Vega Yon
> > +1 (626) 381 8171
> > http://www.its.caltech.edu/~gvegayon/
> >
> >
> > _______________________________________________
> > Rsiena-help mailing list
> > Rsiena-help at lists.r-forge.r-project.org
> > https://lists.r-forge.r-project.org/cgi-bin/mailman/listinfo/rsiena-help
> >
> _______________________________________________
> Rsiena-help mailing list
> Rsiena-help at lists.r-forge.r-project.org
> https://lists.r-forge.r-project.org/cgi-bin/mailman/listinfo/rsiena-help
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.r-forge.r-project.org/pipermail/rsiena-help/attachments/20160718/72dc69be/attachment.html>