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. See these release notes for features.
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 g16.
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 g16. Standard output should be caught in a log-file. We suggest you use the extensions .g16 for input files and .log for results.
Interactively, the command line to invoke Gaussian is thus:
g16 < test.g16 >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. Here is a small sample input file for test purposes:
%mem=512MB #B3LYP/6-31G* opt Test calculation 0 1 H1 O2 H1 R H3 O2 R H1 A R 1.1 A 107.
Important: Since Gaussian has recently moved from Solaris to Linux, the above command will work only on the Linux login node swlogin1, not (as before) on the Solaris-based sflogin0.
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 #$ -V #$ -cwd #$ -q abaqus.q #$ -l qname=abaqus.q #$ -M email@example.com #$ -m be #$ -pe glinux.pe 4 #$ -o STD.out #$ -e STD.err . /opt/gaussian/setup.sh g16 < sample.g16 > sample.log
The script (let's call it g16.sh) is submitted by the qsub command:
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 make sure that you have set up Gaussian (use g16) before you submit a job and that you are working from the Linux logion node swlogin1.
Important: The Gaussian software has recently moved from the Solaris to the Linux platform. Submission of jobs must be done from swlogin1, not from sflogin0.
Migration from Sparc/Solaris
Until August 2016, the Gaussian software was being run on the Sparc/Solaris platform, on our M9000 servers (specifically, m9k0002) which are now de-commissioned. The following is a list of changes that took place when running on the x86/Linux platform.
Gaussian is a licensed program. The license held by the Centre for Advanced Computing is limited to our computers at our main site. That means that any of our users can use the program on our machines (but nowhere else), whether they are located at Queen's or not.
We require 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 ?