[chaosCFD]

Dear Foamers,

Does OpenFOAM allow to establish two fvMatrix objects in one program? I tried the following code:

	fvVectorMatrix DEqn1
        (
            fvm::laplacian(impKf_, D(), "laplacian(DD,D)")
            - fvc::laplacian(impKf_, D(), "laplacian(DD,D)")
	);

        fvVectorMatrix DEqn2
       (
          fvm::laplacian(impKf_, D(), "laplacian(DD,D)")
          - fvc::laplacian(impKf_, D(), "laplacian(DD,D)")
       );

Info << "source of DEqn1: " << DEqn1.source() << endl;
Info << "source of DEqn2: " << DEqn2.source() << endl;

And the output is:

source of DEqn1: 4{(0 0 0)}
source of DEqn2: 4((0 0 0) (0 0 0) (0 0 0) (0 -27000 0))

Why the sources of the two fvMatrixes are different? They are established with the same parameters.

BTW, the fvc::laplacian(impKf_, D(), "laplacian(DD,D)") is:

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

internalField   nonuniform List<vector> 4((0 0 0) (0 0 0) (0 0 0) (0 -180000 0));

boundaryField
{
    top
    {
        type            zeroGradient;
    }
    left
    {
        type            zeroGradient;
    }
    right
    {
        type            zeroGradient;
    }
    bottom
    {
        type            zeroGradient;
    }
    front
    {
        type            empty;
    }
    back
    {
        type            empty;
    }
}

[hjasak]

Why D(), ie why do you need brackets? Is there a memory leak, or a reference to temporary?

Try making a field D and repeat the exercise.it looks like your second D or second equation has got a fixedValue boundary condition on the bottom patch. I’m not sure how this happened.

There are always dozens of such matrices created all the time - this must work.

Hrv

[chaosCFD]

Originally Posted by hjasak

Why D(), ie why do you need brackets? Is there a memory leak, or a reference to temporary?

Try making a field D and repeat the exercise.it looks like your second D or second equation has got a fixedValue boundary condition on the bottom patch. I’m not sure how this happened.

There are always dozens of such matrices created all the time - this must work.

Hrv

Dear Prof. Jasak
D() returns a volVectorField D_. The definition is in the base class.

            
virtual volVectorField& D()
            {
                return D_;
            }

Is this way of writing more likely to cause memory leak?