김경종
58 lines
2.6 KiB
Markdown
58 lines
2.6 KiB
Markdown
---
|
|
type: concept
|
|
title: "Abaqus User Subroutines and Utility Routines"
|
|
complexity: advanced
|
|
domain: computational-mechanics
|
|
created: 2026-05-29
|
|
updated: 2026-05-29
|
|
address: c-000091
|
|
aliases:
|
|
- Abaqus user subroutines
|
|
- Abaqus utility routines
|
|
- Abaqus external databases
|
|
tags:
|
|
- concept
|
|
- finite-element-method
|
|
- abaqus
|
|
- user-subroutines
|
|
- implementation
|
|
status: current
|
|
related:
|
|
- "[[Abaqus-Analysis-User-s-Guide-Volume-II|Abaqus Analysis User's Guide Volume II]]"
|
|
- "[[Abaqus Job Execution Workflow]]"
|
|
- "[[Abaqus Resource and Parallel Execution]]"
|
|
- "[[Finite Element Program Implementation]]"
|
|
- "[[Abaqus Multiphysics Coupling and Co-simulation]]"
|
|
sources:
|
|
- "[[Abaqus-Analysis-User-s-Guide-Volume-II|Abaqus Analysis User's Guide Volume II]]"
|
|
---
|
|
|
|
# Abaqus User Subroutines and Utility Routines
|
|
|
|
## Definition
|
|
|
|
Abaqus user subroutines and utility routines extend Abaqus analyses with compiled C, C++, or Fortran code when ordinary keyword input is not flexible enough.
|
|
|
|
## How It Works
|
|
|
|
User subroutines are included at execution time through the job command or job settings. They are not saved into restart files, so they must be supplied again for restarted runs and can be revised if needed.
|
|
|
|
Subroutines can call certain Abaqus utility routines, but user subroutines cannot call one another directly. External database hooks such as `UEXTERNALDB` and `VEXTERNALDB` can manage runtime data exchange, once-per-increment computations, accumulated output, or staggered interaction with other codes.
|
|
|
|
The guide emphasizes implementation discipline: include the required Abaqus parameter files, follow Fortran/C calling conventions, avoid overwriting variables not designated for user definition, allocate large arrays dynamically, respect Abaqus file unit numbers, and test on small models before production use.
|
|
|
|
## Why It Matters
|
|
|
|
User subroutines are the point where a production finite element code becomes an extensible platform. They can encode material behavior, loads, fields, output, control logic, and external coupling, but they also introduce compiler, memory, thread-safety, restart, and debugging risks.
|
|
|
|
## Connections
|
|
|
|
- [[Abaqus Job Execution Workflow]] supplies the command-line path for compiling and linking user code.
|
|
- [[Abaqus Resource and Parallel Execution]] matters because user routines share memory and must behave correctly under parallel execution.
|
|
- [[Finite Element Program Implementation]] is the broader code-architecture context for extension points.
|
|
|
|
## Sources
|
|
|
|
- [[Abaqus-Analysis-User-s-Guide-Volume-II|Abaqus Analysis User's Guide Volume II]]
|
|
|