modify wiki

2026-05-29 17:05:53 +09:00
parent b7f84e1c0f
commit b7b79e38b1
64 changed files with 3131 additions and 48 deletions
@@ -0,0 +1,56 @@
+---
+type: concept
+title: "Abaqus Output Database and Results Files"
+complexity: intermediate
+domain: computational-mechanics
+created: 2026-05-29
+updated: 2026-05-29
+address: c-000078
+aliases:
+  - Abaqus ODB
+  - Abaqus results file
+  - Abaqus output files
+tags:
+  - concept
+  - finite-element-method
+  - abaqus
+  - output
+  - postprocessing
+status: current
+related:
+  - "[[Abaqus-Analysis-User-s-Guide-Volume-I|Abaqus Analysis User's Guide Volume I]]"
+  - "[[Abaqus Job Execution Workflow]]"
+  - "[[Abaqus Input File Syntax]]"
+  - "[[Finite Element Modeling and Convergence Checks]]"
+  - "[[Finite Element Program Implementation]]"
+sources:
+  - "[[Abaqus-Analysis-User-s-Guide-Volume-I|Abaqus Analysis User's Guide Volume I]]"
+---
+
+# Abaqus Output Database and Results Files
+
+## Definition
+
+Abaqus output database and results files are the persistent files through which Abaqus reports computed fields, histories, diagnostics, status information, restart data, and selected analysis results.
+
+## How It Works
+
+Common output files include the data file (`.dat`), output database (`.odb`), SIM database (`.sim`), selected results file (`.fil`), message file (`.msg`), status file (`.sta`), and restart files. Different Abaqus products and procedures may create different combinations of files.
+
+The output database stores field output, history output, and diagnostic information. Field output is usually spatially broad and written less frequently, such as stress or displacement fields over model regions. History output is written more frequently at selected points or regions, such as a reaction force, displacement, energy, or contact quantity over time.
+
+The selected results file is a lower-level record stream intended for external or custom postprocessing. It uses record keys and attributes, references internal node and element numbers, and can be accessed by utility routines such as `INITPF`, `DBRNU`, `DBFILE`, `POSFIL`, and `DBFILW`.
+
+## Why It Matters
+
+Output control is part of the analysis model. Too little output hides modeling or convergence problems; too much output increases runtime and file size. The distinction between field output, history output, diagnostics, and selected results files determines how an analyst validates, debugs, and postprocesses an analysis.
+
+## Connections
+
+- [[Abaqus Input File Syntax]] controls output requests in history data.
+- [[Abaqus Job Execution Workflow]] creates and manages the output files.
+- [[Finite Element Modeling and Convergence Checks]] depends on reliable displacement, stress, reaction, energy, and diagnostic output.
+
+## Sources
+
+- [[Abaqus-Analysis-User-s-Guide-Volume-I|Abaqus Analysis User's Guide Volume I]]