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,62 @@
+---
+type: concept
+title: "Abaqus Job Execution Workflow"
+complexity: intermediate
+domain: computational-mechanics
+created: 2026-05-29
+updated: 2026-05-29
+address: c-000076
+aliases:
+  - Abaqus execution
+  - Abaqus job workflow
+  - Abaqus command line
+tags:
+  - concept
+  - finite-element-method
+  - abaqus
+  - execution
+status: current
+related:
+  - "[[Abaqus-Analysis-User-s-Guide-Volume-I|Abaqus Analysis User's Guide Volume I]]"
+  - "[[Abaqus-Analysis-User-s-Guide-Volume-II|Abaqus Analysis User's Guide Volume II]]"
+  - "[[Abaqus Input File Syntax]]"
+  - "[[Abaqus Resource and Parallel Execution]]"
+  - "[[Abaqus Output Database and Results Files]]"
+  - "[[Abaqus Restart and Results Transfer]]"
+  - "[[Abaqus User Subroutines and Utility Routines]]"
+  - "[[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-II|Abaqus Analysis User's Guide Volume II]]"
+---
+
+# Abaqus Job Execution Workflow
+
+## Definition
+
+Abaqus job execution workflow is the set of command-line and utility operations used to run, check, continue, recover, convert, and postprocess Abaqus analyses.
+
+## How It Works
+
+The guide centers execution on the `abaqus` command. A job normally has a job name, an input file, and options that select analysis behavior. Common modes include full analysis, data check, syntax check, parameter check, continuation, conversion, and recovery.
+
+Abaqus utilities extend the workflow beyond solving. The guide covers launching CAE or Viewer, running Python, fetching samples, compiling user subroutines, converting output databases, reporting results, translating external data, mapping thermal or magnetic loads, and assembling matrix data.
+
+Volume II adds execution consequences for analysis techniques: restart requests must be written before continuation is possible, import workflows depend on saved state files, co-simulation jobs need synchronized restart behavior, and user subroutines must be supplied again for restarted runs because they are not stored in restart files.
+
+## Why It Matters
+
+Execution is the operational boundary between model definition and numerical results. It determines which input file is parsed, what checks run before solving, which files are created, whether a failed analysis can be continued or recovered, and how external code such as user subroutines enters the analysis.
+
+## Connections
+
+- [[Abaqus Input File Syntax]] defines the input consumed by the job.
+- [[Abaqus Resource and Parallel Execution]] controls memory, scratch storage, CPU usage, MPI/threading, and GPU settings.
+- [[Abaqus Output Database and Results Files]] describes the files produced by execution.
+- [[Abaqus Restart and Results Transfer]] describes staged continuation and state import workflows.
+- [[Abaqus User Subroutines and Utility Routines]] describes compiled extension code attached to job execution.
+
+## Sources
+
+- [[Abaqus-Analysis-User-s-Guide-Volume-I|Abaqus Analysis User's Guide Volume I]]
+- [[Abaqus-Analysis-User-s-Guide-Volume-II|Abaqus Analysis User's Guide Volume II]]