Abaqus¶
Abaqus can work in both multithreading and multiprocessing (MPI) modes. Below, you can find examples of submission scripts for both modes.
Multiprocessing job (MPI)¶
1. Load module
The launcher command matches the version you load: abaqus/2024 provides
abq2024, abaqus/2022 provides abq. The associated fe-safe and tosca
tools are available as well.
2. Submit abaqus job
If you want to run Abaqus with multiprocessing on a single node, you can submit the following script:
#!/bin/bash
#
#SBATCH --job-name="SC8R_S1_DMB_R"
#SBATCH --time=108:00:00
#SBATCH --nodes=1
#SBATCH --ntasks-per-node=16
#SBATCH --cpus-per-task=1
#SBATCH --partition=compute
#SBATCH --mem-per-cpu=4GB
#SBATCH --account=research-<faculty>-<department>
#
JOBNAME=SC8R_S1_DMB_R1
module load abaqus/2024
cd $SLURM_SUBMIT_DIR
TMP=$SLURM_SUBMIT_DIR/results_$JOBNAME
mkdir -p $TMP
cp $JOBNAME.inp $JOBNAME.py $SLURM_SUBMIT_DIR/ $TMP
cd $TMP
abq2024 job=$JOBNAME input=$JOBNAME.inp cpus=$SLURM_NPROCS mp_mode=mpi interactive
abq2024 cae noGUI=$JOBNAME.py
Multithreading job¶
1. Load module
The launcher command matches the version you load: abaqus/2024 provides
abq2024, abaqus/2022 provides abq. The associated fe-safe and tosca
tools are available as well.
2. Submit abaqus job
If you want to run Abaqus with shared memory on a single node, you can submit the following script:
#!/bin/bash
#SBATCH --job-name="abaqus"
#SBATCH --partition=compute
#SBATCH --nodes=1
#SBATCH --ntasks-per-node=1
#SBATCH --cpus-per-task=4
#SBATCH --time=08:00:00
#SBATCH --mem-per-cpu=2G
#SBATCH --account=research-<faculty>-<department>
module load abaqus/2024
abq2024 cpus=$SLURM_NPROCS mp_mode=threads [all your other abaqus parameters here...]
Running Abaqus interactively with GUI¶
Start a DelftBlue Desktop session from Open OnDemand. Inside the desktop, open a terminal and load Abaqus:
You should see the Abaqus/CAE window:

Harmless warnings on start-up
Abaqus/CAE prints a few messages when it starts in the desktop, such as
X Error: ... BadValue and a warning about "creating an OpenGL feedback
context for printing" / indirect GLX. With software rendering these are
expected and do not affect normal use.