Everything about Writing User Subroutines with Abaqus📝| Abaqus Subroutine Tutorial

1. Requirements for Writing Abaqus Subroutines

Abaqus user subroutines are mostly written in Fortran. When a simulation model that contains user subroutines is submitted to Abaqus, the correct compile and link commands should be used automatically. If the version of your Fortran compiler does not correspond to that specified, incompatibilities may occur. Therefore, it is important to have compatible components for subroutine configuration. You can find a comprehensive guide to compatible versions of Abaqus, Intel Fortran and Visual Studio In this article:

Compatible Fortran and Visual Studio for Abaqus

First, prepare the required programs. Then you should follow an instruction to link Abaqus with Intel Fortran and Visual Studio. For example, this article helps you with Abaqus 2017:

Linking Abaqus 2017 and Fortran

The basics are similar to other versions of Abaqus. Just pick the compatible versions from the former article

These are some of the necessary requirements to begin writing user subroutines with Abaqus. So, before we proceed with this Abaqus subroutines tutorial, make sure you have followed these instructions.

⭐⭐⭐Free Abaqus Course | ⏰10 hours Video  👩‍🎓+1000 Students   ♾️ Lifetime Access ✅ Module by Module Training                                  ✅ Standard/Explicit Analyses Tutorial ✅ Subroutines (UMAT) Training                    …         ✅ Python Scripting Lesson & Examples …………………………                 …………………….. ……………   …………………………………….Start Free Abaqus Course

2.An Introduction to Different Abaqus User Subroutines | Abaqus Subroutine Example

One of the most important Abaqus subroutine example is UMAT, which allows adding constitutive models to the program. A more advanced subroutine is UEL, enabling the creation of user-defined elements. Other, less complex Abaqus user subroutine examples include:

• DLOAD for specifying user-defined loading
• DISP to define the magnitudes of prescribed boundary conditions
• UVARM for defining a user output variable
• URDFIL for reading the results file during analyses
• SIGINI for specifying initial stress fields
• USDFLD for defining field variable dependence

UEL or UMAT are more complicated and require a good understanding of applied mechanics concepts (FEM, Continuum mechanics, Computational Plasticity…).

Read More: Units in Abaqus | Consistent units Abaqus

Although, several Abaqus user subroutines like DLOAD, USDFLD or DISP could be simple and can be learned with little effort using the Abaqus documentation and examples that come with it. If you want to learn more about each of the Abaqus subroutines mentioned in this section, you can easily click on Most Typically Used Subroutines in Abaqus.

3. Choosing the Appropriate Abaqus user Subroutine for Your Specific Issue

First, I have to say, The subroutines are available for both Abaqus/Standard and Abaqus/Explicit. For example, we have DLOAD in Abaqus/Standard and VDLOAD in Abaqus/Explicit.

This is where you should decide which subroutine is the answer to your need. While a complete understanding of the structure of Abaqus is not required to develop a user subroutine, it helps if the developer has at least an overview of the structure. This understanding is really mandatory when writing advanced subroutines like UMAT or UEL.

This is the basic flow of data and actions from the start of an Abaqus/Standard analysis to the end:

In addition, you can see this article to master the step, increment and iteration concepts:

Step, Increment, Iteration and Attempt concepts in Abaqus

And this is the basic flow diagram in an Abaqus/Explicit analysis:

There is some Abaqus subroutine example or Abaqus user subroutine manual in our Package shop. Follow this post to learn the basics about user subroutine writing or Abaqus user subroutine, and after that, you can learn each subroutine in our packages.

If you are looking for a quick guide about the compatible versions of Fortran and Visual Studio, click on the link below:

Q&A: What are the compatible versions of Intel Fortran and Visual Studio for my Abaqus version?

4. Referring to Abaqus Documentation

Reading the Abaqus user subroutine manual in the Documentation before working on it can save your time in the end and complete this Abaqus subroutine tutorial. You’re in good hands, in the following, we will explain how you can utilize the Abaqus Documentation.

Most difficulties in using Abaqus user subroutines can be solved by following the instructions in the manuals carefully. Open Abaqus User Subroutines Reference Guide from Abaqus Documentation:

First, select User Subroutines in the left panel. Then, Find your subroutine name from the list either for Abaqus/Standard or Abaqus/Explicit. Now, you will see these details on the right:

In the next section, we will provide detailed explanations to help you better understand the structure of Abaqus user subroutines.

4.1. Sections of a Subroutine Guide in Abaqus Documentation:

(1) Subroutine title and a short description of its usage in Abaqus

(2) Some links to the related topics of Documentation. Relation of the subroutine and the keywords of Abaqus.

(3) There are some refers to different examples included in Abaqus Documentation related to this subroutine. Open those examples too and look at them carefully.

It is generally useful to look for relevant examples in Abaqus Documentation to review them when embarking on a new class of problems. You may find these examples in Example Problems Guide, Benchmarks Guide, Verification Guide and less likely in Getting Started with Abaqus/CAE. Study the example problem description and the inputs and outputs. Find the most similar example to your specific problem.

(4) Here, you can learn what this subroutine can do, its limitations, etc.

Sometimes, after the Overview, there are some notes about the theory behind the subroutine and so on (for example, see Creep subroutine section in Documentation). Read them carefully, too.

(5) That is the code structure for the Abaqus user subroutine. Copy this part exactly

Generally, the variables passed into a user subroutine via the argument list are classified as either variables to be defined, variables that can be defined, or variables passed in for information.

(6) The parameters introduced in this part constitute the main part of a subroutine. You should define the parameters listed here.

(7) The user must not alter the values of the Variables passed in for information at all. Doing so will have unpredictable results.

Now, let’s dive into the main part of this Abaqus subroutine tutorial: writing user subroutines with Abaqus.

5. Writing User Subroutines with Abaqus

Now, you need to create a Fortran file (a simple txt file with .for ending) with whatever name you like.
Open the file. Here, we named our Abaqus subroutine example “myDISP.for” . By default, Microsoft Visual Studio will show up:

First, copy exactly the User subroutine interface part of the Documentation ((5) in the above figure). Now you should define the parameters listed in Variables to be defined section (6) instead of user coding to define x line. Here your coding skill come in! Write the customized expression for the parameters.

For example, for a DISP subroutine, we should define U (user defined special form of displacement B.C. that is not supported in Abaqus itself). Therefore, you need to be familiar with Fortran coding language. However, knowing just the main commands (loops, conditions…) and the data structures can be sufficient for most applications.

For this part, you can read the related post about UMAT Abaqus that completely describe how to write your first UMAT subroutine in Abaqus.

⭐⭐⭐Free Abaqus Course | ⏰10 hours Video  👩‍🎓+1000 Students   ♾️ Lifetime Access ✅ Module by Module Training                                  ✅ Standard/Explicit Analyses Tutorial ✅ Subroutines (UMAT) Training                    …           ✅ Python Scripting Lesson & Examples …………………………               ………….  …………………….. ……………   …………………………….Start Free Abaqus Course

6. Using the Subroutine in Abaqus Analysis

After you have written your own Abaqus user subroutine, you need to inform Abaqus where to use the subroutine. It depends on the type of subroutine. For example, DISP is a type of B.C. So, we go to Load module:

And when creating a new job, you give the address of your written subroutine.

7. How can I use multiple user subroutines in Abaqus? Should each subroutine have a separate file or be placed in the same .for file? How?

In Abaqus, there are situations where it becomes necessary to write multiple subroutines within a single file. This approach offers several advantages, including improved code organization, efficient compilation, and simplified code management. By combining multiple subroutines into a single file, engineers can better organize their code and maintain a logical structure. This helps in understanding the relationships and dependencies between different subroutines, making it easier to navigate and modify the code when necessary.

Additionally, compiling a single file with multiple subroutines can be more efficient than compiling multiple individual files. It reduces the overhead associated with compiling and linking separate files, resulting in faster compilation times.

Furthermore, managing a single file is often more convenient than dealing with multiple files. It simplifies the process of version control, sharing code with collaborators, and ensuring all necessary subroutines are readily available.

An example of multiple subroutines within a single file could be a scenario where an Abaqus user wants to implement custom material behavior along with user-defined elements. They might write a subroutine for the constitutive model (e.g., UMAT) and another subroutine for the user-defined element behavior (e.g., UEL). By combining these subroutines into a single file, the engineer can maintain a cohesive representation of their custom material and element behavior, making it easier to manage and reuse the code in different analyses.

We can have more than one Abaqus subroutine in one file. Abaqus himself will call both subroutines wherever and whenever it needs during analysis.

For example, if you are writing a UMAT and a USDFLD, your Fortran file will have such a structure:

Remember that a given user subroutine (such as UMAT or USDFLD) should appear only once in the specified user subroutine source.

8. Testing Your Written Abaqus Subroutine

The last and the trickiest step! Follow these instructions when running your sample jobs with subroutines:

» Always test your subroutines on the smallest possible model.

» Do not include other complicated features, such as contact, unless they are absolutely necessary when testing the subroutine.

» Test the most basic model of the user subroutine before adding additional complexity to the subroutine. Whenever add a new feature to the model in a user subroutine, test it before adding another feature.

» When appropriate, try to test the user subroutine in models where only values of the nodal degrees of freedom (displacement, rotations, temperature) are specified: simple tension test, simple shear test, simple temp B.C. s, etc.

To start to write the subroutine, you need to have Fortran knowledge. You can read “Fortran ‘Must Knows’ for Writing Subroutines in Abaqus article to get what you need!

9. How to Learn Abaqus Subroutine Writing Correctly? | Abaqus subroutine tutorial

Here below, I have listed some main Abaqus subroutine tutorials that you may encounter when using Abaqus at an advanced level as a graduate student or researcher. Good news for you! You can learn each subroutine you want by clicking on that.

In the last part of this post, I invite you to watch the below video, which presents our main Abaqus tutorial package that can save a lot of time if you are a beginner in Abaqus. Also, you can read this article about UAMP Abaqus subroutine.

Get this post as a PDF file: Writing User Subroutines with Abaqus

References:

Abaqus Documentation (User Subroutine Reference Guide)

Abaqus Documentation (Analysis User’s Guide)

Eager to hear from you…

The CAE Assistant is committed to addressing all your CAE needs, and your feedback greatly assists us in achieving this goal. If you have any questions or encounter complications, please feel free to comment here.