Boundary conditions
Where it is
Section titled “Where it is”Setup tree: Boundary conditions
Controls
Section titled “Controls”Assigned patches
Section titled “Assigned patches”Use the mesh’s patches
Section titled “Use the mesh’s patches”- Control: action (
ToolButton2) - Shown when:
Results.ready && !CaseState.patchesMatchMesh
New patch
Section titled “New patch”- Control: value (
ValueField) - Value modes: none (plain entry)
Named as OpenFOAM will see it — letters, digits and underscores.
+ Add patch
Section titled “+ Add patch”- Control: action (
ToolButton2) - Enabled when:
listRoot.pendingName !== "" && CaseState.patchNameIssue(listRoot.pendingName, -1) === ""
Problems reported against this step
Section titled “Problems reported against this step”The application checks these before a run and reports them in the Problems tab against this step.
| Severity | Message |
|---|---|
| error | No patch is set to ‘Wave inlet’, so constant/waveProperties names a patch that generates nothing. |
| info | Nothing on the boundary fixes the pressure level, so pRefCell 0 and pRefValue 0 are written into fvSolution to pin it. Only differences in pressure mean anything in a closed domain. |
| error | This case is set to two-dimensional but no patch is Empty (2D), so the solver will treat it as 3D. The side faces have to be empty for the direction to be dropped. |
| error | An axisymmetric case needs exactly two wedge patches, one each side of the axis. This case has …. |
| error | A case cannot be both two-dimensional and axisymmetric - empty and wedge patches are alternative ways of removing the same direction. |
… marks a value the application computes at run time, so the source carries no fixed text for it.