Gaussian is arguably the most commonly used computational quantum-chemistry program. It offers a wide range of features on the field of computational chemistry, ranging from atomic and molecular structure to thermochemical computations. A list of these features can be found here.
Gaussian does electronic-structure calculations and standard quantum chemical calculations. Among the methods available are simple molecular mechanics (such as Amber force field), semi-empirical methods (such as CNDO), Hartree-Fock (restricted and unrestricted), MPn (Mollar-Plesset perturbation theory of order n=2,3,4), CI (Configuration-Interaction), CC (Coupled-Cluster), Multi-configurational SCF (such as CAS-SCF) and various DFT (Density-Functional Theory) methods. Specific to Gaussian are high-accuracy energy methods (G2, CBS). It can be used to obtain electronic properties, molecular geometries, vibrational frequencies, orbitals, reaction profiles, and much more. Check out the capabilities here.
Location of the program and setup
The program resides in /opt/gaussian. Multiple versions and revisions of the program are located in different sub-directories. The name of the root executable is g09.
The source code of Gaussian is not publicly accessible since Gaussian is a licensed product. However, Gaussian grants the permission to alter the code under certain conditions. If you want to do so, contact us to learn more. You are not allowed to copy the executable or any part of the distribution onto your local machine.
At present, we are using the usepackage system to set up Gaussian. This means that typing
is automatically adding all required settings to your shell set-up.
One of the settings is the environment variable GAUSS_SCRDIR which is required to redirect the temporary files that Gaussian uses to the proper scratch space, presently
where hpcXXXX stands for your username. If for some reason Gaussian does not terminate normally (e.g. a job gets cancelled), it leaves behind large scratch files which you may have to delete manually. To check if such files exist, type
ls -lt /scratch/hpcXXXX
Once you have determined that the scratch files are no longer needed (because the program that used them is not running any more), you can delete them by typing
Cleaning up the scratch space is the user's responsibility. If it is not done regularly, it can cause jobs to terminate, and much work to be lost.
Running Gaussian from a command line
To run Gaussian on our systems, you have to belong to a user group g98 (it's called that for historical reason, but it applies to all versions of Gaussian). You need to read our license agreement and signed a statement to be included in this user group. Once you are, you can access the executables.
A computation is performed by preparing an input file and pipe it to standard input of the program g09. Standard output should be caught in a log-file. We suggest you use the extensions .g09 for input files and .log for results.
Interactively, the command line to invoke Gaussian is thus:
g09 < test.g09 >test.gout
This will only work if you are a member of the g98 group and have set the environment correctly. Note that the interactive execution of Gaussian is only meant for test runs.
Gaussian input files are explained in the "User's Reference". It is impossible to give an outline here. Sample files can be found in
Note: It is absolutely essential to have a good idea about the size and complexity of your calculations before you start a Gaussian job. Many of the methods mentioned above have terrible scaling properties, i.e. the computational cost grows very quickly with the number of electrons, degrees of freedom, or number of basis functions used. We suggest you start with a small basis set and a cheap method, and then slowly increase those parameters.
Submitting (parallel) Gaussian jobs
If you want to run Gaussian on several processors on our machines, you have to include a line in your input file:
where we assume that you want to use 8 processors (cores, threads).
It is mandatory to submit a Gaussian job script through our scheduling software (see our Scheduler Help File for details).
Here is a "bare bones" sample of a Gaussian submission script:
#! /bin/bash #$ -S /bin/bash #$ -cwd #$ -V #$ -M hpcXXXX@localhost #$ -m be #$ -o STD.out #$ -e STD.err #$ -pe gaussian.pe 8 . /opt/gaussian/setup.sh g09 < sample.g09 > sample.log
- In this script, an email address for notifications is specified in the #$ -M line. We suggest to use "hpcXXXX@localhost" (hpcXXXX stands for the username). Place a file .forward containing your actual email address into your home directory.
- The -o and -e lines are used to tell the system where to write "standard output" and "standard error", i.e. the screen output.
- The #$ -pe gaussian.pe 8 line specifies the number of processors the scheduler will allocate. It is crucial to choose the same number as specified in the %nrocs= line of the input file.
- The line . /opt/gaussian/setup.sh does an internal setup for the scheduler and must be included.
Note that we are using a special parallel environment "gaussian.pe" for Gaussian submissions. This will schedule all Gaussian jobs to a dedicated node. The line that sources in "setup.sh" redirects I/O from/to scratch files to a fast local disk. This greatly increases Gaussian performance in some cases and automatically removes scratch file when they are not needed anymore.
Important: Please do not use any PE other than gaussian.pe for Gaussian job submissions and make sure you include the "setup.sh" line.
The script (let's call it g09.sh) is submitted by the qsub command:
- qsub g09.sh
This must be done from the working directory, i.e. the directory that contains the input file and is supposed to contain the output. Also, we assume you are properly set up for Gaussian usage before submitting the script, for instance by typing "use g09".
There is an easier way to do this: We are supplying a small perl script called GaussSubmit that can be called directly, and will ask a few basic questions, such as the name for the job to be submitted and the number of processes to be used in the job. Simply type
and answer the questions. The script expects a Gaussian input file with "file extension" .g09 to be present and will do everything else automatically. This is meant for simple Gaussian job submissions. More complex job submissions are better done manually.
How is Gaussian licensed?
Gaussian is a licensed program. The license held by HPCVL is limited to the HPCVL-operated computers at our main site. That means that any user of HPCVL can use the program on our machines (but nowhere else), whether they are located at Queen's or not.
HPCVL requires users of Gaussian to sign a statement in which they state that they are informed about the terms of the license to be included in the Gaussian user group named "g98". Please fax the completed statement to (613) 533-2015 or scan/email to firstname.lastname@example.org.
Where can I get more detailed information?
This is the most important question treated here. To learn the basics about Gaussian input and output, refer to the Gaussian 09 User's Reference. For templates, and to get many examples, check out /opt/gaussian/g09/bsd/examples.
There is a Gaussian web page with lots of information. Gaussian also operates a help line for licensed users. Send email to email@example.com, but don't expect the answer to come too quick, they get a lot of requests.
For hardcore computational chemists, there is the "Gaussian 09 Programmer's Reference" and the IOPs Reference which are useful if you want to tinker with default settings and internal parameters, or even want to write some subroutines of your own. These can be purchased from Gaussian Inc..