Zum Ende der Metadaten springen
Zum Anfang der Metadaten

Sie zeigen eine alte Version dieser Seite an. Zeigen Sie die aktuelle Version an.

Unterschiede anzeigen Seitenhistorie anzeigen

« Vorherige Version anzeigen Version 71 Nächste Version anzeigen »

A Finite Element Analysis Package for Engineering Application

Our Abaqus license will run out on April 30th, 2024. You will only be able to resume working with Abaqus products if you can bring your own license (see Abaqus - only with own license). Alternatively, you might consider using other Finite Element Analysis (FEA) tools such as Abaqus - only with own license or Abaqus - only with own license from Ansys.

To see our provided versions type:
module avail abaqus

ABAQUS 2019 is the default.
ABAQUS 2018 is the first version with multi-node support.
ABAQUS 2016 is the last version including Abaqus/CFD.

Documentation

To access the official documentation (starting with version 2017) you can register for free at:
http://help.3ds.com

Conditions for Usage and Licensing

You are only able to work with our installed Abaqus products if you can bring your own license (see Bring Your Own License). Alternatively, you might consider using other Finite Element Analysis (FEA) tools such as Mechanical or LS-DYNA from Ansys.

Access to and usage of the software is regionally limited:

  • Only users from Berlin (account names "be*") can use the ZIB license on NHR@ZIB systems. This license is strictly limited to teaching and academic research for non-industry funded projects only. Usually, there are always sufficient licenses for Abaqus/Standard and Abaqus/Explicit command-line based jobs. You can check this yourself (just in case):

    # on NHR@ZIB systems
    lmutil lmstat -S -c 1700@10.241.101.140 | grep -e "ABAQUSLM:" -e "Users of abaqus" -e "Users of parallel" -e "Users of cae"
  • Users from other german states can use the software installed on HLRN but have to use their own license from their own license server (see Bring Your Own License).

Example Jobscripts

The input file of the test case (Large Displacement Analysis of a linear beam in a plane) is: c2.inp

Distributed Memory Parallel Processing

This is an example of an Abaqus 2020 job on 2 nodes with 48 tasks, each.
#!/bin/bash
#SBATCH -t 00:10:00
#SBATCH --nodes=2  
#SBATCH --ntasks-per-node=48
#SBATCH -p standard96:test
#SBATCH --mail-type=ALL
#SBATCH --job-name=abaqus.c2

module load abaqus/2020

# host list:
echo "SLURM_NODELIST:  $SLURM_NODELIST"
create_abaqus_hostlist_for_slurm
# This command will create the file abaqus_v6.env for you.
# If abaqus_v6.env exists already in the case folder, it will append the line with the hostlist.

### ABAQUS parallel execution
abq2019 analysis job=c2 cpus=${SLURM_NTASKS} standard_parallel=all mp_mode=mpi interactive double

echo '#################### ABAQUS finished ############'

SLURM logs to: slurm-<your job id>.out

The log of the solver is written to: c2.msg

The small number of elements in this example does not allow to use 2x96 cores. Hence, 2x48 are utilized here. But typically, if there is sufficient memory per core, we recommend using all physical cores per node (such as, in the case of standard96: #SBATCH --ntasks-per-node=96). Please refer to Slurm partitions CPU, to see the number of cores on your selected partition and machine (Lise, Emmy).

Single Node Processing

This is an example of an Abaqus 2016 single-node job with 96 tasks.
#!/bin/bash
#SBATCH -t 00:10:00
#SBATCH --nodes=1  ## 2016 and 2017 do not run on more than one node
#SBATCH --ntasks-per-node=96
#SBATCH -p standard96:test
#SBATCH --job-name=abaqus.c2

module load abaqus/2016

# host list:
echo "SLURM_NODELIST:  $SLURM_NODELIST"
create_abaqus_hostlist_for_slurm
# This command will create the file abaqus_v6.env for you.
# If abaqus_v6.env exists already in the case folder, it will append the line with the hostlist.

### ABAQUS parallel execution
abq2016 analysis job=c2 cpus=${SLURM_NTASKS} standard_parallel=all mp_mode=mpi interactive double

echo '#################### ABAQUS finished ############'

Abaqus CAE GUI - not recommended for supercomputer use!

If you cannot set up your case input files *.inp by other means you may start a CAE GUI as a last resort on our compute nodes.
But be warned: to keep fast/small OS images on the compute node there is a minimal set of graphic drivers/libs only; X-window interactions involve high latency.
If you comply with our license terms (discussed above) you can use one of our four CAE licenses. In this case, please always add

#SBATCH -L cae

to your job script. This ensures that the SLURM scheduler starts your job only if a CAE license is available.

Interactive CAE GUI run (not recommended)
srun -p standard96:test -L cae --x11 --pty bash

# wait for node allocation (a single node is the default), then run the following on the compute node 

module load abaqus/2022
abaqus cae -mesa
  • Keine Stichwörter