Descriptionπ
The uniformMixed is a boundary condition that provides
βmixedβ type boundary condition that mix a uniform fixed value and a
uniform patch-normal gradient condition. The term βuniformβ is a legacy name
since the prescribed values were previously spatially uniform across that patch.
Usageπ
The condition requires entries in both the boundary and field files.
Boundary fileπ
<patchName>
{
type patch;
...
}
Field fileπ
<patchName>
{
// Mandatory entries
type uniformMixed;
// Optional entries
uniformValue <Function1<Type>>;
uniformGradient <Function1<Type>>;
// Conditional entries
// if 'uniformValue' and 'uniformGradient' entries are set
uniformValueFraction <Function1<scalar>>;
// Inherited entries
...
}
where:
| Property | Description | Type | Required | Default |
|---|---|---|---|---|
type |
Type name: uniformMixed
|
word | yes | - |
uniformValue |
Uniform fixed values | Function1<Type> | no | - |
uniformGradient |
Uniform gradient values | Function1<Type> | no | - |
uniformValueFraction |
Fraction values | Function1<scalar> | conditional | - |
The inherited entries are elaborated in:
- fixedGradientFaPatchField.H
-
Function1.H
- This boundary condition allows lazier definitions so that either
or both:
uniformValueanduniformGradientmust be defined. If only of these entries is defined, the value fraction is automatically treated appropriately (ie, 0 with \c uniformGradient and 1 withuniformValue). If bothuniformValueanduniformGradientare defined, theuniformValueFractionmust also be defined. - The
valueentry (optional) is used for the initial values. Otherwise the function(s) are used for the evaluation. In some cases (eg, coded or expression entries with references to other fields) this can be problematic and thevalueentry will be needed.
Further informationπ
Tutorial:
- N/A
Source code:
API:
History:
- Introduced in version v2306
