- Scilab help
- PVM parallel Toolbox
Please note that the recommended version of Scilab is 2023.1.0. This page might be outdated.
However, this page did not exist in the previous stable version.
Starts new PVM processes.
[tids, numt] = pvm_spawn_independent(task, ntask, [where])
string, which is the executable file name of the PVM process to be started. The executable must already reside on the host on which it is to be started. The name may be a file in the PVM search path or an absolute path. The default PVM search path is $HOME/pvm3/bin/$PVM_ARCH/ .
integer, specifying the number of copies of the executable file to start.
string (optional), can be a host name such as ``tequila.ens-lyon.fr'' or a PVM architecture class such as ``SUN4''.
integer, the actual number of tasks started. Values less than zero indicate a system error.
row of integers, array of the tids of the PVM processes started by this pvm_spawn_independent call.
ntask copies of the executable named
On systems that support environment variables,
pvm_spawn_independent passes selected variables
from parent environment to children tasks. If set, the envar
PVM_EXPORT is passed. If
PVM_EXPORT contains other names
(separated by ':') they will be passed too. This is useful for e.g.:
The hosts on which the PVM processes are started are determined by the
where arguments. On return the array
tids contains the PVM task identifiers for each process started.
pvm_spawn_independent starts one or more tasks,
will be the actual number of tasks started. If a system error occurs
numt will be < 0.
numt is les than
then some executables have failed to start.
The last locations in the
will contain error codes (see below for meaning). Note that the
first tids in the array are always valid.
When the argument
is omitted an heuristic (round-robin assignment) is used to
processes across the virtual machine.
In the special case where a multiprocessor is specified by
pvm_spawn_independent will start all
copies on this single machine using the vendor's underlying routines.
|<< pvm_spawn||PVM parallel Toolbox||pvm_start >>|