김경종
4.3 KiB
type, title, complexity, domain, created, updated, address, aliases, tags, status, related, sources, source_refs
| type | title | complexity | domain | created | updated | address | aliases | tags | status | related | sources | source_refs | |||||||||||||||||||||||||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| concept | Abaqus Input File Syntax | intermediate | computational-mechanics | 2026-05-29 | 2026-06-01 | c-000072 |
|
|
current |
|
|
Abaqus Input File Syntax
Definition
Abaqus input file syntax is the keyword-based text format used to define models, analysis steps, procedure controls, loads, boundary conditions, interactions, and output requests for ABAQUS.
How It Works
An Abaqus input file is an ASCII file arranged as option blocks. Keyword lines begin with *, can include comma-separated parameters, and are followed by data lines when the option requires numeric or label data. Comment lines begin with **.
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 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
The input syntax is the user-visible API of a finite element code. It turns the abstract Finite Element Program Implementation workflow into a declarative model description that the solver can parse into nodes, elements, degrees of freedom, procedures, and output requests.
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
abaquscommand and related checks. - Abaqus Output Database and Results Files is controlled by output requests placed in history data.