[kar]

Hello,

I would be happy to read some answer to these 3 things currently confusing me:

1. Whats the point of ddtSchemes subdictionary (userguide u-109), if actual discretisation scheme is what's written by constructing fvMatrix?

2. May I call OpenFOAM a implementation of *linear* FVM? Is there anything really quadratic (or more) about it? (what are cubicCorrection, fourth?)

3. Is it necessary to use fvm::{Su/Sp/SuSp}, if matrices are somehow preconditioned? For example, if momentum equation includes volume and body force (or some heat sources)?

Thank you.

[kar]

Ok, one question: are phi (surface field representing mass / volume flux) and U & mesh.Sf() supposed to be equal after PISO loop (U is velocity, of course)? Please answer to this!

[dbxmcf]

Phi does not necessarily to be equal, however, it should obey the continuity after the 2 PISO correction steps, which is the key issue of the Pressure-Velocity correction procedure.

[kar]

Another "mystery" related to this is a steady solution of cavity - when using linear interpolation for convection, I get this ugly solution:



but, the problem is, when use some limited scheme, say GammaV 1, they do not disappear! When solving in transient regime, this problem vanishes -- why? Could you explain, please?

[dbxmcf]

Hi, I don't know the exactly problem you have, my suggestion might be wrong, but I just think something "might" affect your solution. Then continuity equation is:

ddt(rho)+div(rho, U)=0

If you have compressible flow, phi should be rho*U which is interpolated to the face? Is your fluid density a constant? If not, then ddt(rho) might have an effect?

[kar]

A simple case, where rho is constant. Just for testing, so I can see if things work well, but they don't in fact.

Currently I've managed to crash icoFoam (and my own solvers) (see "OpenFOAM crashes when input is a steady solution!!").

A more constructive question would be: how to calculate phi field, if *only* U field is given (say, for initial conditions)? U&Sf result is different from solved one...

[dbxmcf]

Hi, I think the U field is interpolated to the control volume surface while calculating the phi. Since your rho is a constant, the phi is using the interpolated surface U times the surface area, that is why phi is coded as "surfaceScalarField" when used in the convection term (both in the pressure correction equation and the pseudo whole N-S equation for the PISO loop), I think a complete phi expression (for the compressible flow) should be:

linearinterpolate(rho*U) & mesh.Sf()

Correct me if I am wrong, thanks!

[kar]

Well, I already did that. Since my solver is incompressible, I used fvc::interpolate(U)&mesh.Sf() and that doesn't give me the same result for saved, converged U field as PISO loop does!
So I ask again: why there is difference and how should I calculate phi from U?

[kar]

To display difference field, I used div( interpolate_lin(U)&mesh.Sf() - phi ) and result looks like a fluctuations around zero. Also boundaries look problematic for some reason I don't know...

Here's a sample:

[hjasak]

(as Bernhard says: Warning - advertising own stuff!)

Have a look at my Thesis - the bit about pressure-velocity coupling, or try to dig out my CFD lecture material from somewhere. It will tell you what the difference between the interpolated velocity and face flux is and what to do if you insist on full consistency. For reference, this is to do with Rhie-Chow treatment.

Hrv

[ivan_cozza]

Karlis,
did you find out what happens if you choose cubicCorrection as interpolation scheme?
I'm facing a similar and strange problem:
I'm solving linearized Euler equations for a Gaussian acoustic pulse, and I tryied linear :

gradSchemes
{
default Gauss linear;
}

divSchemes
{
default Gauss linear;
// div(phi,utfold) Gauss limitedLinear 1;
}

laplacianSchemes
{
default none;
}

interpolationSchemes
{
default cubic;
}

and cubic schemes:

gradSchemes
{
default Gauss cubic;
}

divSchemes
{
default Gauss cubic;
// div(phi,utfold) Gauss limitedLinear 1;
}

laplacianSchemes
{
default none;
}

interpolationSchemes
{
default cubic;
}

and the results are the same!!
I'm wondering what I'm wrong in it...
Have a good day!