Gaussian

Gaussian is a computational chemistry application produced by Gaussian, Inc.

License limitations

Compute Canada currently supports Gaussian only on Graham and certain legacy systems.

In order to use Gaussian you must agree to the following:

1. You are not a member of a research group developing software competitive to Gaussian.
2. You will not copy the Gaussian software, nor make it available to anyone else.
3. You will properly acknowledge Gaussian Inc. and Compute Canada in publications.
4. You will notify us of any change in the above acknowledgement.

If you do, please send an email with a copy of those conditions, saying that you agree to them, to support@computecanada.ca. We will then grant you access to Gaussian.

Running Gaussian on Graham

Gaussian g09.e01 and g16.a03 are installed on Graham cluster and available through the modules system. You can load them using either of

[name@server ~]$ module load gaussian/g16.a03

[name@server ~]$ module load gaussian/g09.e01

Job submission

Graham uses the Slurm scheduler; for details about submitting jobs, see Running jobs.

Besides your input file (in our example name.com), you have to prepare a job script to define the compute resources for the job; both input file and job script must be in the same directory.

There are two options to run your Gaussian job on Graham based on the size of your job files:

• g16 or g09 for regular size jobs
• G16 ou G09 for large jobs

g16 (or g09) for regular size jobs

This option will save the runtime files (.rwf, .inp, .d2e, .int, .skr) to local scratch (/localscratch/username/) on the compute node where the job was scheduled to. The files on local scratch will be deleted by the scheduler afterwards; to keep trace of them we recommend that users note the computer node number.

The following example is a g16 job script; for a g09 job, simply change g16 to g09.

Note that for coherence, we use the same name for each files, changing only the extension (name.sh, name.com, name.log)."

File : mysub.sh

#!/bin/bash
#SBATCH --mem=16G             # memory, roughly 2 times %mem defined in the input name.com file
#SBATCH --time=02-00:00       # expect run time (DD-HH:MM)
#SBATCH --cpus-per-task=16    # No. of cpus for the job as defined by %nprocs in the name.com file
module load gaussian/g16.a03
g16 < name.com >& name.log   # g16 command, input: name.com, output: name.log

You can modify the script to fit your job's requirements for compute resources.

G16 (or G09) for large size jobs

localscratch is ~800G shared by any jobs running on the node. If your job files are bigger than or close to that size range, you would instead use this option to save files to your /scratch. However it's hard for us to define what size of job is considered as a large job because we cannot predict how many jobs will be running on a node at certain time, how many jobs may save files and the size of the files to /localscratch. It is however possible to have multiple Gaussian jobs running on the same node sharing the ~800G space.

G16 provides a better way to manage your files as they are located within the /scratch/username/jobid/ directory, and it's easier to locate the .rwf file to restart a job in a later time.

The following example is a G16 job script; for a G9 job, simply change G16 to G09.

File : mysub.sh

#!/bin/bash
#SBATCH --mem=16G             # memory, roughly 2 times %mem defined in the input name.com file
#SBATCH --time=02-00:00       # expect run time (DD-HH:MM)
#SBATCH --cpus-per-task=16    # No. of cpus for the job as defined by %nprocs in the name.com file
module load gaussian/g16.a03
 G16 name.com                # G16 command, input: name.com, output: name.log by default

Interactive jobs

You can run interactive Gaussian job for testing purpose on Graham. It's not a good practice to run interactive Gaussian jobs on a login node. You can start an interactive session on a compute node with salloc, the example for an hour, 8 cpus and 10G memory Gaussian job is like Goto the input file directory first, then use salloc command:

[name@server ~]$ salloc --time=1:0:0 --cpus-per-task=8 --mem=10g

Then use either

[name@server ~]$ module load gaussian/g16.a03
[name@server ~]$ G16 g16_test2.com    # G16 saves runtime file (.rwf etc.) to /scratch/yourid/93288/

or

[name@server ~]$ module load gaussian/g16.a03
[name@server ~]$ g16 < g16_test2.com >& g16_test2.log &   # g16 saves runtime file to /localscratch/yourid/