Constraints, loads and interfaces
This page is the syntax reference for constraints, loads and interfaces. To set up a study, see Loads and Constraints.
These declarations belong to a model. Each has a stable id and a closed typed kind. Geometry
targets resolve to exact regions before projection onto a mesh.
Constraints
Essential constraints use a physics-qualified kind block and an explicit target. Implemented
families include structural fixed, symmetry, antisymmetry, prescribed motion, rigid/distributing
coupling, and tie constraints; thermal temperature and tie constraints; electrical potential,
equipotential, floating-conductor, integral-current, and reference constraints; magnetic vector
potential, ground, gauge, and periodic forms; acoustic pressure and periodic forms; and fluid
velocity, moving wall, no-slip wall, slip wall, symmetry, and pressure reference.
Value-bearing constraints require a constant or compatible typed signal. Target topology, cardinality, quantity, shape, frame, and units are validated by kind. Relational constraints name both sides and their kinematic relation; they do not hide the secondary target inside a string.
Loads and natural boundary conditions
A load can use direct applied-load syntax for force, moment, pressure, traction, body force, and
other supported physics quantities. Physics-qualified natural conditions cover thermal flux and
convection, electromagnetic sources, acoustic wall/radiation behavior, and fluid inlet/outlet
conditions. Each kind defines the accepted target role and physical value.
A load_case contains include load.<name> or include excitation.<name> members. Unknown,
duplicate, or incompatible members fail checking. Case membership remains explicit through
realization and evidence.
Signals and excitations
A signal <name> : <quantity> over <domain> owns values over time or frequency. Sources are a
constant, an explicit sample table, a standard waveform, or generated by function.<name>.
Sampled signals require one canonical interpolation spelling: linear, left_endpoint, or
right_endpoint. Extrapolation is reject, hold_endpoint, or zero; omitted extrapolation
means reject.
An excitation binds a signal to a physical action. It owns target, direction/frame,
distribution, and fixed_frame|follower kinematics. Omitted kinematics means fixed_frame.
Whole-model excitation is an explicit target and is allowed only for compatible kinds.
Initial conditions
initial declarations cover typed structural kinematics, temperature, electromagnetic state,
acoustic state, and fluid state. Sources are uniform values, compatible signals at a sample, or
field artifacts. A procedure selects the initial condition explicitly; the checker validates
family, quantity, topology, sample domain, and state compatibility.
Connectors and interfaces
Connectors and interfaces are relational model objects with typed endpoints, frames, laws, and transfer direction. Structural connector kinds, thermal and electromagnetic contacts, acoustic interfaces, fluid boundaries, and coupled-family interfaces use separate closed contracts. A coupled analysis must name the interface that transfers a field; adjacency alone does not create coupling.
The language server supplies the exact fields and units for a selected kind. Unknown members are errors rather than ignored extension data.
Constraint examples
constraint base_support {
structural.fixed { target = geometry.bracket.region.base }
}
constraint prescribed_temperature {
thermal.temperature {
target = geometry.bracket.region.heated_face
value = 80 degC
}
}Load and excitation examples
A constant force needs no separately named signal:
load service_force {
force on geometry.bracket.region.load_face = [0, -2.5, 0] kN
}
load_case service { include load.service_force }Name the signal when its history or generator is part of the model:
signal impact_force : force over time {
samples = [
{ at = 0 ms, value = 0 N },
{ at = 5 ms, value = 2.5 kN },
{ at = 20 ms, value = 0 N },
]
interpolation = linear
extrapolation = zero
}
excitation impact {
force {
target = geometry.bracket.region.load_face
direction = global([0, -1, 0])
signal = signal.impact_force
}
}Initial-condition and relationship examples
initial warm_start {
thermal.temperature {
target = whole_model
uniform = 325 K
}
}
connector mount_spring {
axial_spring {
primary = geometry.assembly.region.mount
secondary = geometry.assembly.region.frame
stiffness = 18 kN/m
}
}
interface bonded_contact {
contact.frictionless {
primary = geometry.assembly.region.part_a_contact
secondary = geometry.assembly.region.part_b_contact
}
}