[teddymett]

Dear All


I am trying to simulate a raceway pond having a rotating paddle-wheel. I have made the pond a closed tank and considered two phase, water and air, because part of the paddle-wheel is above the water. The geometry was built on SALOME and exported in STL format. I have modified the "mixerVesselAMI" tutorial to setup my case. Running "interDyMFoam" is giving me this error message pasted below that I couldn't remove by changing the boundary condition of U and P_rgh. snappyHexMesh has generated all parts of the geometry similar to the tutorial case. U and P_rgh files are also found below.



Any help please and thank you in advance.

teddy@teddy:~/Desktop/mixerVesselAMI_medit$ interDyMFoam
/*---------------------------------------------------------------------------*\
| ========= | |
| \\ / F ield | OpenFOAM: The Open Source CFD Toolbox |
| \\ / O peration | Version: 5.x |
| \\ / A nd | Web: www.OpenFOAM.org |
| \\/ M anipulation | |
\*---------------------------------------------------------------------------*/
Build : 5.x-68e8507efb72
Exec : interDyMFoam
Date : Nov 02 2018
Time : 16:17:17
Host : "teddy"
PID : 14665
I/O : uncollated
Case : /home/teddy/Desktop/mixerVesselAMI_medit
nProcs : 1
sigFpe : Enabling floating point exception trapping (FOAM_SIGFPE).
fileModificationChecking : Monitoring run-time modified files using timeStampMaster (fileModificationSkew 10)
allowSystemOperations : Allowing user-supplied system call operations

// * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * //
Create time

Create mesh for time = 0

Selecting dynamicFvMesh dynamicMotionSolverFvMesh
Selecting motion solver: solidBody
Selecting solid-body motion function rotatingMotion
Applying solid body motion to cellZone rotating

PIMPLE: no residual control data found. Calculations will employ 2 corrector loops

Reading field p_rgh

Reading field U

Reading/calculating face flux field phi

AMI: Creating addressing and weights between 52232 source faces and 52232 target faces
AMI: Patch source sum(weights) min/max/average = 1, 3.39257, 1.00135
AMI: Patch target sum(weights) min/max/average = 1, 2.47497, 1.00133
Reading transportProperties

Selecting incompressible transport model Newtonian
Selecting incompressible transport model Newtonian
Selecting turbulence model type RAS
Selecting RAS turbulence model kEpsilon

Reading g

Reading hRef
Calculating field g.h

No MRF models present

No finite volume options present



--> FOAM FATAL ERROR:
Continuity error cannot be removed by adjusting the outflow.
Please check the velocity boundary conditions and/or run potentialFoam to initialise the outflow.
Total flux : 1e-300
Specified mass inflow : 5.8243e-21
Specified mass outflow : 8.15734e-21
Adjustable mass outflow : 0


From function bool Foam::adjustPhi(Foam::surfaceScalarField&, const volVectorField&, Foam::volScalarField&)
in file cfdTools/general/adjustPhi/adjustPhi.C at line 107.

U

FoamFile
{
version 2.0;
format binary;
class volVectorField;
object U;
}
// * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * //

dimensions [0 1 -1 0 0 0 0];

internalField uniform (0 0 0);

boundaryField
{
".*"
{
type fixedValue;
value $internalField;
}

paddle
{
type movingWallVelocity;
value $internalField;

}

shaft
{
type rotatingWallVelocity;
origin (0.1 0.41 0.39);
axis (1 0 0);
omega -5;
}

"AMI.*"
{
type cyclicAMI;
value $internalField;
}
}

p_rgh

FoamFile
{
version 2.0;
format binary;
class volVectorField;
object U;
}
// * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * //

dimensions [0 1 -1 0 0 0 0];

internalField uniform (0 0 0);

boundaryField
{
".*"
{
type fixedValue;
value $internalField;
}

paddle
{
type movingWallVelocity;
value $internalField;

}

shaft
{
type rotatingWallVelocity;
origin (0.1 0.41 0.39);
axis (1 0 0);
omega -5;
}

"AMI.*"
{
type cyclicAMI;
value $internalField;
}
}

[NablaDyn]

I had the same problem (interFoam, OpenFOAM v1912). I'm not entirely sure how, but including

value uniform (0 0 0);

in the "rotatingWallVelocity" patch solved it. I assume it is another case underlining the importance of the "value" entry....

[Nasos_bal]

I have the same problem..did you solve it?