Continuity error cannot be removed by adjusting the outflow - rotating domain case
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: I have seen the following post: https://www.cfd-online.com/Forums/op...tml#post613877 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]; Code:
dimensions [0 2 -2 0 0 0 0]; 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 Code:
/*--------------------------------*- C++ -*----------------------------------*\ Thanks, Thomas |
i have recieved this error and i have solved it:
one thing i can promise you is ; error is in your boundary conditions. just be 100% sure of that. other thing is: this error pops up when you solve same problem in different openfoam versions. mainly bcz codes evolve overtime. so adjust your boundary conditions. problem is most likely to be in P/U files. have luck! |
Hi Saddy,
Thanks for your input. Do you have any suggestions regarding the U and P BCs? To me they look right but I have been staring at it for days and can't figure it out. Thanks again, Thomas |
Greetings Saddy and the rest of the Forum,
I resolved the problem. Thanks for the help. As Saddy mentioned and the error message mentioned the problem was my boundary conditions for U. The exists in both the stationary and rotating regions of the domains, but I had a 'fixedValue' boundary condition. By changing it to 'movingWallVelocity' as is the case with the rotor, the problem is resolved. I'm not sure if this is a valid boundary condition for the part of the shaft in stationary region so I may remove the shaft altogether or create separate shaft patches in the stationary and rotating domains. Problem solved. Whew. Thomas |
whoa.......i was just here looking for the problem and in 1 second you solved it!! bravo
yeah i figured this same reason, actually physically we have to imagine whether we are unnecessarily imposing fixed/moving condition to one of our boundaries. this type of boundary conditions sometimes lead to divergence later or solution wont proceed at all. anyways u got it! |
All times are GMT -4. The time now is 22:00. |