ALIs

kommt noch

Software

Tools and libraries for better and easier use of SuperMUC

Inhalt

Application Software

For an overview of software packages that are available on LRZ systems, see: http://www.lrz.de/services/software/.

Access to software packages

LRZ uses the environment module approach to manage the user environment for different software, library or compiler versions. The distinct advantage of the modules approach is that the user is no longer required to explicitly specify paths for different executable versions, and try to keep the MANPATH and related environment variables coordinated. With the modules approach, users simply "load" and "unload" modules to control their environment. Type

  • module avail

to list all the modules which are available to be loaded. Notice that most of them indicate associated version numbers. Modules make it easy to switch between versions of a package. Specifying a module name without a version number will select the default production version.

Many modules.contain the URL of the LRZ documentation for the specific software package. Type

  • module show <modulename>

and look for the variable which ends with _WWW.

LRZ Tools

To get access to the LRZ Tools insert the following command

module load lrztools

After that the following commands are available

Comand Purpose, details and usage

Information
budget_and_quota Displays the CPU time budget and the file system quotas

Placement of processes and threads
cpuset_query Returns information about the topology, number of core and CPU on which a process can run
get_cpuset_mask Returns a string of 0's and 1's indicating on which (logical) CPUs a process can run
where_do_i_run Returns the CPU-ID  on which the command was run
placementtest-mpi.ibm
placementtest-mpi.intel
placementtest-omp		 Returns information how processes and threads are placed on nodes and CPUs.
Example: 
MP_POCS=5
MP_NODES=2
OMP_NUM_THREADS=10
MP_TASK_AFFINITY=core:$OMP_NUM_THREADS
mpiexec -n 5 placement-test.ibm

Batchjobs

  
llx A better and more comprehensive overview of jobs in the queues, including various sort options.
For details see:  llx -h
myjobs Display all job owned by user in the queues. Can be used as input to build other commands. E.g. llcancel `myjobs` will cancel all job owned by user.
llrun Submit or interactively run a parallel executable. 
Usage : llrun [<options>] <exe> [<user_or_poe_args>]
<options>:
-N - number of nodes (Default: 1)
-n - total number of processes, same as -p (Default: 1)
-P - Task per node
-t - number of threads per process (Default: 1)
-j - jobname
-w,-W - submit batch job with wallclock limit (Default: 02:00:00)
-A - No automatic adjustment of number of nodes (Default: automatic adj.)
-M - MPI Environment (intel|ibm)
-E - copy current environment (COPYALL)
-f - Pin processes and Threads to Fixed physical cores
-b - submit batch job
-c,-C - submit to class (default: test)
-m - email address 
-i - include content of file before parallel execution 
-I - include content of file after parallel execution 
-o - do not run/submit job but save to file 
-h - help (this message)
-v - verbose (Default)
-V - NO verbose
Examples: 
llrun -b -n 320 ./myexe

(runs 320 tasks on 8 Nodes because of automatic adjustment)

llrun -b -N 10 -n 320 ./myexe

(runs 320 tasks on 8 Nodes because of automatic adjustment)

llrun -b -N 10 -P 32 -A ./myexe

(runs 320 tasks on 10 Nodes, no automatic adjustment)

llrun -b -t 2 -n 320 ./myexe

(runs 320 tasks each which 2 threads on 16 Nodes)

llrun -b -n 320 -M intel ./myexe.intel

(runs 320 tasks with an Intel-MPI executable)

llrun -b -n 40 -c test ./myexe

(runs 40 tasks in the test queue)

llrun -b -n 40 -c general ./myexe

(runs 40 tasks in the general production queue)

llrun -n 40 ./myexe

(runs directly 40 tasks using terminal for stdout and sterr)

Programming Environment
MP Displays sorted list of the current settings of the IBM Parallel Environment

LRZ Libraries