Gaussian can be run in both serial and parallel, via shared memory,
through LoadLeveler on the IBM Regatta and IBM SP.
The following sections
demonstrate how to run Gaussian03 in parallel and serial in both interactive
and batch modes.
The script qg03 described below was created by the user support
staff to make running Gaussian easier. This script is not part of the
original Gaussian distribution.
IBM Regatta: The Gaussian scratch directory is set automatically on the
Regatta. Please DO NOT set the environment variable GAUSS_SCRDIR on
the Regatta.
On the IBM SP the scratch directory where Gaussian stores temporary files can
be specified in two different ways.
where scr_directory is the directory you want Gaussian to use for the
temporary files.
If the GAUSS_SCRDIR environment variable has been set, then the script
will not create a temporary file in the scratch space, rather the predefined
scratch location will be used.
Note: Setting the GAUSS_SCRDIR environment variable is
particularly useful when one or both of the scratch directories are
unavailable or close to 100% filled.
where input_file is the Gaussian input file and
output_file is the desired name of the output file.
If the GAUSS_SCRDIR environment variable has been set, Gaussian will
use the designated directory for the temporary files.
Please see the General Policies webpage for details about the
policies and time limits for interactive calculations on the IBM Power4.
to the Gaussian input file. This line tells Gaussian that it can use
up to 2 processors. Currently, 4 processors is the limit on the SP.
This is because the winterhawk+ nodes (the
interactive nodes) have 4 processors per node, therefore the maximum
number of processors that can be used with shared memory is 4.
The current limit on the Regatta is 24 processors.
where input_file is the Gaussian input file and
output_file is the Gaussian ouput file name.
If the GAUSS_SCRDIR environment variable has been set, Gaussian will
use the designated directory for the temporary files. Otherwise, the
Gaussian output file, output_file and the temporary files will be
placed in the same directory as the input_file.
Please see the webpage,
http://www.msi.umn.edu/sp/info/policies/#bgjobs for details about the
policies and time limits for interactive calculations on the IBM SP.
where input_file is the Gaussian input file and the options for
the qg03
scripts are given above. When running in parallel the -p option
MUST be set to n > 1, where n is the number of processors.
Notes:
or
where h2o-p is a parallel Gaussian input file.
Remember the maximum number of parallel processors available at this
time (for Gaussian calculations) on the IBM SP, winterhawk+ nodes and on the
nighthawk nodes, is 4.
Guassian can be run in both serial and parallel (via shared memory)
through PBS on the Origin and other Institute machines.
The following sections
demonstrate how to run Gaussian03 in parallel and serial in both interactive
and batch modes.
The scratch directory where Gaussian stores temporary files can be specified
in two different ways.
where scr_directory is the directory you want Gaussian to use for the
temporary files.
If the GAUSS_SCRDIR environment variable has been set, then the scripts
will not create a temporary file in the scratch space.
where input_file is the Gaussian input file and the options for
the qg03
scripts are given above.
Notes:
Gaussian assumes that the amount of memory specified with the %mem keyword is a
per processor limit, whereas the -m flag designates the total amount
of memory. Therefore, Gaussian will use %mem * %nproc of total memory.
or
where h2o-p is a parallel Gaussian input file.
The Gaussian input file should contain the lines
%mem=200Mb
Notes:
Gaussian assumes that the amount of memory specified with the %mem keyword is a
per processor limit, whereas the -m flag designates the total amount
of memory. Therefore, Gaussian will use %mem * %nproc of total memory.
The default is 64Mb per processor. Hence, you will have to specify the
-m flag for jobs with 3 or more processors when using the default
amount of memory.
Please direct questions or problems to
help@msi.umn.edu
LoadLeveler: (IBM Regatta and IBM SP)
Introduction
Setting the Scratch Directory
setenv GAUSS_SCRDIR scr_directory
Interactive running of g03
Running g03 in serial:
module load g03
g03 < input_file > output_file
Run a Gaussian 03 calculation with the input file h2o and return
the output file h2o.out to the current working directory.
g03 < h2o > h2o.out
Running g03 in parallel:
module load g03
%nproc=2
g03 < input_file > output_file
Run a Gaussian 03 calculation with the parallel (%nproc=2) input file
h2o-p and return the output file
h2o-p.out to the current working directory.
g03 < h2o-p > h2o-p.out
Running g03 in parallel
module load g03
qg03 [options] -p n input_file
line to the
Gaussian input file, where n is the number of processors to be
used by Gaussian.
%nproc=n
qg03 -p 2 h2o-p
qg03 -r yes -p 2 -n winter -s scratch1 -t 5:00:00 h2o-p
qg03 -p 2 -t 12:00:00 -s scratch2 -n night h2o-p
qg03 -p 4 -n night -t 24:00:00 h2o-p
PBS: (SGI, Sun)
Introduction
Setting the Scratch Directory
setenv GAUSS_SCRDIR scr_directory
Running g03 in parallel
module load g03
qg03 [options] input_file
line to the
Gaussian input file, where n is the number of processors to be
used by Gaussian.
%nproc=n
-m = %nproc * %mem + 200mb
qg03 h2o-p
qg03 -r yes -m 500MB -p 2 -t 5:00:00 h2o-p
%nproc=2
qg03 -p 4 -m 2000Mb -t 24:00:00 h2o-p
line to the
Gaussian input file, where n is the number of processors to be
used by Gaussian.
%nproc=n
-m = %nproc * %mem + 200mb
The University of Minnesota is an equal opportunity educator and employer.
This information is available in alternative formats upon request by individuals with disabilities. Please send email to alt-format@msi.umn.edu or call 612-624-0528. |
||||||||||||
|
HOME |
QUESTIONS |
FEEDBACK |
||||||||||||
|
||||||||||||