Description Usage Arguments Details See Also Examples
This function is a simple wrapper around the system() command. As such, data is not shared between the calling R process and the batch processes which execute the 'body' source.
1 2 |
nranks |
The number of MPI ranks to launch. |
mpicmd |
The command to launch mpi as a string (e.g., "mpirun", "mpiexec", "aprun", ...). |
bcaster |
The method used by the servers to communicate. Options are "zmq" for ZeroMQ-based communication, or "mpi" for |
port |
A numeric value, or optionally for |
auto.dmat |
Logical; deteremines if pbdDMAT should automatically be loaded
and |
Launcher for the pbdR server.
The port
values between the client and server MUST
agree. If they do not, this can cause the client to hang.
The servers are launched via pbdRscript()
.
The client is a specialized REPL that intercepts commands sent through the R interpreter. These commands are then sent from the client to and evaluated on the servers.
The client communicates over ZeroMQ with MPI rank 0 (of the
servers) using a REQ/REP pattern. Both commands (from client to
server) and returns (from servers to client) are handled in this
way. Once a command is sent from the client to MPI rank 0,
that command is then "broadcasted" from MPI rank 0 to the other
MPI ranks. The method of broadcast is handled by the input
bcaster
. If bcaster="mpi"
, then MPI_bcast
is used to transmit the command. Otherwise (bcaster="zmq"
)
uses ZeroMQ with a PUSH/PULL pattern. The MPI method is probably
epsilon faster, but it will busy-wait. The ZeroMQ bcast method
will not busy wait, in addition to the other benefits ZeroMQ
affords; thus, bcaster="zmq"
is the default.
To shut down the servers and the client, use the command exit()
from the remoter package.
1 2 3 4 5 6 | ## Not run:
library(pbdCS)
pbd_launch_servers()
pbd_launch_client()
## End(Not run)
|
Add the following code to your website.
For more information on customizing the embed code, read Embedding Snippets.