File: pvm_spawn.cat

package info (click to toggle)
scilab 2.4-1
  • links: PTS
  • area: non-free
  • in suites: potato, slink
  • size: 55,196 kB
  • ctags: 38,019
  • sloc: ansic: 231,970; fortran: 148,976; tcl: 7,099; makefile: 4,585; sh: 2,978; csh: 154; cpp: 101; asm: 39; sed: 5
file content (62 lines) | stat: -rw-r--r-- 2,356 bytes parent folder | download
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62

pvm_spawn(1)                   Scilab function                   pvm_spawn(1)
NAME
  pvm_spawn - Starts new Scilab processes.

CALLING SEQUENCE
  [tids, numt] = pvm_spawn(task,  ntask, [where])

PARAMETERS

  task : string, which is the file name of the scilab script to be
       started. The Scilab script must already reside on the host on which it
       is to be started.  The name must an absolute path.

  ntask
      : integer, specifying the number of copies of the  scilab script to
      start.

  where
      : string (optional, default value is NULL), can be a host name such as
      ``tequila.ens-lyon.fr'' or a PVM architecture class such as ``SUN4''.

  numt : integer, the actual number of tasks started.  Values less than zero
       indicate a system error.

  tids
      : row of integers, array of the tids of the PVM processes started by
      this pvm_spawn call.

DESCRIPTION
  pvm_spawn starts ntask copies of the scilab script task.  On systems that
  support environment, spawn passes selected variables from parent environ-
  ment 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.:

          setenv DISPLAY myworkstation:0.0
          setenv MYSTERYVAR 13
          setenv PVM_EXPORT DISPLAY:MYSTERYVAR

  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.

  If pvm_spawn starts one or more tasks, numt will be the actual number of
  tasks started.  If a system error occurs then numt will be < 0.  If numt is
  less than ntask then some executables have failed to start and the user
  should check the last ntask - numt locations in the tids array which will
  contain error codes (see below for meaning).  The first numt tids in the
  array are always valid.
  When the argument where is set to NULL a heuristic (round-robin assignment)
  is used to distribute the ntask processes across the virtual machine.

  In the special case where a multiprocessor is specified by where, pvm_spawn
  will start all ntask copies on this single machine using the vendor's
  underlying routines.

EXAMPLE
  [tids, numt] = pvm_spawn("foo.sci",2,"loop")

SEE ALSO
  pvm, pwm_spawn_independent