exaFOAM/foam-extend4.1-coherent-io
Archived
1
1
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity

Update in solutionControl class

Browse source 
Flux should not be recalculated for patches with inletOutlet boundary
conditions.
This commit is contained in:
Vuko Vukcevic 2017-04-20 08:59:23 +02:00
parent 795249e50e
commit 28a310ce71
1 changed files with 14 additions and 5 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

19
src/finiteVolume/cfdTools/general/solutionControl/solutionControl/solutionControl.C
View file

@ -26,6 +26,7 @@ License
#include "solutionControl.H"
#include "lduMatrix.H"
#include "fvc.H"
#include "inletOutletFvPatchFields.H"
#include "slipFvPatchFields.H"
#include "symmetryFvPatchFields.H"
@ -300,19 +301,27 @@ void Foam::solutionControl::correctBoundaryFlux
// considerations when calculating the flux. Maybe we can reorganise this in
// future by relying on distinction between = and == operators for
// fvsPatchFields. However, that would require serious changes at the
// moment. VV, 23/Dec/2016.
// moment (e.g. using phi = rUA*UEqn.H() as in most solvers would not update
// the boundary values correctly for fixed fvsPatchFields). VV, 20/Apr/2017.
forAll (phib, patchI)
{
if (Ub[patchI].fixesValue())
// Get patch field
const fvPatchVectorField& Up = Ub[patchI];
if
(
Up.fixesValue()
&& !isA<inletOutletFvPatchVectorField>(Up)
)
{
// This is fixed value patch, flux needs to be recalculated
// with respect to the boundary condition
phib[patchI] == (Ub[patchI] & Sb[patchI]);
phib[patchI] == (Up & Sb[patchI]);
}
else if
(
isA<slipFvPatchVectorField>(Ub[patchI])
|| isA<symmetryFvPatchVectorField>(Ub[patchI])
isA<slipFvPatchVectorField>(Up)
|| isA<symmetryFvPatchVectorField>(Up)
)
{
// This is slip or symmetry, flux needs to be zero