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.
日本語の概要は準備中です。原文の説明を表示しています。
Define contact and interactions - contact pairs, tie constraints, connectors. Use when user mentions contact, friction, tie, parts touching, or bonded surfaces.
インストールする前に、エージェントに与えられる指示の中身を確認できます。
Define contact pairs, tie constraints, coupling, and connectors between parts in an assembly.
Route here when user mentions:
Route elsewhere:
/abaqus-contact-analysis/abaqus-bc/abaqus-load| User Describes | Interaction Type | Key Feature |
|---|---|---|
| Welded, glued, bonded | Tie constraint | Permanent, no relative motion |
| Parts can slide and separate | Surface-to-surface contact | Friction, gap allowed |
| Load from point to surface | Coupling | Reference point control |
| Spring, damper, hinge | Connector | Stiffness/damping behavior |
| Adhesive, delamination | Cohesive | Damage initiation criteria |
| Formulation | When to Use |
|---|---|
| Surface-to-surface | General contact (recommended default) |
| Node-to-surface | Legacy compatibility, special cases |
| General contact | Automatic detection (explicit dynamics) |
| Self-contact | Folding, buckling, large deformation |
| Surface Pair | Friction Coefficient |
|---|---|
| Frictionless | 0.0 |
| Lubricated metal | 0.1 - 0.3 |
| Dry metal-to-metal | 0.3 - 0.5 |
| Rubber on surface | 0.5 - 0.8 |
| No slip (rough) | Use ROUGH formulation |
If unclear, ask:
Bonded or sliding?
Friction coefficient?
Which surface is master/slave?
Can surfaces separate?
allowSeparation=ONallowSeparation=OFF| Criterion | Master Surface | Slave Surface |
|---|---|---|
| Stiffness | Stiffer body | Softer body |
| Mesh density | Coarser mesh | Finer mesh |
| Size | Larger surface | Smaller surface |
| Geometry | Flat/convex | Curved/concave |
When in doubt: The coarser mesh should be master.
List all surfaces that interact. For each pair determine:
Surfaces must be defined on assembly instances before creating interactions.
For contact interactions, define:
Assign contact property to surface pair in appropriate step.
Check for:
| Symptom | Likely Cause | Solution |
|---|---|---|
| Contact not detected | Surfaces too far apart | Use adjust=ON or reduce initial gap |
| Severe discontinuity warnings | Contact chattering | Add stabilization, use smaller increments |
| Negative eigenvalue | Wrong master/slave | Swap master and slave surfaces |
| Overclosure too large | Initial interference | Use shrink fit option or adjust geometry |
| Tie not working | Surfaces not close enough | Increase position tolerance |
Before running analysis:
For 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.
日本語の概要は準備中です。原文の説明を表示しています。