CFD Online Discussion Forums (http://www.cfd-online.com/Forums/)
-   OpenFOAM Running, Solving & CFD (http://www.cfd-online.com/Forums/openfoam-solving/)

 liuhuafei December 28, 2007 01:39

I have a question about the LD

I have a question about the LDUMatrix.

LDUMatrix contains the coefficients, lowerPtr,upperPtr,diagPtr ,and the address reference, uPtr and lPtr.

My questions are as follows:
1) Does the lPtr mean the owner of face and uPtr the neigbour of the face as done in the polyMesh?
In some mesh class in openfoam, owner's index(P)
is lower than neighbor index(N).

2) Does the upperPtr store the contribution of the neighbour cell(N) to the owner cell(P) and
the lowerPtr store the contribution of the owner(P) to the neighbour(N).

In Hoperations.C // H operator
template<class>
tmp<field<type> > lduMatrix::H(const ield<type>& ) const
{
.........
const scalarField& Lower = lower();
const scalarField& Upper = upper();

for (register label face=0; face<l.size(); face++) {
Hphi[u[face]] -= Lower[face]*sf[l[face]];
Hphi[l[face]] -= Upper[face]*sf[u[face]];
}
}

From this code, I guess the LowerAddr is owner list and UpperAddr is neighbour list,
Lower is the contribution of the owner (P) to the neighbour (N), Upper is the contribution of
the neighbour(N) to the owner.

if the matrix is

But in fvMatrix, the implementation of function negSumDiag() is as follows
negSumDiag:
for (register label face=0; face<l.size(); face++)
{
Diag[l[face]] -= Lower[face];
Diag[u[face]] -= Upper[face];
}
Diag[i] should be substract the contribution from all its neighbouring cell, why not the following code?
for (register label face=0; face<l.size(); face++)
{
Diag[l[face]] -= Upper[face];
Diag[u[face]] -= Lower[face];
}

3) For the implementation of FVM laplacian operator,only the fvm.upper is calculated,
why not the fvm.lower?
template<class>
tmp<fvmatrix<type> >
gaussLaplacianScheme<type>::fvmLaplacianUncorrecte d
(
const surfaceScalarField& gammaMagSf,
GeometricField<type,>& vf
)
{
.......
fvMatrix<type>& fvm = tfvm();

fvm.upper() = deltaCoeffs.internalField()*gammaMagSf.internalFie ld();

! why not the fvm.lower()
fvm.negSumDiag();

}

Liu Huafei

 schmidt_d December 28, 2007 11:31

Liu, I could take a guess at

Liu,
I could take a guess at question #3. Wouldn't the Laplacian produce a symmetric matrix? Until you have created asymmetric terms in the matrix, you could get away with only storing and calculating half the matrix. I haven't dug through the code, so this is just a guess.
David

 N2a May 29, 2009 07:12

Hello,

I try to solve an equation with the term " gamma *laplacian(rAUf, pd) ", I don't understand how to apply fvm for this kind of term.

May be someone can help me.

Thanks.

 N2a June 19, 2009 07:21

Quote:
 Originally Posted by N2a (Post 217559) Hello, I try to solve an equation with the term " gamma *laplacian(rAUf, pd) ", I don't understand how to apply fvm for this kind of term. May be someone can help me. Thanks.
Hello,
I tried an other way to solve it, but now I have to turn back on this equation.
On the programmer Guide, il's mentioned that fvMatrix autorizes * operator.
So I tried to write the term above as:
fvm::Sp(gamma,pd) * fvm::laplacian(rAUf, pd)) which would be what I want, it doesn't work. I tried also with the inner product & without success.

Hoping to have someone who can guide me,

Thanks,

 joern October 2, 2009 08:39

Quote:
 3) For the implementation of FVM laplacian operator,only the fvm.upper is calculated, why not the fvm.lower? template tmp > gaussLaplacianScheme::fvmLaplacianUncorrecte d ( const surfaceScalarField& gammaMagSf, GeometricField& vf ) { ....... fvMatrix& fvm = tfvm(); fvm.upper() = deltaCoeffs.internalField()*gammaMagSf.internalFie ld(); ! why not the fvm.lower() fvm.negSumDiag(); }
It want to ask this question again.
I tried to understand the matrix, produced by fvmlaplacianuncorrected for two days now, but i dont get it.

every discretisation for a diffusion (laplacian) term produces a sum over the faces. i looked into versteeg an in jasak's PhD.
If i want to reconstruct the matrix this way i get Terms:
- u_P + u_W + u_E + u_N + u_S = 0
(like in versteeg)
That produces a matrix with terms in upper, diag an lower.

If i look into OF code the laplacian Term only produces an upper-diagonal matrix. The lower part is 0.
For me it looks like the code only uses the faces that are not owed by the cells.
All my trys to construct or reverse-engeneer this matrix where useless.

can anyone tell me, why you just can look at the upper part (some of the faces)?

thx,
Joern

 hjasak October 3, 2009 06:21

Easy: if you only set the upper, the code assumes the matrix is SYMMETRIC and that you (clever trick) choose to store only one half of coefficients to save the memory and speed up the solver.

For asymmetric matrices you have no choice and have to store all coefficients. Otherwise, a_ij = a_ji and the pressure solver (the most expensive part of a segregated solver) runs much faster.

So here, the secret is out :)

Hope this helps,

Hrv

 joern October 3, 2009 06:58

thx a lot.
this helps. now i can work on...

 All times are GMT -4. The time now is 02:53.