abaqus-dynamic-analysis
Complete workflow for dynamic analysis. Use when user mentions impact, crash, drop test, transient, or time-varying response. Handles explicit and implicit dynamics.
Best use case
abaqus-dynamic-analysis is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Complete workflow for dynamic analysis. Use when user mentions impact, crash, drop test, transient, or time-varying response. Handles explicit and implicit dynamics.
Teams using abaqus-dynamic-analysis should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/abaqus-dynamic-analysis/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How abaqus-dynamic-analysis Compares
| Feature / Agent | abaqus-dynamic-analysis | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Complete workflow for dynamic analysis. Use when user mentions impact, crash, drop test, transient, or time-varying response. Handles explicit and implicit dynamics.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# Abaqus Dynamic Analysis Skill This skill handles explicit and implicit dynamics for impact, crash, drop test, and transient response analysis. ## When to Use This Skill **Route here when user mentions:** - Impact, crash, collision, drop test - Transient response, time-varying response - Shock loading, blast loading, explosive loading - High-speed events, wave propagation - "What happens when it hits..." **Route elsewhere:** - Natural frequency extraction → `/abaqus-modal-analysis` - Static/constant loads → `/abaqus-static-analysis` - Harmonic/sinusoidal response → modal + steady-state dynamics - Very long transients (minutes+) → consider implicit or quasi-static ## Prerequisites Before dynamic analysis: 1. Geometry and mesh ready 2. **Material MUST have density defined** (required for mass matrix) 3. Understand event duration and loading type ## Workflow: Setting Up Dynamic Analysis ### Step 1: Gather Information from User Ask if unclear: - **What's the event duration?** Milliseconds, seconds, or longer? - **Initial velocity?** For drop tests or impact - **Is contact involved?** Parts colliding or touching - **What output needed?** Stress, velocity, acceleration, energy? ### Step 2: Choose Explicit vs Implicit | Factor | Explicit | Implicit | |--------|----------|----------| | Time scale | Short (us to ms) | Longer (ms to s) | | Step size | Automatic (very small) | User-controlled | | Nonlinearity | Handles well | May need iterations | | Memory | Lower | Higher | | Contact | Natural handling | Needs care | | Best for | Impact, crash | Vibration, long transient | **Decision rule:** - Event < 10ms with impact/contact → **Explicit** - Event > 100ms without severe nonlinearity → **Implicit** - In between → Either can work, explicit often easier ### Step 3: Set Time Period | Event Type | Typical Duration | |------------|------------------| | High-speed impact | 0.1-10 ms | | Drop test | 1-100 ms | | Blast loading | 1-50 ms | | Seismic/vibration | 1-100 s | ### Step 4: Define Initial Conditions For drop tests and impact: - Set initial velocity on the impacting part/region - Velocity is applied in the Initial step ### Step 5: Configure Output Field outputs: `S` (stress), `U` (displacement), `V` (velocity), `A` (acceleration), `PEEQ` (plastic strain) History outputs for energy balance (explicit): `ALLKE`, `ALLIE`, `ALLWK`, `ETOTAL` ### Step 6: Consider Mass Scaling (Explicit Only) | Option | Effect | When | |--------|--------|------| | None | True inertia | Very short events, accuracy critical | | At beginning | Scale once | Quasi-static explicit | | Throughout | Continuous scaling | When inertia less important | **Warning:** Mass scaling speeds up analysis but affects inertial response. ### Step 7: Run and Validate Use `/abaqus-job` to submit, then check: - Energy balance (ETOTAL approximately constant) - Stable time increment (explicit) - Results physically reasonable ## Key Parameters | Parameter | Explicit | Implicit | |-----------|----------|----------| | Time period | Event duration | Event duration | | Time increment | Automatic | Specify initial, min, max | | Element library | EXPLICIT | STANDARD | | Element type | C3D8R recommended | C3D8R or C3D8 | | Hourglass control | ENHANCED | Default | ## Validation Checklist - [ ] Density defined in material - [ ] Time period appropriate for event - [ ] Initial conditions applied (velocity, position) - [ ] Output frequency captures behavior (100+ frames typical) - [ ] Energy balance acceptable (ETOTAL constant for explicit) - [ ] Results physically reasonable ## Troubleshooting | Problem | Likely Cause | Solution | |---------|--------------|----------| | "Time increment too small" | Small/distorted elements | Use mass scaling or coarsen mesh | | Energy balance error | Hourglass or instability | Check hourglass energy, add control | | Analysis takes forever (explicit) | Long time period | Consider implicit instead | | Convergence failure (implicit) | Severe nonlinearity | Use explicit or smaller increments | ## Related Skills - `/abaqus-material` - Define density (required) - `/abaqus-amplitude` - Time-varying loads - `/abaqus-field` - Initial velocity and predefined fields - `/abaqus-interaction` - Contact for impact problems - `/abaqus-odb` - Results extraction ## Code Patterns For API syntax and code examples, see: - [API Quick Reference](references/api-quick-ref.md) - [Common Patterns](references/common-patterns.md) - [Troubleshooting Guide](references/troubleshooting.md)
Related Skills
abaqus-modal-analysis
Complete workflow for modal/frequency analysis - extract natural frequencies and mode shapes. Use for vibration analysis and resonance avoidance.
stride-analysis-patterns
Apply STRIDE methodology to systematically identify threats. Use when analyzing system security, conducting threat modeling sessions, or creating security documentation.
statistical-analysis-spa
웹 기반 통계 분석 SPA 개발 스킬. 이상치 탐지(Outlier Detection)와 행별 통계 분석(Row Statistics)을 수행하는 React 애플리케이션 구현. Z-Score, IQR, MAD, Grubbs, Winsorize 이상치 탐지와 T-test, ANOVA 통계 분석 지원. Copy & Paste 또는 CSV/TXT 파일 드래그 앤 드롭으로 데이터 입력, Recharts를 활용한 시각화 기능 포함. 모든 데이터는 로컬에서만 처리되며 네트워크 전송 없음.
smiles_comprehensive_analysis
SMILES Comprehensive Analysis - Comprehensive SMILES analysis: validate, convert name, compute all molecular descriptors, and predict ADMET. Use this skill for cheminformatics tasks involving is valid smiles ChemicalStructureAnalyzer calculate mol basic info pred molecule admet. Combines 4 tools from 3 SCP server(s).
root-cause-analysis
Find the true source, not symptoms — systematic debugging from observation to permanent fix
rhetorical-analysis
Analyse rhétorique et épistémologique d'articles, discours et textes argumentatifs. Utiliser ce skill quand l'utilisateur demande d'analyser la qualité argumentative d'un texte, d'identifier des sophismes ou biais, d'évaluer la fiabilité des sources citées, de déconstruire la logique d'un raisonnement, ou de produire une réécriture critique structurée d'un document.
regulatory-community-analysis-ChIA-PET
This skill performs protein-mediated regulatory community analysis from ChIA-PET datasets and provide a way for visualizing the communities. Use this skill when you have a annotated peak file (in BED format) from ChIA-PET experiment and you want to identify the protein-mediated regulatory community according to the BED and BEDPE file from ChIA-PET.
project-analysis
Analyzes any project to understand its structure, tech stack, patterns, and conventions. Use when starting work on a new codebase, onboarding, or when asked "how does this project work?" or "what's the architecture?"
prd-analysis
PRD parsing and task decomposition patterns for intake workflows.
manifold-analysis
Analyze Manifold Markets prediction market data. Use when processing HTML exports or trade history from manifold.markets to create visualizations of trading volume, trader leaderboards, probability movements, and market dynamics. Triggers on requests involving Manifold Markets data, prediction market analysis, or when user uploads Manifold HTML files.
error-diagnostics-error-analysis
You are an expert error analysis specialist with deep expertise in debugging distributed systems, analyzing production incidents, and implementing comprehensive observability solutions.
error-debugging-error-analysis
You are an expert error analysis specialist with deep expertise in debugging distributed systems, analyzing production incidents, and implementing comprehensive observability solutions.