[Mirage]

I am using OF3.0.1 and I am trying to edit an already edited pisoFoam solver written in OF 2.3.

I wrote the UEq in a separate .H file. The solver is working but I am sure, if i am doing it correctly.

Here is what i wrote in the new UEq file:

turbulence->correct();    

fvVectorMatrix UEqn
(
    fvm::ddt(U)
  + fvm::div(phi, U)
  + turbulence->divDevReff(U)
 ==                                
    flowDirection*gradP            
);

UEqn.relax();

if (piso.momentumPredictor())    
{
    solve(UEqn == -fvc::grad(p));
}

and here is the new pisoFoam .C file:

       Info<< "Time = " << runTime.timeName() << nl << endl;

        // Pressure-velocity PISO corrector
        {
            #include "UEqn.H"

            // --- PISO loop
            volScalarField rAU(1.0/UEqn.A());    
            while (piso.correct())
            {
                #include "pEqn.H"
                {
                    U.correctBoundaryConditions();
                }

            
         }

Here is the old pisoFoam solver:

while (runTime.loop())
    {
        Info<< "Time = " << runTime.timeName() << nl << endl;

       // #include "readPISOControls.H"
        #include "CourantNo.H"
    #include "setDeltaT.H" // added

    
    turbulence->correct();   

        // Pressure-velocity PISO corrector
        {
            // Momentum predictor

            fvVectorMatrix UEqn
            (
                fvm::ddt(U)
              + fvm::div(phi, U)
              + turbulence->divDevReff(U)
             ==                
        flowDirection*gradP   
            );

            UEqn.relax();

            if (momentumPredictor)
            {
                solve(UEqn == -fvc::grad(p));
            }

In the original pisoFoam (OF3.0.1) the UEq was also separated from the main .C file:

// Solve the Momentum equation

MRF.correctBoundaryVelocity(U);

fvVectorMatrix UEqn
(
    fvm::ddt(U) + fvm::div(phi, U)
  + MRF.DDt(U)
  + turbulence->divDevReff(U)
 ==
    fvOptions(U)
);

UEqn.relax();

fvOptions.constrain(UEqn);

if (piso.momentumPredictor())
{
    solve(UEqn == -fvc::grad(p));

    fvOptions.correct(U);
}

As you can see that UEq files look different. I was wondering, if I should use the functions

MRF.correctBoundaryVelocity(U);

and

fvOptions(U)

.

Please let me know if you need any other informations.

Any advice will be greatly appreciated, thanks in advance

[TobM]

You only need these, if you want to use fvOptions or MRF. If not, you don't need them.