calculatedFvPatchField: 'value' entry is now required to avoid problems with non-initialization
This commit is contained in:
parent
8d041d7ba8
commit
9e0e9fd37f
2 changed files with 3 additions and 2 deletions
|
|
@ -39,7 +39,7 @@ Description
|
|||
myPatch
|
||||
{
|
||||
type calculated;
|
||||
value uniform (0 0 0); // optional value entry
|
||||
value uniform (0 0 0); // Required value entry
|
||||
}
|
||||
\endverbatim
|
||||
|
||||
|
|
@ -89,7 +89,7 @@ public:
|
|||
const fvPatch&,
|
||||
const DimensionedField<Type, volMesh>&,
|
||||
const dictionary&,
|
||||
const bool valueRequired=false
|
||||
const bool valueRequired=true
|
||||
);
|
||||
|
||||
//- Construct by mapping given patchField<Type> onto a new patch
|
||||
|
|
|
|||
|
|
@ -24,6 +24,7 @@ boundaryField
|
|||
".*"
|
||||
{
|
||||
type calculated;
|
||||
value $internalField;
|
||||
}
|
||||
|
||||
frontAndBack
|
||||
|
|
|
|||
Loading…
Add table
Reference in a new issue