Master backend architectures, REST API design, microservices, and server-side development across multiple languages. Use this as a central index to access specialized sub-skills.
中文简介正在准备中。当前显示原文说明。
Complete workflow for dynamic analysis. Use when user mentions impact, crash, drop test, transient, or time-varying response. Handles explicit and implicit dynamics.
中文简介正在准备中。当前显示原文说明。
查看安装方法安装前可以查看交给 AI 代理的指令内容。
This skill handles explicit and implicit dynamics for impact, crash, drop test, and transient response analysis.
Route here when user mentions:
Route elsewhere:
/abaqus-modal-analysis/abaqus-static-analysisBefore dynamic analysis:
Ask if unclear:
| 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 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 |
For drop tests and impact:
Field outputs: S (stress), U (displacement), V (velocity), A (acceleration), PEEQ (plastic strain)
History outputs for energy balance (explicit): ALLKE, ALLIE, ALLWK, ETOTAL
| 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.
Use /abaqus-job to submit, then check:
| 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 |
| 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 |
/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 extractionFor API syntax and code examples, see:
还没有评价。欢迎分享你的使用感受。
无需登录即可发表。欢迎分享使用感受、提问,或说明在哪些环境下无法运行。
还没有评论。来写第一条吧。
Master backend architectures, REST API design, microservices, and server-side development across multiple languages. Use this as a central index to access specialized sub-skills.
中文简介正在准备中。当前显示原文说明。
在每次回复中使用固定前缀并列出本次实际参考的指令/文件,便于校验是否遵循上下文与规则。
中文简介正在准备中。当前显示原文说明。
Automate 21risk tasks via Rube MCP (Composio). Always search tools first for current schemas.
中文简介正在准备中。当前显示原文说明。
Automate 2chat tasks via Rube MCP (Composio). Always search tools first for current schemas.
中文简介正在准备中。当前显示原文说明。
Arquitecto de Soluciones Principal y Consultor Tecnológico de Andru.ia. Diagnostica y traza la hoja de ruta óptima para proyectos de IA en español.
中文简介正在准备中。当前显示原文说明。
[00] META. Orchestrate skills into dynamic chains for complex tasks. Analyzes the task, discovers available skills, builds an optimal chain, explains why each skill is needed, and executes step-by-step with user confirmation. Use for any complex task requiring multiple thinking/research/analysis steps. Triggers on "plan this", "how to approach", "what's the strategy", "build a plan", or any multi-step problem requiring skill orchestration.
中文简介正在准备中。当前显示原文说明。