[Paul R]

Hello everyone,

I am trying to combine dynamicMotionSolverFvMesh with dynamicRefineFvMesh using esi version of OpenFOAM-v2206.

I went across multiple post like this one : https://shorturl.at/tFHY8
And other link like this one : https://shorturl.at/exyX0

That explain quite clearly how to do it on OpenFOAM-2.4.x
Eventho, it was not the same version of Openfoam I tried to follow as best as possible the main steps to achieve that.

Those steps are :
- Copying dynamicRefineFvMesh and rename it as dynamicMotionSolverRefineFvMesh
- Replace inside the .H and .C file the dynamicRefineFvMesh by dynamicMotionSolverRefineFvMesh
- Add fiew lines inside the Make/files and Make/options.
- Then create a motion pointer inside the .H file. / Add to the .H and .C the correct files at the beginning ("#include ....H") / Add to the .C file the functions used inside the dynamicMotionSolverFvMesh to move points.
- Compile the new solver.
- Modify the dynamicMeshDict.

But when I run it I encounter this error message :

''""
--> FOAM FATAL ERROR: (openfoam-2206)
The number of points in the mesh seems to have changed.
In constant/polyMesh there are 141254 points; in the current mesh there are 231329 points.

From virtual void Foam::sixDoFRigidBodyMotionSolver::solve()
in file sixDoFRigidBodyMotionSolver/sixDoFRigidBodyMotionSolver.C at line 195.

FOAM exiting
''""

What I understand is that after refining the mesh, sixDoFRigidBodyMotionSolver (which is the motionSolver) is still looking for mesh infos inside my constant/polyMesh folder which is not updated. Instead it should be looking at the ones created by the refinement part inside the steps folders "0", "0.5"...

So I tried to ckeck where the mesh informations are transmitted to the motionSolver to resolve this but a clear lack of C++ skills on my side is making it really difficult.
Is there a way to fix this ?
Maybe by updating at every step the constant/polyMesh folder or by pointing the input of the motionSolver to the step folders...

Moreover, I did some testing on my case :
When I remove the moving object the refinement is working and the simulation runs properly.
When I put a threshold impossible to reach for my refinement, the motion part is working and the simulation runs properly.

Those two tests makes me think that I am not that far from merging the two solvers but I'm not quite there yet.
I'll attached the dynamicMeshDict and the solver .C, Template.C, .H, Make/options and Make/files files to this post.

Thank you for your help and your time !

[jbo]

Hi Paul,
I'm also exploring the combination of dynamic mesh motion and refinement.
Have you managed to get it to work?
Looking forward to your response.
Best,
Julien

[Paul R]

Hi Julien,

Sorry for the late reply, I moved on to an other project whithout finding a solution for this one.

However, if anyone find something, i'll still be interested !
Best of luck,

Paul