Boundary conditions¶
Apply conditions to names from the actual mesh boundary inventory. A syntactically valid request can still describe the wrong physical problem if a boundary is misidentified.
Type |
Typical use |
Key inputs and checks |
|---|---|---|
|
Prescribed incoming flow |
Velocity vector, or supported volumetric flow with direction; temperature and turbulence where applicable |
|
Downstream pressure condition |
Absolute pressure and a location suitable for the expected flow |
|
Solid boundary |
No-slip, slip or supported moving-wall behaviour |
|
A rotating surface |
Axis, origin and angular velocity |
|
Physical symmetry plane |
Correct plane and compatibility with the expected solution |
|
External-flow boundary |
Consistent freestream/reference conditions |
config.boundary_conditions maps each patch name to a type and optional value. Inspect BoundaryCondition and BoundaryValue for exact fields.
Flow and pressure¶
Velocity uses Cartesian m/s. Volumetric flow uses m³/s and requires a nonzero flow_direction; it is converted using the actual inlet area. Do not supply both velocity and volumetric flow for the same inlet.
Pressure values are absolute Pa. A retained compatibility convention maps a zero outlet/farfield pressure to the reference pressure; use explicit physical absolute pressure in new requests to avoid ambiguity.
Turbulence and rotation¶
SST inlet values can use turbulent_kinetic_energy in m²/s² with specific_dissipation_rate in 1/s, or the supported intensity/viscosity-ratio convention. Read the schema and validate the selected combination. Never confuse a fraction with a percentage.
Rotation uses rad/s about an axis following the right-hand rule; origins use metres in the mesh coordinate system. A rotating wall does not create a rotating fluid volume. Use MRF zones when the model requires them.
Review mass balance and boundary-adjacent fields after solving. Backflow, unexpected blockage or a boundary too close to the region of interest can invalidate an otherwise converged setup.