How do I set up and run a Abaqus batch job?

Please note: The FAQ pages at the HPCVL website are continuously being revised. Some pages might pertain to an older configuration of the system. Please let us know if you encounter problems or inaccuracies, and we will correct the entries.

In most cases, you will run Abaqus on the HPCVL machines in batch mode. Since you have to have access to Abaqus outside of the HPCVL license, most interactive work can be done elsewhere, whereas the computationally intensive runs can be executed on the cluster.

Production jobs are submitted on the systems via the GridEngine, which is a load-balancing software. To obtain details, read our Gridengine FAQ. For a Abaqus batch job, this means that rather than issuing the above commands directly, you wrap it into a GridEngine batch script that looks something like this:

#$ -S /bin/bash
#$ -q abaqus.q
#$ -l qname=abaqus.q
#$ -V
#$ -cwd
#$ -be
#$ -M {email}
# Defining output file
#$ -o {output}
#$ -e {error}
export PATH="/opt/abaqus/6.11/Commands":$PATH
export PATH="/bin":$PATH
source /opt/ics/bin/ intel64
abaqus job={name} input={input} scratch=/scratch/{username} -interactive

This script needs to be altered by replacing all the relevant items enclosed in curly brackets by the right values. The interactive option is necessary; without it the program will not start properly. The script can be submitted to the GridEngine by typing, e.g.

Note that Abaqus needs to be set up correctly before submitting this script, as it inherents the settings of the submitting shell.

The advantage to submit jobs via a load balancing software is that the software will automatically find the resources required and put the job onto a set of processors that have a low load. This will help executing the job faster. Note that the usage of Gridengine for all production jobs on the HPCVL clusters is mandatory. Production jobs that are submitted outside of the load balancing software will be terminated by the system administrator.