Sim Plugin Abaqus — Development skill for Claude Code

sim-plugin-abaqus

Use Codex, Claude Code, or another AI agent to work with [Dassault Systemes SIMULIA Abaqus](https://www.3ds.com/products/simulia/abaqus) input decks and Abaqus/CAE Python scripts through [sim-cli](https://github.com/svd-ai-lab/sim-cli).

`sim-plugin-abaqus` gives an agent practical Abaqus control paths: run `.inp` decks, run Abaqus/CAE Python scripts in Abaqus's embedded interpreter, keep an iterative noGUI CAE authoring session, inspect runtime health, collect model summaries, read job diagnostics, and report generated artifacts such as `.dat`, `.msg`, `.sta`, `.cae`, and `.odb` files.

The Abaqus application is not bundled. See [LICENSE-NOTICE.md](LICENSE-NOTICE.md).

This plugin is for Dassault SIMULIA Abaqus, not Ansys Mechanical. Use the Mechanical plugin for PyMechanical and Ansys Mechanical sessions.

What an agent can do with Abaqus

• Run complete Abaqus input decks with uv run sim run --solver abaqus model.inp.
• Run Abaqus/CAE Python scripts through Abaqus's embedded Python.
• Build and debug CAE models incrementally with connect, exec, and inspect.
• Use a file-backed authoring session for conservative step-by-step work.
• Use the optional noGUI bridge backend for lower-latency trusted local loops.
• Inspect session.health, cae.model_summary, workdir.files, and job.latest before continuing a workflow.
• Treat solver completion as one signal, then validate against engineering acceptance criteria.

Choose the right Abaqus workflow

1. Batch input-deck execution

Use this when the model is already fully specified as an Abaqus `.inp` deck:

uv run sim lint path/to/model.inp
uv run sim run --solver abaqus path/to/model.inp

Abaqus writes output artifacts next to the deck. Inspect `.msg`, `.sta`, `.dat`, and `.odb` outputs before treating the result as accepted.

2. Abaqus/CAE Python script execution

Use this when the model is authored by a complete Abaqus/CAE Python script: