/[escript]/trunk/doc/user/execute.tex
ViewVC logotype

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

Parent Directory Parent Directory | Revision Log Revision Log | View Patch Patch

revision 2316 by gross, Thu Mar 19 01:22:15 2009 UTC revision 2331 by jfenwick, Mon Mar 23 01:18:21 2009 UTC
# Line 2  Line 2 
2  \label{EXECUTION}  \label{EXECUTION}
3    
4  \section{Overview}  \section{Overview}
5  A typical way of starting your {\it escript} script \file{myscript.py} is done through  A typical way of starting your {\it escript} script \file{myscript.py} is with the \program{escript} command\footnote{The \program{escript} launcher is not supported under \WINDOWS yet.}:
6  \begin{verbatim}  \begin{verbatim}
7  escript myscript.py  escript myscript.py
8  \end{verbatim}  \end{verbatim}
9  as already shown in section~\ref{FirstSteps}\footnote{It is assumed that your \program{escript} is included in your \env{PATH} environment. See installation guide for details.}  as already shown in section~\ref{FirstSteps}\footnote{For this discussion, it is assumed that \program{escript} is included in your \env{PATH} environment. See installation guide for details.}
10  \footnote{The \program{escript} launcher is not supported under \WINDOWS yet.}. In some cases  . In some cases
11  it can be useful to interactively work e.g. when debugging a script with the command  it can be useful to work interactively e.g. when debugging a script, with the command
12  \begin{verbatim}  \begin{verbatim}
13  escript -i myscript.py  escript -i myscript.py
14  \end{verbatim}  \end{verbatim}
15  the script \var{myscript.py} is processed and after completion or if an error occured the  This will execute \var{myscript.py} and when it completes (or an error occurs), a \PYTHON prompt will be provided.
16  \program{escript} will remain in the \PYTHON prompt. To leave the prompt press \kbd{Control-d}.  To leave the prompt press \kbd{Control-d}.
17    
18  To start  To start
19  \program{escript} using four threads (eg. if you use a multi-core processor) you can use  \program{escript} using four threads (eg. if you use a multi-core processor) you can use
20  \begin{verbatim}  \begin{verbatim}
21  escript -t 4 myscript.py  escript -t 4 myscript.py
22  \end{verbatim}  \end{verbatim}
23  This will require {\it escript} to be compiled for \OPENMP.  This will require {\it escript} to be compiled for \OPENMP\cite{OPENMP}.
24    
25  To start \program{escript} using \MPI with 8 processors you use  To start \program{escript} using \MPI\cite{MPI} with $8$ processes you use
26  \begin{verbatim}  \begin{verbatim}
27  escript -n 8 myscript.py  escript -p 8 myscript.py
28  \end{verbatim}  \end{verbatim}
29  If the processors which are used are multi--core processors or multi--processor shared memory archtiectures you can use threading in addition to \MPI. For instance to run $8$ \MPI processors with using $4$ threads each you use the command  If the processors which are used are multi--core processors or multi--processor shared memory archtiectures you can use threading in addition to \MPI. For instance to run $8$ \MPI processes with using $4$ threads each, you use the command
30  \begin{verbatim}  \begin{verbatim}
31  escript -n 8 -t 4 myscript.py  escript -p 8 -t 4 myscript.py
32  \end{verbatim}  \end{verbatim}
33  Alternatively one can use $4$ \MPI processors on each of the $8$ compute nodes through the command  In the case of a super computer or a cluster, you may wish to distribute the workload over a number of nodes\footnote{For simplicity, we will use the term node to refer to either a node in a super computer or an individual machine in a cluster}.
34    For example, to use $8$ nodes, with $4$ \MPI processes per node, write
35  \begin{verbatim}  \begin{verbatim}
36  escript -n 8 -s 4 myscript.py  escript -n 8 -p 4 myscript.py
37  \end{verbatim}  \end{verbatim}
38  where $4$ now specifies the number of slots per compute node. It is also possible  Since threading has some performance advantages over processes, you may specify a number of threads as well.
39  to combine the usage of slots and threading however. Threading has a  \begin{verbatim}
40  performance advantage over the usage of slots.  escript -n 8 -p 4 -t 2 myscript.py
41    \end{verbatim}
42    This runs the script on $8$ nodes, with $4$ processes per node and $2$ threads per process.
43    
44  \section{Options}  \section{Options}
45  The general form of the \program{escript} launcher is as follows:  The general form of the \program{escript} launcher is as follows:
46    
47  \program{escript}  \program{escript}
48  \optional{\programopt{-n \var{nn}}}  \optional{\programopt{-n \var{nn}}}
49  \optional{\programopt{-s \var{ns}}}  \optional{\programopt{-p \var{np}}}
50  \optional{\programopt{-t \var{nt}}}  \optional{\programopt{-t \var{nt}}}
51  \optional{\programopt{-f \var{hostfile}}}  \optional{\programopt{-f \var{hostfile}}}
52  \optional{\programopt{-x}}  \optional{\programopt{-x}}
# Line 57  The general form of the \program{escript Line 60  The general form of the \program{escript
60  \optional{\var{file}}  \optional{\var{file}}
61  \optional{\var{ARGS}}  \optional{\var{ARGS}}
62    
63  where \var{file} is the name of a script, \var{ARGS} are arguments.  where \var{file} is the name of a script, \var{ARGS} are arguments for the script.
64  The \program{escript} program will import your current environment.  The \program{escript} program will import your current environment variables.
65    If no \var{file} is given, then you will be given a \PYTHON prompt (see \programopt{-i} for restrictions).
66    
67    
68  The options are used as follows:  The options are used as follows:
69  \begin{itemize}  \begin{itemize}
70    
71   \item[\programopt{-n} \var{nn}] the number of compute nodes \var{nn} to be used. The total number of process being used is   \item[\programopt{-n} \var{nn}] the number of compute nodes \var{nn} to be used. The total number of process being used is
72  $\var{nn} \cdot \var{ns}$. This option overwrites the value of the \env{ESCRIPT_NUM_NODES} environment variable. If $\var{nn}>1$ but {\it escript}  is not compiled for \MPI a warning is pronted but execution is continued with $\var{nn}=1$. The default value is 1.  $\var{nn} \cdot \var{ns}$. This option overwrites the value of the \env{ESCRIPT_NUM_NODES} environment variable. If $\var{nn}>1$ but {\it escript}  is not compiled for \MPI a warning is pronted but execution is continued with $\var{nn}=1$. The default value is 1.
73    
74  \item[\programopt{-s} \var{ns}] the number of processor slots per node. This options specifies how many \MPI processors are used on each node. The total number of process being used is  \item[\programopt{-p} \var{np}] the number of processor slots per node. This options specifies how many \MPI processes are used on each node. The total number of process being used is
75  $\var{nn} \cdot \var{ns}$. This option overwrites the value of the \env{ESCRIPT_NUM_SLOTS} environment variable. If $\var{ns}=1$ but {\it escript}  is not compiled for \MPI a warning is printed but execution is continued with $\var{ns}>1$. The default value is 1.  $\var{nn} \cdot \var{np}$. This option overwrites the value of the \env{ESCRIPT_NUM_PROC} environment variable. If $\var{np}>1$ but {\it escript}  is not compiled for \MPI a warning is printed but execution is continued with $\var{np}=1$. The default value is 1.
76    
77   \item[\programopt{-t} \var{nt}] the number of threads used per processor. This options specifies how many threads are used on each node. The option overwrites the value of the \env{ESCRIPT_NUM_THREADS} environment variable. If $\var{nt}>1$ but {\it escript} is not compiled for \OPENMP a warning is printed but execution is continued with $\var{nt}=1$. The default value is 1.   \item[\programopt{-t} \var{nt}] the number of threads used per processes.
78    The option overwrites the value of the \env{ESCRIPT_NUM_THREADS} environment variable.
79    If $\var{nt}>1$ but {\it escript} is not compiled for \OPENMP a warning is printed but execution is continued with $\var{nt}=1$. The default value is 1.
80    
81   \item[\programopt{-f} \var{hostfile}] the name of a file with a list of host names. Some systems require to specify the addresses or names of the compute nodes where \MPI process should be spawned. The list of addresses or names of the compute nodes is listed in the file with the name \var{hostfile}. In order to avoid oversubsription the number of differnt   \item[\programopt{-f} \var{hostfile}] the name of a file with a list of host names. Some systems require to specify the addresses or names of the compute nodes where \MPI process should be spawned. The list of addresses or names of the compute nodes is listed in the file with the name \var{hostfile}. In order to avoid oversubsription the number of differnt
82  hosts defined in \var{hostfile} must be greater or equalt to the number of requsted compute nodes \var{nn}. The option overwrites the value of the \env{ESCRIPT_HOSTFILE} environment variable. By default value no host file is used.  hosts defined in \var{hostfile} must be greater or equal to the number of requsted compute nodes \var{nn}. The option overwrites the value of the \env{ESCRIPT_HOSTFILE} environment variable. By default value no host file is used.
83   \item[\programopt{-c}] prints the information about the settings used to compile {\it escript} and stops execution..   \item[\programopt{-c}] prints the information about the settings used to compile {\it escript} and stops execution..
84   \item[\programopt{-V}] prints the version of {\it escript} and stops execution.   \item[\programopt{-V}] prints the version of {\it escript} and stops execution.
85   \item[\programopt{-h}] prints a help message and stops execution.   \item[\programopt{-h}] prints a help message and stops execution.
86   \item[\programopt{-i}] excutes the script \var{file} and switches to interactive mode after the execution is finished or an exception has occured. This option is useful for debugging a script. The option cannot be used if more then one processor ($\var{nn} \cdot \var{ns}>1$) is used.   \item[\programopt{-i}] excutes the script \var{file} and switches to interactive mode after the execution is finished or an exception has occured. This option is useful for debugging a script. The option cannot be used if more then one process ($\var{nn} \cdot \var{np}>1$) is used.
87    
88   \item[\programopt{-e}] shows additional environment variables and commands used during  \program{escript} execution. This option is useful if users wish to excute scripts without using \program{escript}.   \item[\programopt{-e}] shows additional environment variables and commands used during \program{escript} execution. This option is useful if users wish to excute scripts without using the \program{escript} command.
89    
90   \item[\programopt{-o}] switches on the redirection of standart and error output of processors with \MPI rank greater than zero to the files \file{stdout_\var{r}.out} and \file{stderr_\var{r}.out} where \var{r} is the rank of the processor. The option overwrites the value of the \env{ESCRIPT_STDFILES} environment variable   \item[\programopt{-o}] switches on the redirection of standart and error output of processors with \MPI rank greater than zero to the files \file{stdout_\var{r}.out} and \file{stderr_\var{r}.out} where \var{r} is the rank of the processor. The option overwrites the value of the \env{ESCRIPT_STDFILES} environment variable
91    
92   \item[\programopt{-x}] uses \var{file} as an \esysxml.    %  \item[\programopt{-x}] interpret \var{file} as an \esysxml \footnote{{\it esysxml} has not been released yet.} task.
93  This option is still expermental.  % This option is still expermental.
94    
95   \item[\programopt{-v}] prints some diagonstic information.   \item[\programopt{-v}] prints some diagonstic information.
96  \end{itemize}  \end{itemize}
97    
98  \section{Input and Output}  \section{Input and Output}
99  The \program{escript} launcher can be run in the interactive mode, i.e.  When \MPI is used on more than one process ($\var{nn} \cdot \var{np} >1$) no input from the standard input is accepted. Standard output on any process other the the master process (\var{rank}=0) will not be available.
100  \programopt{-i} or no script name \var{file} is given, if used on a single processor (possibly with several threads). When \MPI is used on more than one processor ($\var{np} \cdot \var{ns} >1$) no input from the standart input is excepted. Standart output on any processor other the the master processor (\var{rank}=0) will not be available. Error output from any processor will be redirected to the node where \program{escript} has been envoked. If the \programopt{-o} or \env{ESCRIPT_STDFILES} is set the standart and error output from any processor other the the master processor will be written  Error output from any processor will be redirected to the node where \program{escript} has been envoked.
101  to files of the names \file{stdout_\var{r}.out} and \file{stderr_\var{r}.out} where  If the \programopt{-o} or \env{ESCRIPT_STDFILES} is set\footnote{That is, it has a non-empty value.}, then the standard and error output from any process other than the master process will be written to files of the names \file{stdout_\var{r}.out} and \file{stderr_\var{r}.out} (where
102  \var{r} is the rank of the processor.  \var{r} is the rank of the process).
103    
104  If files are created or read by individual \MPI processors with information local to the processor (e.g in the \function{dump} function)  and more than one processor is used ($\var{np} \cdot \var{ns} >1$), file names are extended by the \MPI processor rank. This will avoid problems if processors are using a shared file system. Files which collect data which are global for all \MPI processors will created on the processor with \MPI rank 0 only. Users should keep in mind that if the file system is not shared a file containing global information  If files are created or read by individual \MPI processes with information local to the process (e.g in the \function{dump} function)  and more than one process is used ($\var{nn} \cdot \var{np} >1$), the \MPI process rank is appended to the file names.
105    This will avoid problems if processes are using a shared file system.
106    Files which collect data which are global for all \MPI processors will created by the process with \MPI rank 0 only.
107    Users should keep in mind that if the file system is not shared, then a file containing global information
108  which is read by all processors needs to be copied to the local file system before \program{escript} is invoked.  which is read by all processors needs to be copied to the local file system before \program{escript} is invoked.
109    
110    

Legend:
Removed from v.2316  
changed lines
  Added in v.2331

  ViewVC Help
Powered by ViewVC 1.1.26