Bugfix: resolving read problem in initialisation of IB patch fields

This commit is contained in:
Hrvoje Jasak 2019-01-29 09:53:30 +00:00
parent 758dad7a27
commit 67e2f83134
4 changed files with 13 additions and 6 deletions

View file

@ -66,7 +66,7 @@ fixedValueIbFvPatchField<Type>::fixedValueIbFvPatchField
const dictionary& dict
)
:
fixedValueFvPatchField<Type>(p, iF, dict),
fixedValueFvPatchField<Type>(p, iF), // Do not read mixed data
immersedBoundaryFieldBase<Type>
(
p,

View file

@ -70,7 +70,7 @@ mixedIbFvPatchField<Type>::mixedIbFvPatchField
const dictionary& dict
)
:
mixedFvPatchField<Type>(p, iF),
mixedFvPatchField<Type>(p, iF), // Do not read mixed data
immersedBoundaryFieldBase<Type>
(
p,
@ -109,7 +109,7 @@ mixedIbFvPatchField<Type>::mixedIbFvPatchField
// the patch is active
// Initialise the value to avoid errors
// HJ, 1/Dec/2017
if (this->ibPatch().ibPolyPatch().active())
// if (this->ibPatch().ibPolyPatch().active())
{
// Re-interpolate the data related to immersed boundary
this->updateIbValues();

View file

@ -65,7 +65,7 @@ movingImmersedBoundaryVelocityFvPatchVectorField
const dictionary& dict
)
:
fixedValueFvPatchVectorField(p, iF, dict),
fixedValueFvPatchVectorField(p, iF), // Do not read data
immersedBoundaryFieldBase<vector>
(
p,

View file

@ -66,9 +66,11 @@ immersedBoundaryFvsPatchField<Type>::immersedBoundaryFvsPatchField
const dictionary& dict
)
:
fvsPatchField<Type>(p, iF, dict),
fvsPatchField<Type>(p, iF), // Do not read base data
ibPatch_(refCast<const immersedBoundaryFvPatch>(p))
{}
{
operator=(pTraits<Type>::zero);
}
template<class Type>
@ -149,6 +151,11 @@ void immersedBoundaryFvsPatchField<Type>::evaluate
)
{
this->updateSize();
Field<Type>::operator=
(
Field<Type>(this->patch().size(), pTraits<Type>::zero)
);
}