calculatedFvPatchField: 'value' entry is now required to avoid problems with non-initialization

This commit is contained in:
Henry Weller
2016-02-24 16:01:40 +00:00
parent 8d041d7ba8
commit 9e0e9fd37f
2 changed files with 3 additions and 2 deletions

View File

@ -39,7 +39,7 @@ Description
myPatch myPatch
{ {
type calculated; type calculated;
value uniform (0 0 0); // optional value entry value uniform (0 0 0); // Required value entry
} }
\endverbatim \endverbatim
@ -89,7 +89,7 @@ public:
const fvPatch&, const fvPatch&,
const DimensionedField<Type, volMesh>&, const DimensionedField<Type, volMesh>&,
const dictionary&, const dictionary&,
const bool valueRequired=false const bool valueRequired=true
); );
//- Construct by mapping given patchField<Type> onto a new patch //- Construct by mapping given patchField<Type> onto a new patch

View File

@ -24,6 +24,7 @@ boundaryField
".*" ".*"
{ {
type calculated; type calculated;
value $internalField;
} }
frontAndBack frontAndBack