Bugfix in pointPatchInterpolate
Regarding boundary condition update for non coupled boundaries of point fields, take 2 (my mistake: Vuko Vukcevic) Author: Dario Zivkovic.
This commit is contained in:
parent
2afc0297bc
commit
75d5b4a289
1 changed files with 3 additions and 13 deletions
|
@ -169,12 +169,6 @@ void pointPatchInterpolation::interpolate
|
|||
{
|
||||
pf.boundaryField()[patchi].initAddField();
|
||||
}
|
||||
else
|
||||
{
|
||||
// Bugfix: Need to update ordinary boundary conditions.
|
||||
// Dario Zivkovic, 8/Dec/2018.
|
||||
pf.boundaryField()[patchi].initEvaluate();
|
||||
}
|
||||
}
|
||||
|
||||
forAll(pf.boundaryField(), patchi)
|
||||
|
@ -186,15 +180,11 @@ void pointPatchInterpolation::interpolate
|
|||
pf.internalField()
|
||||
);
|
||||
}
|
||||
else
|
||||
{
|
||||
// Bugfix: Need to update ordinary boundary conditions.
|
||||
// Dario Zivkovic, 8/Dec/2018.
|
||||
pf.boundaryField()[patchi].evaluate();
|
||||
}
|
||||
}
|
||||
|
||||
// All boundaries already updated. Nothing to do. VV, 4/Dec/2017.
|
||||
// Bugfix: Must update boundary conditions for e.g. fixedValue that changes
|
||||
// within e.g. fvMotion solver. Dario Zivkovic, 21/Dec/2018.
|
||||
pf.correctBoundaryConditions();
|
||||
|
||||
if (debug)
|
||||
{
|
||||
|
|
Reference in a new issue