The five primitives and residuals

Fluxcore’s five primitive flow quantities describe the fluid mean-flow state: density, the three velocity components, and pressure. Temperature is related to the thermodynamic state through the selected material model. Turbulence and conjugate heat transfer add their own model variables and checks.

Primitive quantity

Symbol / familiar field label

Physical units

Density

ρ / rho

kg/m³

X velocity

u / Ux

m/s

Y velocity

v / Uy

m/s

Z velocity

w / Uz

m/s

Pressure

p / pressure

Pa

These quantities describe the flow. The residual chart reports how well the governing equations are satisfied, so its five core curves are not a one-to-one list of primitive-variable changes.

The five core equation residuals

Reported key

Equation being checked

How to interpret it

continuity

Conservation of mass

Remaining mass-balance residual across the flow domain

Ux

X momentum

Remaining imbalance in the x-directed momentum equation

Uy

Y momentum

Remaining imbalance in the y-directed momentum equation

Uz

Z momentum

Remaining imbalance in the z-directed momentum equation

energy

Conservation of total energy

Remaining energy-equation imbalance

The velocity-labelled curves are equation residuals, not velocity values in m/s. Likewise, a residual value is not a pressure in Pa, a temperature in K, or a direct percentage error in the engineering answer.

Pressure is part of the physical solution, but the current Fluxcore reporting does not add an independent pressure-equation curve to these five conservation equations. Agents should preserve the returned energy label and should not invent a p residual or relabel an older pressure history as energy.

Additional curves

SST can add k and omega; Spalart–Allmaras can add nu_tilde. Thermal or other diagnostics can include T and additional qualified quantities. Their presence depends on the run and saved result. A temperature diagnostic does not replace the total-energy residual, and absent data is not a zero residual.

Read the histories together

Look for the required reduction and sustained behaviour across all relevant equations. Residuals are scaled convergence measures; compare their trend within the run and retain any supplied normalization or qualification. A common numerical value does not imply identical physical error across different equations or cases.

Check forces, pressure drop, mass/energy balance and relevant thermal outputs alongside the curves. For URANS, distinguish within-step convergence from the physical time history and statistical sampling. CHT also needs fluid/solid and interface evidence.

The published convergence.residuals dictionary identifies the actual saved channels and convergence.iterations provides their abscissa. Use the returned final residuals as the terminal assessment; they can describe the exported state separately from the last plotted history sample. Keep that distinction when presenting a result.

See convergence and qualification, running a job, and result handling through API/MCP.