Back to Skills

abaqus-field

majiayu000
Updated Today
15 views
58
9
58
View on GitHub
Othergeneral

About

This skill defines initial conditions and predefined fields in Abaqus, such as initial temperature, stress, or velocity. Use it when importing results from a previous analysis or setting a model's starting state. It routes fixed boundary conditions or time-varying loads to other dedicated skills.

Quick Install

Claude Code

Recommended
Plugin CommandRecommended
/plugin add https://github.com/majiayu000/claude-skill-registry
Git CloneAlternative
git clone https://github.com/majiayu000/claude-skill-registry.git ~/.claude/skills/abaqus-field

Copy and paste this command in Claude Code to install this skill

Documentation

Abaqus Field Skill

This skill defines initial conditions and predefined fields in Abaqus. Use it to set starting states or import results from previous analyses.

When to Use This Skill

Route here when user mentions:

  • "initial temperature", "starting temperature", "the part starts at..."
  • "pre-stress", "residual stress", "initial stress"
  • "initial velocity" (for impact/explicit dynamics)
  • "import temperature from thermal analysis"
  • "transfer results from previous analysis"
  • "bolt pre-tension", "bolt preload"

Route elsewhere:

  • Fixed temperature boundary conditions → /abaqus-bc
  • Heat flux, convection, radiation loads → /abaqus-load
  • Time-varying fields via amplitude → /abaqus-amplitude

Key Decisions

Field Type Selection

User NeedField TypeTypical Use
Starting temperatureTemperatureThermal stress from uniform T
Residual stressStressPre-stressed members
Impact velocityVelocityExplicit dynamics
From other analysisPredefined TemperatureSequential thermal-structural
Custom variablePredefined FieldUser-defined behaviors

Distribution Type

TypeWhen to Use
UNIFORMSame value everywhere
FROM_FILEImport from ODB or FIL
ANALYTICAL_FIELDExpression-based (X, Y, Z)
USER_DEFINEDVia user subroutine

What to Ask User

If information is missing, ask:

  1. What initial condition? Temperature, stress, velocity, or custom field?
  2. Uniform or varying? Same value everywhere or position-dependent?
  3. Import from ODB? If transferring, which file/step/frame?
  4. Region? Entire model or specific region?
  5. Value(s)? Magnitude, stress components, or velocity vector?

Workflow: Setting Up Fields

Step 1: Identify Field Type

Match user request to field type:

  • Temperature values → Temperature field
  • Stress state → Stress field
  • Moving parts → Velocity field
  • Previous analysis results → FROM_FILE distribution

Step 2: Define Region

Determine where the field applies:

  • Entire model (assembly set)
  • Specific part instance
  • Element set or node set

Step 3: Set Values or Import

For uniform fields: specify single magnitude or component values. For imported fields: ODB path, step name, increment number.

Step 4: Verify Step

Initial conditions use createStepName='Initial'. Predefined fields in analysis steps use the step name.

Sequential Thermal-Structural Workflow

  1. Run thermal analysis, save ODB
  2. Import temperature as predefined field in structural model
  3. Temperature causes thermal strain (requires expansion coefficient)

Key Parameters

ParameterNotes
createStepName'Initial' for initial conditions, step name for predefined
distributionTypeUNIFORM, FROM_FILE, ANALYTICAL_FIELD
fileNameODB path for FROM_FILE distribution
beginStep/endStepFrame selection for ODB import

Validation Checklist

  • Correct field type for the physics
  • Region covers intended elements/nodes
  • Step name is correct (Initial vs analysis step)
  • For FROM_FILE: ODB exists and contains required data
  • For thermal stress: material has expansion coefficient

Troubleshooting

ProblemLikely CauseSolution
Field not appliedWrong region or stepVerify region covers elements
Cannot read from ODBODB locked or wrong pathClose other sessions, check path
Temperature mismatchMesh incompatibilityUse mapping tolerance options
Stress equilibrium errorStress not self-equilibratingReview stress field consistency

Code Patterns

For API syntax and code examples, see references/ folder.

GitHub Repository

majiayu000/claude-skill-registry
Path: skills/data/abaqus-field

Related Skills

algorithmic-art

Meta

This Claude Skill creates original algorithmic art using p5.js with seeded randomness and interactive parameters. It generates .md files for algorithmic philosophies, plus .html and .js files for interactive generative art implementations. Use it when developers need to create flow fields, particle systems, or other computational art while avoiding copyright issues.

View skill

subagent-driven-development

Development

This skill executes implementation plans by dispatching a fresh subagent for each independent task, with code review between tasks. It enables fast iteration while maintaining quality gates through this review process. Use it when working on mostly independent tasks within the same session to ensure continuous progress with built-in quality checks.

View skill

executing-plans

Design

Use the executing-plans skill when you have a complete implementation plan to execute in controlled batches with review checkpoints. It loads and critically reviews the plan, then executes tasks in small batches (default 3 tasks) while reporting progress between each batch for architect review. This ensures systematic implementation with built-in quality control checkpoints.

View skill

cost-optimization

Other

This Claude Skill helps developers optimize cloud costs through resource rightsizing, tagging strategies, and spending analysis. It provides a framework for reducing cloud expenses and implementing cost governance across AWS, Azure, and GCP. Use it when you need to analyze infrastructure costs, right-size resources, or meet budget constraints.

View skill