Potential bug while using multiple solvers with dynamicOversetFvMesh
Summary
I am trying to use two motion solvers simultaneously with dynamicOversetFvMesh. One of the solver "displacementLaplacian" morphs the mesh based on the linear oscillation defined in the pointDisplacement Boundary condition file. The other solver moves the overset mesh using solidBodyMotionSolver or multiSolidBodyMotionSolver functionality.
Now, While running the simulation, I am noticing that the second solver seems to function only on every alternate time steps rather than executing every timestep. The displacementLaplacian solver appears to function at every timestep.
While using multiSolidBodyMotionSolver with tabulated6DoFMotion function, it can also be noticed that the overset mesh actually returns to it's t_0 position at every alternate timestep.
I have seen the tutorial for floatingBodyWithSpring, where the application of two different solvers is pretty much the same as my case. But I am not sure why I am getting such an issue.
Steps to reproduce
Example case
I have attached my example case of a Translating flat plate with overPimpleDyMFoam solver, to reproduce the exact behaviour.
Just need to run "overPimpleDyMFoam".HeavePlate_Issue.zip
What is the current bug behaviour?
The overset mesh return to its t_0 position at every alternate time step. The mesh morphing, however, seems to update nicely at every time-step.
If we remove the displacementLaplacian solver, and just use the solidBodyMotionSolver or multiSolidBodyMotionSolver functionality, there is no issue.
What is the expected correct behavior?
The overset mesh should not return to its t_0 position at every alternate time step. It should update to the new position from the last time-step position.
Relevant logs and/or images
Environment information
- OpenFOAM version : v2012|v1912
- Operating system : ubuntu
- Hardware info :
- Compiler :