본문으로 건너뛰기
cccskills
무료GitHub에 공개

abaqus-interaction

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

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

설치 방법 보기

포함된 파일(1)

  • SKILL.md4.7 KB

SKILL.md(원문)

설치하기 전에 에이전트에게 전달되는 지시 내용을 확인할 수 있습니다.

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:

리뷰

아직 리뷰가 없습니다. 사용해 본 소감을 남겨 주세요.

댓글

로그인 없이 쓸 수 있습니다. 사용 후기, 질문, 작동하지 않은 환경 등을 편하게 남겨 주세요.

아직 댓글이 없습니다. 첫 댓글을 남겨 보세요.

보내면 바로 공개됩니다. 이메일 주소나 전화번호 같은 개인 정보는 쓰지 마세요. URL은 2개까지입니다.

0 / 1,000자

이 양식은 reCAPTCHA로 보호되며 Google 개인정보처리방침 및 서비스 약관이 적용됩니다.

같은 저장소의 스킬

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.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

MikeCheng1208/BattleTree22026년 7월 22일 업데이트

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

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

MikeCheng1208/BattleTree22026년 7월 22일 업데이트

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

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

MikeCheng1208/BattleTree22026년 7월 22일 업데이트

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

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

MikeCheng1208/BattleTree22026년 7월 22일 업데이트

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.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

MikeCheng1208/BattleTree22026년 7월 22일 업데이트

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

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

MikeCheng1208/BattleTree22026년 7월 22일 업데이트

MikeCheng1208의 스킬 모두 보기

이 스킬의 문제 신고