# Diff of /trunk/doc/user/execute.tex

revision 2483 by gross, Thu May 14 02:28:58 2009 UTC revision 2484 by gross, Mon Jun 22 04:22:19 2009 UTC
# Line 129  In general a script based on the \escrip Line 129  In general a script based on the \escrip
129  When \MPI is used on more than one process ($\var{nn} \cdot \var{np} >1$) the user needs to keep in mind that several copies of his script are executed at the same time  When \MPI is used on more than one process ($\var{nn} \cdot \var{np} >1$) the user needs to keep in mind that several copies of his script are executed at the same time
130  \footnote{In case of OpenMP only one copy is running but \escript temporarily spawns threads.} while data exchange is performed through the \escript module. At any time,  \footnote{In case of OpenMP only one copy is running but \escript temporarily spawns threads.} while data exchange is performed through the \escript module. At any time,
131  \escript assumes that an argument of the type \var{int}, \var{float}, \var{str}  \escript assumes that an argument of the type \var{int}, \var{float}, \var{str}
132  and \numarray has an identical value across all processors. All  and \numpy has an identical value across all processors. All
133  values of these types returned by \escript have the same value on all processors.  values of these types returned by \escript have the same value on all processors.
134  If values produced by other modules are used as arguments the user has to make sure that the argument values are identical on all processors. For instance, the usage of a random number generator to create argument values bears the risk that the value may depend on the processor.  If values produced by other modules are used as arguments the user has to make sure that the argument values are identical on all processors. For instance, the usage of a random number generator to create argument values bears the risk that the value may depend on the processor.
135
# Line 158  for instance as opening a file for writi Line 158  for instance as opening a file for writi
158  are not automatically made aware of this as \MPI  are not automatically made aware of this as \MPI
159  is not handling exceptions. However, \MPI will terminate the other processes but  is not handling exceptions. However, \MPI will terminate the other processes but
160  may not inform the user of the reason in an obvious way. The user needs to inspect the  may not inform the user of the reason in an obvious way. The user needs to inspect the
error output files to identify the exception.
161    error output files to identify the exception.

Legend:
 Removed from v.2483 changed lines Added in v.2484