Software skeleton-page: Difference between revisions
mNo edit summary |
|||
| Line 1: | Line 1: | ||
<!-- |
<!-- |
||
Minimum-Breite sollte nicht unter 600px sein. Sind die Zeilen breiter, dann die |
Minimum-Breite sollte nicht unter 600px sein. Sind die Zeilen breiter, dann die |
||
'width=600px'-Zeile loeschen oder anpassen. |
'width=600px'-Zeile loeschen oder anpassen (also vergroessern). |
||
class="wikitable" unbedingt so lassen! |
class="wikitable" unbedingt so lassen! |
||
| Line 8: | Line 8: | ||
| = Pipe-Zeichen |
| = Pipe-Zeichen |
||
Interne Verlinkungen benutzen. Syntax: [[#Ueberschrift|Link-Text]] |
|||
--> |
--> |
||
{| width=600px class="wikitable" |
{| width=600px class="wikitable" |
||
| Line 18: | Line 21: | ||
| Availability |
| Availability |
||
| [[bwUniCluster]] | [[BwForCluster_Chemistry]] |
| [[bwUniCluster]] | [[BwForCluster_Chemistry]] |
||
<!-- Verfuegbare Cluster (soweit bekannt): |
|||
[[bwUniCluster]] [[bwForCluster ENM]], [[bwForCluster MLS/WISO]], [[BwForCluster_Chemistry]], [[bwForCluster BinAC]] --> |
|||
|- |
|- |
||
| License |
| License |
||
| Line 28: | Line 32: | ||
|- |
|- |
||
| Links |
| Links |
||
| [https://some.homepage.edu SW-Homepage] | [https://some.otherpage.TLD some other pages] |
| [https://some.homepage.edu SW-Homepage] | [https://some.otherpage.TLD some other pages] | [https://some.homepage.edu SW-Documentation] |
||
|- |
|- |
||
| Graphical Interface |
| Graphical Interface |
||
| No | Yes <!-- |
| No | Yes <!-- Links zur Hardcopy, Beschreibung (X-forwardung, ssh -X ... --> |
||
|- |
|- |
||
| Included in module |
| Included in module |
||
| Line 37: | Line 41: | ||
<!-- e.g.: mpi/openmpi/1.6.5-gnu-4.8 |
<!-- e.g.: mpi/openmpi/1.6.5-gnu-4.8 |
||
mention if there is more than one software in the module, i.e. icc, ifort and debugger --> |
mention if there is more than one software in the module, i.e. icc, ifort and debugger --> |
||
|- |
|||
| Updates... |
|||
| Any other infos... |
|||
|} |
|} |
||
| Line 42: | Line 49: | ||
'''Softwarename''' is used for worbeling the worbels. It makes use of advanced flubberdiflaps . |
'''Softwarename''' is used for worbeling the worbels. It makes use of advanced flubberdiflaps . |
||
<br> |
<br> |
||
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. |
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. |
||
<br> |
<br> |
||
<br> |
<br> |
||
= Versions and Availability = |
= Versions and Availability = |
||
A list of versions currently available on all bwHPC-C5-Clusters can be obtained from the |
A list of versions currently available on all bwHPC-C5-Clusters can be obtained from the |
||
| Line 78: | Line 83: | ||
</pre> |
</pre> |
||
<br> |
<br> |
||
= License = |
= 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) |
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) |
||
| Line 87: | Line 91: | ||
<br> |
<br> |
||
<br> |
<br> |
||
= Usage = |
= Usage = |
||
== Loading the module == |
== Loading the module == |
||
| Line 107: | Line 110: | ||
</pre> |
</pre> |
||
<br> |
<br> |
||
== Program Binaries == |
== Program Binaries == |
||
Show the location and contents of the installed binaries in the main folder of the software |
Show the location and contents of the installed binaries in the main folder of the software |
||
and show some informations, too. |
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. |
e.g.: After loading the SOFTWARENAME module (''module load category/softwarename/'version''') this path is also set to the local $PATH- and [[#PATH-TO-ENVIRONMENTS-SECTION|$SOFTWARENAME_BIN_DIR]] environments. |
||
<pre> |
<pre> |
||
$ls -F (or ls -x) $SOFTWARE_BIN_DIR |
$ ls -F (or ls -x) $SOFTWARE_BIN_DIR |
||
... list of content of software-bin-dir ... |
... list of content of software-bin-dir ... |
||
$ |
$ |
||
| Line 121: | Line 122: | ||
<br> |
<br> |
||
<br> |
<br> |
||
== Disk Usage / Workspaces == |
== Disk Usage / Workspaces == |
||
Scratch files are written to the current directory by default. |
Scratch files are written to the current directory by default. |
||
| Line 135: | Line 135: | ||
<br> |
<br> |
||
'calc_repo' is an example name of a repository you created by using the command 'ws_allocate'. |
'calc_repo' is an example name of a repository you created by using the command 'ws_allocate'. |
||
<br> |
|||
<pre> |
<pre> |
||
$ cd $(ws_find calc_repo) |
$ cd $(ws_find calc_repo) |
||
| Line 142: | Line 142: | ||
['your-id'-calc_repo-0]$ |
['your-id'-calc_repo-0]$ |
||
</pre> |
</pre> |
||
<br> |
|||
In case of multi-node parallel jobs, you might need to create the directory on all nodes used. |
In case of multi-node parallel jobs, you might need to create the directory on all nodes used. |
||
<br> |
<br> |
||
<br> |
<br> |
||
= Moab Submit Examples = |
= Moab Submit Examples = |
||
You can copy a simple interactive example to your '''workspace''' and run it, using 'msub' |
You can copy a simple interactive example to your '''workspace''' and run it, using 'msub' |
||
| Line 160: | Line 159: | ||
</pre> |
</pre> |
||
<br> |
<br> |
||
= Software-Specific Environments = |
= Software-Specific Environments = |
||
To see a list of all SOFTWARENAME environments set by the 'module load'-command use 'env | grep SOFTWARENAME'<br> |
To see a list of all SOFTWARENAME environments set by the 'module load'-command use 'env | grep SOFTWARENAME'<br> |
||
or the command 'module display category/softwarename/version' (you don't need to load the module before!). |
or the command 'module display category/softwarename/version' (you don't need to load the module before!). |
||
<pre> |
<pre> |
||
# EXAMPLE ONLY |
# EXAMPLE ONLY |
||
| Line 177: | Line 174: | ||
</pre> |
</pre> |
||
<br> |
<br> |
||
= Version-Specific Information = |
= 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 |
For a more detailed information specific to a specific SOFTWARENAME version, see the information available via the module system with the command |
||
| Line 215: | Line 211: | ||
[...] |
[...] |
||
</pre> |
</pre> |
||
<br> |
|||
<!-- ==================================================== |
<!-- ==================================================== |
||
remove comment to put page in category |
remove comment to put page in category |
||
Revision as of 15:49, 16 December 2015
| Description | Content |
|---|---|
| module load | category/name (e.g. chem/orca) |
| Availability | bwUniCluster | BwForCluster_Chemistry |
| License | Link to SW-license-page, GPL ... License |
| Citing | Citing-informations here oder [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... | Any other infos... |
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.
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!
{{#widget:Iframe
|url=https://cis-hpc.uni-konstanz.de/prod.cis/bwUniCluster/chem/gromacs
|width=90%
|height=320
|border=0
}}
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
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
Usage
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.
# EXAMPLE! $ 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
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...
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 /work/workspace/scratch/'your-id'-calc_repo-0 ['your-id'-calc_repo-0]$
In case of multi-node parallel jobs, you might need to create the directory on all nodes used.
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
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!).
# EXAMPLE ONLY $ module load chem/orca/3.0.3 $ env | grep ORCA ORCA_VERSION=3.0.3 ORCA_MAN_DIR=/opt/bwhpc/common/chem/orca/3.0.3/manual ORCA_EXA_DIR=/opt/bwhpc/common/chem/orca/3.0.3/bwhpc-examples ORCA_BIN_DIR=/opt/bwhpc/common/chem/orca/3.0.3 ORCA_HOME=/opt/bwhpc/common/chem/orca/3.0.3 $
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'
: EXAMPLE ONLY !!!
$ 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'
[...]
Documentation:
* Max-Planck-Institut fuer Chemische Energiekonversion
https://cec.mpg.de/forum/portal.php
* New features for version 3.0.1
https://cec.mpg.de/forum/portal.php#a3
* Manuals in pdf format:
/opt/bwhpc/common/chem/orca/3.0.1/manual
* Example data and a Moab example script can be found here:
/opt/bwhpc/common/chem/orca/3.0.1/bwhpc-examples
[...]