Abaqus Boundary Conditions
Overview
Translate an approved physical support or prescribed field into an auditable
region, degree-of-freedom, magnitude, amplitude, and activation contract.
When to use
Use before creating or changing a boundary condition, or when reactions,
rigid-body motion, symmetry, or step activation suggest a support error.
Inputs
- Physical restraint or prescribed-field statement
- Named region and coordinate system
- Active degrees of freedom, units, and magnitude
- Creation step, later modifications, and amplitude behavior
- Expected reactions or symmetry evidence
Outputs
Return a boundary-condition table, Abaqus object plan, conflict audit, and
verification observations. State every unconstrained degree of freedom.
Workflow
- Express the physical intent without Abaqus syntax.
- Resolve the exact region and local/global coordinate system.
- Map intent to active degrees of freedom and step history.
- Check duplicate, conflicting, or over-constraining conditions.
- Define reaction, displacement, or symmetry evidence.
Safety gates
- Never add a restraint only to suppress convergence trouble.
- Never infer symmetry from visual appearance alone.
- Never prescribe an unknown magnitude or sign.
- Keep support adequacy separate from solver completion.
Example prompts
Review the base and side supports for a three-dimensional soil model. List
constrained degrees of freedom, coordinate systems, conflicts, and reaction
checks. Do not edit the model.
Common failures
- Applying a global direction where the region uses a rotated system.
- Leaving an obsolete condition active in later steps.
- Constraining both members of an intended relative motion.
- Reporting a fixed node set without its physical justification.
Acceptance checklist
1---2name: abaqus-bc3description: Use when defining or reviewing Abaqus displacement, rotation, symmetry, support, pore-pressure, temperature, or other prescribed boundary conditions on named regions and steps.4---56# Abaqus Boundary Conditions78## Overview910Translate an approved physical support or prescribed field into an auditable11region, degree-of-freedom, magnitude, amplitude, and activation contract.1213## When to use1415Use before creating or changing a boundary condition, or when reactions,16rigid-body motion, symmetry, or step activation suggest a support error.1718## Inputs1920- Physical restraint or prescribed-field statement21- Named region and coordinate system22- Active degrees of freedom, units, and magnitude23- Creation step, later modifications, and amplitude behavior24- Expected reactions or symmetry evidence2526## Outputs2728Return a boundary-condition table, Abaqus object plan, conflict audit, and29verification observations. State every unconstrained degree of freedom.3031## Workflow32331. Express the physical intent without Abaqus syntax.342. Resolve the exact region and local/global coordinate system.353. Map intent to active degrees of freedom and step history.364. Check duplicate, conflicting, or over-constraining conditions.375. Define reaction, displacement, or symmetry evidence.3839## Safety gates4041- Never add a restraint only to suppress convergence trouble.42- Never infer symmetry from visual appearance alone.43- Never prescribe an unknown magnitude or sign.44- Keep support adequacy separate from solver completion.4546## Example prompts4748> Review the base and side supports for a three-dimensional soil model. List49> constrained degrees of freedom, coordinate systems, conflicts, and reaction50> checks. Do not edit the model.5152## Common failures5354- Applying a global direction where the region uses a rotated system.55- Leaving an obsolete condition active in later steps.56- Constraining both members of an intended relative motion.57- Reporting a fixed node set without its physical justification.5859## Acceptance checklist6061- [ ] Region, step, coordinate system, and units are explicit.62- [ ] Every constrained degree of freedom has physical justification.63- [ ] Conflicts and rigid-body modes were checked.64- [ ] Activation history matches the construction sequence.65- [ ] Verification variables and regions are defined.66
1348109517