Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 7 Next »

Introduction

TCP Linda is a parallel execution environment to parallelize Gaussian jobs.  By default, Gaussian jobs are single processor core jobs.  TCP Linda must be used to to parallelize Gaussian.  In order to use TCP Linda you must configure your Gaussian input file to use multiple processors (and possibly multiple nodes).  For multiple node jobs this requires that you know which nodes you will be running on.  However, this information is not known ahead of time.  We have developed a script that will configure your job for you.  Please follow the instructions below.

Linda not available on all systems

Linda is not available on all of our systems. 

Configure Gaussian

In order to run a Gaussian job on our clusters you must first load the Gaussian module:

Subsequently, you should source the Gaussian command file to set up your environment:

tcsh users:

bash users:

Build Your Gaussian Job

You must have a Gaussian input file.  For our example we will use a file called example.gjf.

This input file must have, as its first lines, the number of processors per node and a list of the node names.  An example is shown in the Linda documentation.

An example of these lines looks like this (taken from the Linda documentation)

As stated previously, the node names for your job will not be known ahead of time. So this must be configured dynamically. To build your job submission script such that these jobs can be configured dynamically, use the following command:

Using our example input file example.gjf and 6 nodes, the command would look like this:

This will create a PBS job script named example.pbs in your current working directory, using example.gjf as the input file and using 6 nodes.  It will build a submission script that will set the Gaussian parameters necessary to run the parallel job.

To submit the job, simply use qsub as follows:

Check the contents of the job submission script for the location of your scratch directory (GAUSS_SCRDIR) and the location of your output file.

  • No labels