Applications
From Molecular Modeling Wiki
(→Scope of this page) |
|||
| Line 1: | Line 1: | ||
== General Information == | == General Information == | ||
| - | |||
| - | |||
| - | |||
| - | |||
=== Scope of this page === | === Scope of this page === | ||
The description of applications on this page is valid for newer clusters starting from '''lithium''', through '''uranium''', '''barium''', '''thallium''', and newer. It is also partially valid for '''francium''' and '''helium''', but there may be some differences. | The description of applications on this page is valid for newer clusters starting from '''lithium''', through '''uranium''', '''barium''', '''thallium''', and newer. It is also partially valid for '''francium''' and '''helium''', but there may be some differences. | ||
| + | |||
| + | === Parallel calculations === | ||
| + | |||
| + | Multiprocessor clusters are built to be able to run calculations in a parallel way. However, using parallel calculations on a cluster requires a special approach when integrating parallelized applications with a queueing system, and almost each application needs to be configured and tuned individually. It is necessary to follow strict rules to use the cluster in an efficient way - please read the application notes below to find specific demands of the installed applications. | ||
=== List === | === List === | ||
Revision as of 14:32, 27 March 2009
Contents |
General Information
Scope of this page
The description of applications on this page is valid for newer clusters starting from lithium, through uranium, barium, thallium, and newer. It is also partially valid for francium and helium, but there may be some differences.
Parallel calculations
Multiprocessor clusters are built to be able to run calculations in a parallel way. However, using parallel calculations on a cluster requires a special approach when integrating parallelized applications with a queueing system, and almost each application needs to be configured and tuned individually. It is necessary to follow strict rules to use the cluster in an efficient way - please read the application notes below to find specific demands of the installed applications.
List
Turbomole 5.10 / 6.0 [1]
Turbomole 5.10 / 6.0
The TurboMole program is supplied in a form of binary files (no source code) which are compiled and linked with an HP implementation of MPI libraries, what imposes strict requiements to the environment setup of parallel calculations. TurboMole needs to have some variables defined and files created to be able to run in parallel, especially when parallel run across machines is reqired.
To submit a parallel TurboMole job:
- Copy a sample script /usr/local/programs/common/turbomole/turbomole-5.10/sub/dscf_sample_mp or /usr/local/programs/common/turbomole/turbomole-6.0/sub/dscf_sample_mp to your data directory and rename it.
- Edit the script and modify the part starting with a comment MODIFY HERE; do not modify other parts, unless you know what you do.
- If your TuboMole control file contains $scfintunit section, specify the file location as file=/scratch/<username>/<filename> where <username> is your login name and <filename> is an arbitrary file name. Please note that saving the file into your home directory will most likely lead to a very slow calculation and may even cause entire cluster slowdown.
- Submit the calculation with
qsub -q <queue_name> -pe hpmpi <n> <scriptname>
To submit a single-processor TurboMole job:
- Copy a sample script /usr/local/programs/common/turbomole/turbomole-5.10/sub/dscf_sample_sp or /usr/local/programs/common/turbomole/turbomole-6.0/sub/dscf_sample_sp to your data directory and rename it.
- Edit the script and modify the part starting with a comment MODIFY HERE; do not modify other parts, unless you know what you do.
- If your TuboMole control file contains $scfintunit section, specify the file location as file=/scratch/<username>/<filename> where <username> is your login name and <filename> is an arbitrary file name. Please note that saving the file into your home directory will most likely lead to a very slow calculation and may even cause entire cluster slowdown.
- Submit the calculation with
qsub -q <queue_name> <scriptname>
