[doctorWho]

I am trying to combine dynamicRefineFvMesh and dynamicMotionSolverFvMesh with solidBody motionFunction. the new class is based on the dynamicRefineFvMesh and just adding a motionSolver pointer as follows:

class dynamicMotionRefineFvMesh
:
    public dynamicFvMesh
{
protected:
        ...
        //- motion solver
        autoPtr<motionSolver> motionPtr_;
        ...
}

in the source file, the member function, update() has the following statements at the begining and the rest is the same as that of dynamicRefineFvMesh.

bool Foam::dynamicMotionRefineFvMesh::update()
{
    fvMesh::movePoints(motionPtr_->newPoints());
    if (foundObject<volVectorField>("U"))
    {
        lookupObjectRef<volVectorField>("U").correctBoundaryConditions();
    }
    ...
}

for a test case, I have copied sloshingTank3D6DoF case from the tutorial and modified const/dynamicMeshDict as follows:

dynamicFvMesh   dynamicMotionRefineFvMesh;
motionSolver    solidBody;
solidBodyMotionFunction tabulated6DoFMotion;
CofG            (0 0 0);
timeDataFileName "constant/6DoF.dat";
refineInterval  1;
field           alpha.water;
lowerRefineLevel 0.001;
upperRefineLevel 0.999;
unrefineLevel   10;
nBufferLayers   1;
maxRefinement   2;
maxCells        200000;
    correctFluxes
    (
     (phi none)
     (nHatf none)
     (rhoPhi none)
     (alphaPhi none)
     (alphaPhi10 none)
     (ghf none)
    );
dumpLevel       true;

I got the following error when interDyMFoam is run.

--> FOAM FATAL ERROR: 
Continuity error cannot be removed by adjusting the outflow.
Please check the velocity boundary conditions and/or run potentialFoam to initialise the outflow.
Total flux              : 1e-300
Specified mass inflow   : 3770.92
Specified mass outflow  : 3770.92
Adjustable mass outflow : 0

When I checked with original dynamicMotionSolverFvMesh with solidBody motionFunction, the adjustPhi function shows as follows:

Total flux              : 123172.
Specified mass inflow   : 389e-13
Specified mass outflow  : 389e-13
Adjustable mass outflow : 0

I guess dynamicRefineMesh modifies boundary field when refine/unrefine but have no clue how to correct this behavior yet. So any help will be helpful.

[Fabian_tudo]

Did you find a solution for this problem? I merged dynamicRefineFvMesh and dynamicMotionSolverFvMesh in a quite similar way which leads to the same error. I tried to solve it by adjusting the parameters of the PIMPLE algorithm (especially changing correctingPhi to "yes") which reduces the total Flux but not in a satisfactory way.

I am not sure if it has anything to do with the boundary field because even if my refinement should be performed in the middle of the domain the error occurs. If I choose settings so that no cells are refined the dynamic mesh works fine exactly like dynamicMotionSolverFvMesh.

[Fabian_tudo]

I overcame this error relatively simple by changing the correctPhi parameter in the PIMPLE subdictionary of fvSolution to no. Unfortunately I do not have results to check the effects until now because another error occurs which I plan to discuss in detail in a new thread.