Frequently Asked Question

The computational boundary should be far enough from the region of interest that its mathematical condition does not distort the solution. The necessary distance depends on wake length, pressure recovery, diffusion, acoustic propagation, and recirculation.

Move a boundary outward and compare the quantity of interest. This domain-sensitivity test is more defensible than using a universal distance rule.

Well-posed boundaries

Boundary conditions provide the information needed to make a mathematical problem well posed. They must match the physical location and the variables that are actually known. Specifying velocity, mass flow, pressure, temperature, turbulence, species, or phase fraction redundantly can over-constrain a problem or hide an unintended assumption. Artificial boundaries should be placed far enough from the feature of interest that their condition does not control the result.

ṁ is mass flow, A is the boundary area, n is the outward normal, and Δp is the pressure difference with a stated reference.

Worked example

For an inlet area of 0.01 m², uniform speed of 5 m/s, and density of 1.2 kg/m³, ṁ = 1.2×5×0.01 = 0.06 kg/s. Compare that value with integrated outlet flux. A mismatch requires investigation of normals, compressibility, sources, leakage, or boundary placement.

Check: vary domain extent or outlet treatment when recirculation or strong gradients reach the boundary.

Engineering check

For Domain Extent and Boundary Placement, maintain traceability from requirement to risk, design output, evidence, and approval. Record the configuration, acceptance criterion, test or analysis conditions, open actions, and residual risk. A method is not complete when the document is filled in; it is complete when the evidence supports the decision and affected controls are updated.