Software skeleton-page - bwHPC Wiki Software skeleton-page - bwHPC Wiki

Software skeleton-page

From bwHPC Wiki
Jump to: navigation, search
Description Content
module load category/name (e.g. chem/orca)
Availability bwUniCluster | BwForCluster_Chemistry | bwForCluster MLS&WISO
License Link to SW-license-page, GPL ... License
Citing-informations here

or [link to citing-information or citing-description]

Links SW-Homepage | some other pages | SW-Documentation
Graphical Interface No | Yes
Included in module catetgory/module/name-dependance | some/more/modules-here
Updates/News Any other infos.... What's new!

1 Description

Softwarename is used for worbeling the worbels. It makes use of advanced flubberdiflaps .
This paragraph should give a short description of what the software does and should enable potential new users to decide if this is the software that might help them with their project.

2 Versions and Availability

A list of versions currently available on all bwHPC-C5-Clusters can be obtained from the

Cluster Information System CIS
Include a direct link to the description in CIS here and remove this line!
Show a list of available versions using 'module avail category/softwarename' on any HPC-C5 cluster.

: EXAMPLE with Gromacs on the bwUniCluster
$ module avail chem/gromacs
------------------------ /opt/bwhpc/common/modulefiles -------------------------
chem/gromacs/4.5.3_gridcount-1.4 chem/gromacs/5.0
chem/gromacs/4.6.2(default)      chem/gromacs/5.0.2
chem/gromacs/4.6.5               chem/gromacs/5.0.5

3 License

Anything specific to the licensing model goes here. If the Program is GPL or one of the over very common free software licenses, you can probably remove this section. Things that should be mentioned here (if they apply) - does the software use a license server - if yes, how many concurrent licenses can we use - are there other restrictions on the license (most proprietary software run on Universitiescan only be used for non-commercial research or teaching purposes) - Do any other restrictions apply

4 Usage

4.1 Loading the module

You can load the default version of software name with the command 'module load category/softwarename'. Example:

$ module load category/softwarename

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 software name. If you wish to load a specific (older) version, you can do so using e.g. $ module load category/softwarename/'version' to load the version you desires.

$ module avail chem/orca
------------------------ /opt/bwhpc/common/modulefiles -------------------------
chem/orca/3.0.1 chem/orca/3.0.3
$ module load chem/orca/3.0.1

4.2 Program Binaries

Show the location and contents of the installed binaries in the main folder of the software and show some informations, too. e.g.: After loading the SOFTWARENAME module (module load category/softwarename/'version') this path is also set to the local $PATH- and $SOFTWARENAME_BIN_DIR environments.

$ ls -F (or ls -x) $SOFTWARE_BIN_DIR
... list of content of software-bin-dir ... 

What-is-what? Some more explanations here...

4.3 Disk Usage / Workspaces

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 

Better solution: Change to a local directory or to your local workspace (preferred) before starting your calculations.
'calc_repo' is an example name of a repository you created by using the command 'ws_allocate'.

$ cd $(ws_find calc_repo)
['your-id'-calc_repo-0]$ pwd

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

5 Moab Submit Examples

You can copy a simple interactive example to your workspace and run it, using 'msub'
Strictly use the $SOFTWARENAME_EXA_DIR environment-variable!

$ cd $(ws_find 'your_repo_name')
$ cp $SOFTWARENAME_EXA_DIR/bwhpc-'softwarename'-example.moab .
$ cp bwhpc-'softwarename'-example.moab my'softwarename'job.moab 
§ vi my'softwarename'job.moab         # do your own modifications
$ msub my'softwarename'job.moab       # start job submission

6 Software-Specific Environments

To see a list of all SOFTWARENAME environments set by the 'module load'-command use 'env | grep SOFTWARENAME'
or the command 'module display category/softwarename/version' (you don't need to load the module before!).

$ module load chem/orca/3.0.3
$ env | grep ORCA

7 Version-Specific Information

For a more detailed information specific to a specific SOFTWARENAME version, see the information available via the module system with the command

$ module help category/softwarename/'version'

For a small abstract what SOFTWARENAME is about use the command

$ module whatis category/softwarename/'version'

$ module avail chem/orca
------------------------------ /opt/bwhpc/common/modulefiles ---------------------------------------
chem/orca/3.0.1 chem/orca/3.0.3

$ module whatis chem/orca/3.0.1
chem/orca/3.0.1      : Quantum chemistry package ORCA, version 3.0.1 
    (command '/opt/bwhpc/common/chem/orca/3.0.1/orca')

$ module help chem/orca/3.0.1
----------- Module Specific Help for 'chem/orca/3.0.1' ------------
This module provides the quantum chemistry package ORCA version 3.0.1
via command '/opt/bwhpc/common/chem/orca/3.0.1/orca' 
*  Max-Planck-Institut fuer Chemische Energiekonversion
*  New features for version 3.0.1
*  Manuals in pdf format:
*  Example data and a Moab example script can be found here: