Skip to content
cccskills
FreePublished on GitHub

abaqus-interaction

Define contact and interactions - contact pairs, tie constraints, connectors. Use when user mentions contact, friction, tie, parts touching, or bonded surfaces.

The English summary is being prepared. Showing the original description.

See how to install

Files included (1)

  • SKILL.md4.7 KB

SKILL.md (original)

Review the instructions the agent will receive before you install.

Abaqus Interaction Skill

Define contact pairs, tie constraints, coupling, and connectors between parts in an assembly.

When to Use This Skill

Route here when user mentions:

  • "Contact between surfaces"
  • "Friction", "sliding contact", "frictionless"
  • "Tie constraint", "bonded surfaces", "welded"
  • "Parts touching", "parts can separate"
  • "Coupling", "connector", "spring element"
  • "Join different meshes"

Route elsewhere:

  • Complete contact analysis workflow → /abaqus-contact-analysis
  • Fixed supports or displacements → /abaqus-bc
  • Applied forces or pressures → /abaqus-load

Key Decisions

1. What Type of Connection?

User DescribesInteraction TypeKey Feature
Welded, glued, bondedTie constraintPermanent, no relative motion
Parts can slide and separateSurface-to-surface contactFriction, gap allowed
Load from point to surfaceCouplingReference point control
Spring, damper, hingeConnectorStiffness/damping behavior
Adhesive, delaminationCohesiveDamage initiation criteria

2. Contact Formulation

FormulationWhen to Use
Surface-to-surfaceGeneral contact (recommended default)
Node-to-surfaceLegacy compatibility, special cases
General contactAutomatic detection (explicit dynamics)
Self-contactFolding, buckling, large deformation

3. Typical Friction Coefficients

Surface PairFriction Coefficient
Frictionless0.0
Lubricated metal0.1 - 0.3
Dry metal-to-metal0.3 - 0.5
Rubber on surface0.5 - 0.8
No slip (rough)Use ROUGH formulation

What to Ask User

If unclear, ask:

  1. Bonded or sliding?

    • Bonded (no relative motion) → Tie constraint
    • Sliding allowed → Contact with friction
  2. Friction coefficient?

    • If not specified, suggest typical value for material pair
    • Frictionless is valid for lubricated or normal-dominant cases
  3. Which surface is master/slave?

    • User may not know - guide them (see below)
  4. Can surfaces separate?

    • Yes → allowSeparation=ON
    • No (always in contact) → allowSeparation=OFF

Master/Slave Selection Guidelines

CriterionMaster SurfaceSlave Surface
StiffnessStiffer bodySofter body
Mesh densityCoarser meshFiner mesh
SizeLarger surfaceSmaller surface
GeometryFlat/convexCurved/concave

When in doubt: The coarser mesh should be master.

Workflow: Setting Up Interactions

Step 1: Identify Contact Pairs

List all surfaces that interact. For each pair determine:

  • Type (contact vs tie)
  • Master and slave assignment
  • Friction requirements

Step 2: Create Surfaces

Surfaces must be defined on assembly instances before creating interactions.

Step 3: Define Contact Properties

For contact interactions, define:

  • Normal behavior: Hard contact, allow separation
  • Tangential behavior: Friction formulation and coefficient

Step 4: Create Interaction

Assign contact property to surface pair in appropriate step.

Step 5: Verify Setup

Check for:

  • Correct master/slave assignment
  • Appropriate initial gap/overclosure
  • Contact pair is active in correct step

Common Gotchas

SymptomLikely CauseSolution
Contact not detectedSurfaces too far apartUse adjust=ON or reduce initial gap
Severe discontinuity warningsContact chatteringAdd stabilization, use smaller increments
Negative eigenvalueWrong master/slaveSwap master and slave surfaces
Overclosure too largeInitial interferenceUse shrink fit option or adjust geometry
Tie not workingSurfaces not close enoughIncrease position tolerance

Validation Checklist

Before running analysis:

  • All contacting surface pairs identified
  • Master/slave correctly assigned
  • Contact properties defined (normal + tangential)
  • Interaction assigned to correct step
  • Initial gaps/overclosures within tolerance
  • Friction coefficient appropriate for materials

Code Patterns

For API syntax and code examples, see:

Reviews

No reviews yet. Tell others what you thought.

Comments

No login needed. Share how it worked for you, ask a question, or note where it did not run.

No comments yet. Be the first to write one.

Comments are published right away. Do not include personal information such as email addresses or phone numbers. Up to 2 URLs.

0 / 1,000 characters

This form is protected by reCAPTCHA, and the Google Privacy Policy and Terms of Service apply.

More skills from this repository

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.

The English summary is being prepared. Showing the original description.

MikeCheng1208/BattleTree2Updated Jul 22, 2026

在每次回复中使用固定前缀并列出本次实际参考的指令/文件,便于校验是否遵循上下文与规则。

The English summary is being prepared. Showing the original description.

MikeCheng1208/BattleTree2Updated Jul 22, 2026

Automate 21risk tasks via Rube MCP (Composio). Always search tools first for current schemas.

The English summary is being prepared. Showing the original description.

MikeCheng1208/BattleTree2Updated Jul 22, 2026

Automate 2chat tasks via Rube MCP (Composio). Always search tools first for current schemas.

The English summary is being prepared. Showing the original description.

MikeCheng1208/BattleTree2Updated Jul 22, 2026

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.

The English summary is being prepared. Showing the original description.

MikeCheng1208/BattleTree2Updated Jul 22, 2026

[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.

The English summary is being prepared. Showing the original description.

MikeCheng1208/BattleTree2Updated Jul 22, 2026

See all skills by MikeCheng1208

Report a problem with this skill