Atlassian uses cookies to improve your browsing experience, perform analytics and research, and conduct advertising. Accept all cookies to indicate that you agree to our use of cookies on your device. Atlassian cookies and tracking notice, (opens new window)
User Manual

User Manual
Results will update as you type.
  • Application Guide
  • Status of System
  • Usage Guide
  • Compute partitions
  • Software
    • AI Frameworks and Tools
    • Bring your own license
    • Chemistry
    • Data Manipulation
    • Engineering
      • Abaqus - only with own license
      • Ansys Suite
      • MATLAB - only with own license
      • OpenFOAM
      • STAR-CCM+
    • Environment Modules
    • Miscellaneous
    • Numerics
    • Virtualization
    • Devtools Compiler Debugger
    • Visualisation Tools
  • FAQ
  • NHR Community
  • Contact

    You‘re viewing this with anonymous access, so some content might be blocked.
    /
    Abaqus - only with own license

    Abaqus - only with own license

    Feb. 11, 2025

    a Finite Element Analysis Package for Engineering Application

    To see our provided versions type:
    module avail abaqus

    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 details below). Alternatively, you might consider using other Finite Element Analysis (FEA) tools such as Mechanical or LS-DYNA from Ansys. Based on ABAQUS naming conventions and input style formats open-source projects like www.calculix.de might be an option, too (OpenMP parallel, MPI is experimental https://www.feacluster.com/calculix.php).

    To bring your own license to our systems first follow the steps described in Bring your own license (It should be sufficient if our login nodes can access your license server.)
    Secondly, place a file called 
    abaqus_v6.env in your home ~ folder (or in your current working directory). Inside that file add the following line:

    abaquslm_license_file="port@ip_number_of_your_license_server"

    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 cpu-clx:test
    #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
    # mp_host_list=[['bcn####', #],['bcn####', #]]
    # Here, the 1st entry is the node name and the 2nd entry is the number of cpu-cores per node.
    
    ### ABAQUS parallel execution
    abaqus analysis job=c2 cpus=${SLURM_NTASKS} standard_parallel=all mp_mode=mpi interactive double
    
    # To enforce a hybrid parallelization one may also add e.g. threads_per_mpi_process=24
    # In this example, if SLURM_NTASKS is 96 (cpu-clx:test) this results in 4 MPI processes, and 24 OpenMP threads.
    
    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 partition CPU CLX, to see the number of cores on your selected partition and machine.

    Single Node Processing

    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 (please note there is also an "abaqus cae noGUI" variant).
    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.

    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
    abaqus cae -mesa

    Note: Mesa provides graphic support for CPU-only systems (without GPUs).

    , multiple selections available, Use left or right arrow keys to navigate selected items
    software
    hlrn-sw
    sw-engineering
    {"serverDuration": 11, "requestCorrelationId": "ce4c40812f0349aea7ccaab77b4d67c1"}