|
[Sponsors] |
Continuity error cannot be removed by adjusting the outflow - rotating domain case |
|
LinkBack | Thread Tools | Search this Thread | Display Modes |
July 7, 2017, 06:06 |
Continuity error cannot be removed by adjusting the outflow - rotating domain case
|
#1 |
Member
Thomas Sprich
Join Date: Mar 2015
Posts: 76
Rep Power: 11 |
Dear Forum,
I am receiving the above mentioned error for the case I am trying to run. The full error message is as follows: Code:
--> 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 : 1516.5 Specified mass inflow : 0.0007348 Specified mass outflow : 0.00057401 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. FOAM exiting I have seen the following post: Continuity error cannot be removed by adjusting the outflow. Please check the velocit which discusses this problem, noting that it could be a problem with my boundary conditions. I am assuming that the problem is with my U and p files. These files are as follows: U Code:
dimensions [0 1 -1 0 0 0 0]; internalField uniform (0 0 0); boundaryField { rotorBottom { type movingWallVelocity; value uniform (0 0 0); } AMIbottom { type cyclicAMI; value uniform (0 0 0); } AMIbottom_slave { type cyclicAMI; value uniform (0 0 0); } baffles { type fixedValue; value uniform (0 0 0); } tank { type fixedValue; value uniform (0 0 0); } shaft { type fixedValue; value uniform (0 0 0); } bottomOfTank { type fixedValue; value uniform (0 0 0); } topOfTank { type fixedValue; value uniform (0 0 0); } } Code:
dimensions [0 2 -2 0 0 0 0]; internalField uniform 0; boundaryField { rotorBottom { type zeroGradient; } AMIbottom { type cyclicAMI; value uniform 0; } AMIbottom_slave { type cyclicAMI; value uniform 0; } baffles { type zeroGradient; } tank { type zeroGradient; } shaft { type zeroGradient; } bottomOfTank { type zeroGradient; } topOfTank { type zeroGradient; } } I have tried running potentialFoam as suggested but it doesn't resolve the error. In desperation, I have also checked that the rotational axis is correct, I have remeshed to get better agreement between the slave a master AMI patches, I have remeshed using different methods (meshing the whole stator and rotor domains in one operation and again meshing the stator and rotor separately and using mergeMesh). I have run moveDynamicMesh and it runs correctly. I am using the fvSolution and fvSchemes from the propeller case. I have just tried changing the speed of rotation in dynamicMeshDict. I found that if I made it very big, the mass inflow and outflow values increase in the error message above. If I decrease omega so that it is very small, the mass inflow and outflow values also decrease. This makes me think that the error might due to the rotating domain or perhaps the AMI interface between slave and master patches. Is there anyway that I could troubleshoot this? The part of the sHM dict that creates the AMI patches and rotating zone looks as follows: Code:
AMIbottom { level (2 2); faceType baffle; cellZone rotatingDomainBottom; faceZone rotatingDomainBottom; cellZoneInside inside; } Code:
/*--------------------------------*- C++ -*----------------------------------*\ | ========= | | | \\ / F ield | OpenFOAM: The Open Source CFD Toolbox | | \\ / O peration | Version: 4.1 | | \\ / A nd | Web: www.OpenFOAM.org | | \\/ M anipulation | | \*---------------------------------------------------------------------------*/ FoamFile { version 2.0; format binary; class polyBoundaryMesh; location "constant/polyMesh"; object boundary; } // * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * // 8 ( AMIbottom { type cyclicAMI; inGroups 1(cyclicAMI); nFaces 51672; startFace 5977891; transform noOrdering; neighbourPatch AMIbottom_slave; } AMIbottom_slave { type cyclicAMI; inGroups 1(cyclicAMI); nFaces 51672; startFace 6029563; transform noOrdering; neighbourPatch AMIbottom; } rotorBottom { type wall; inGroups 1(wall); nFaces 30099; startFace 6081235; } baffles { type wall; inGroups 1(wall); nFaces 32160; startFace 6111334; } tank { type wall; inGroups 1(wall); nFaces 87354; startFace 6143494; } shaft { type wall; inGroups 1(wall); nFaces 7779; startFace 6230848; } bottomOfTank { type wall; inGroups 1(wall); nFaces 24822; startFace 6238627; } topOfTank { type wall; inGroups 1(wall); nFaces 24910; startFace 6263449; } ) // ************************************************************************* // Thanks, Thomas |
|
|
|
Similar Threads | ||||
Thread | Thread Starter | Forum | Replies | Last Post |
Is Playstation 3 cluster suitable for CFD work | hsieh | OpenFOAM | 9 | August 16, 2015 14:53 |
How to write k and epsilon before the abnormal end | xiuying | OpenFOAM Running, Solving & CFD | 8 | August 27, 2013 15:33 |
injection problem | Mark New | FLUENT | 0 | August 4, 2013 01:30 |
IcoFoam parallel woes | msrinath80 | OpenFOAM Running, Solving & CFD | 9 | July 22, 2007 02:58 |
Free surface boudary conditions with SOLA-VOF | Fan | Main CFD Forum | 10 | September 9, 2006 12:24 |