Software skeleton-page

Name
module load	kat/name
License	e.g. GPL
Citing
Links	Homepage; Documentation
Graphical Interface	No (Yes)
Included in module

Description

Programname is used for worbeling the worbels. It makes use of advanced flubberdiflaps .

Versions and Availability

A current list of the versions available on the bwUniCluster and bwForclusters can be obtained from the Cluster Information System: CIS Information on Programname

On the commandline of the the bwUni or bwFor clusters, you can get a list of the available i versions using

module avail kat/programname

Usage

Loading the module

You can load the default version of dacapo with the command

module load kat/programname

The module will try to load modules it needs to function (e.g. compiler/intel). If loading the module fails, check if you have already loaded one of those modules, but not in the version needed for dacapo.

If you wish to load a specific (older) version, you can do so using e.g.

module load kat/programname/0.0.0

to load the version 0.0.0

Disk Usage

Scratch files are written to the current directory by default. Please change to a local directory before starting your calculations. For example

mkdir -p /tmp/$USER/job_sub_dir 
cd /tmp/$USER/job_sub_dir 

In case of multi-node parallel jobs, you might need to create the directory on all nodes used.

Examples

You can copy a simple interactive example to your home directory and run it, using:

mkdir ~/PROGRAMNAME-examples/
cp -r $PROGRAMNAME_EXA_DIR/ ~/PROGRAMNAME-examples/
cd ~/PROGRAMNAME-examples/
blabla

Version-Specific Information

For information specific to a single version, see the information available via the module system with the command

module help kat/programname