add wiki
Tests / Hermetic test suite (push) Has been cancelled
Tests / Skill frontmatter validation (push) Has been cancelled

This commit is contained in:
김경종
2026-06-01 09:36:33 +09:00
parent b7b79e38b1
commit b195ac126c
74 changed files with 3421 additions and 402 deletions
+10 -1
View File
@@ -4,7 +4,7 @@ title: "Abaqus Input File Syntax"
complexity: intermediate
domain: computational-mechanics
created: 2026-05-29
updated: 2026-05-29
updated: 2026-06-01
address: c-000072
aliases:
- ABAQUS input syntax
@@ -18,12 +18,17 @@ tags:
status: current
related:
- "[[Abaqus-Analysis-User-s-Guide-Volume-I|Abaqus Analysis User's Guide Volume I]]"
- "[[Abaqus-Analysis-User-s-Guide-Volume-V|Abaqus Analysis User's Guide Volume V]]"
- "[[ABAQUS]]"
- "[[Abaqus Spatial Model Definition]]"
- "[[Abaqus Prescribed Conditions and Amplitudes]]"
- "[[Abaqus Kinematic Constraints and MPCs]]"
- "[[Abaqus Contact Interaction Definition]]"
- "[[Abaqus Job Execution Workflow]]"
- "[[Finite Element Program Implementation]]"
sources:
- "[[Abaqus-Analysis-User-s-Guide-Volume-I|Abaqus Analysis User's Guide Volume I]]"
- "[[Abaqus-Analysis-User-s-Guide-Volume-V|Abaqus Analysis User's Guide Volume V]]"
---
# Abaqus Input File Syntax
@@ -38,6 +43,8 @@ An Abaqus input file is an ASCII file arranged as option blocks. Keyword lines b
The guide separates input into model data and history data. Model data define the reusable analysis model: nodes, elements, materials, sections, sets, initial conditions, and assembly structure. History data define analysis steps: procedure type, loads, boundary conditions, interactions, controls, and output requests. `*STEP` and `*END STEP` delimit each step.
[[Abaqus-Analysis-User-s-Guide-Volume-V|Volume V]] expands the history-data side of this syntax: prescribed conditions, amplitude references, boundary conditions, loads, predefined fields, constraints, contact interactions, contact properties, and cavity radiation controls all become keyword-level definitions tied to steps, surfaces, sets, or named properties.
Sets and labels are the main referencing mechanism. Nodes and elements can be grouped into sets so later options can apply constraints, sections, loads, surfaces, or output requests without restating individual IDs. Labels are generally case-insensitive unless quoted, and include files can split a large model across multiple files.
## Why It Matters
@@ -47,9 +54,11 @@ The input syntax is the user-visible API of a finite element code. It turns the
## Connections
- [[Abaqus Spatial Model Definition]] supplies the node, element, set, and assembly content referenced by the syntax.
- [[Abaqus Prescribed Conditions and Amplitudes]] and [[Abaqus Contact Interaction Definition]] show how history data drives loads, constraints, and interactions.
- [[Abaqus Job Execution Workflow]] consumes the input file through the `abaqus` command and related checks.
- [[Abaqus Output Database and Results Files]] is controlled by output requests placed in history data.
## Sources
- [[Abaqus-Analysis-User-s-Guide-Volume-I|Abaqus Analysis User's Guide Volume I]]
- [[Abaqus-Analysis-User-s-Guide-Volume-V|Abaqus Analysis User's Guide Volume V]]