Overset mesh motion issues

astrotoma · March 24, 2020, 09:17

Dear all,

I am facing issues when running a model with an overset mesh and DFBI enabled. As you can see from the attached image of a simple test simulation of a floating cube, which shows the volume fraction on a section plane and the cube surface, the overset mesh seems to "drag" the fluid along while there seems to be no effect on the free surface in the background mesh.

Has anyone experienced this? I encountered the same problem in the "Lifeboat with overset mesh" tutorial.

ping · March 28, 2020, 20:19

it looks like your two regions have not been interfaced so do this and then use the overset mesh representation and overset status field functions to check the quality of the interfacing. you don’t need elongated cells since these are just used to save cell numbers in the free surface zone to create more cells vertically that horizontally

ping · March 30, 2020, 03:13

for a newby to overset mesh large cubic cells will work well and give quick debugging of basic problems that are happening in this case. and there is no reason to have grids initially aligned eg one region could use polyhedral cells although this is not recommendend for the HRIC physics used in star when wanting a good free surface.

once those issues are resolved then the user can introduce some mesh refinement in the vertical direction and and possible grid refinement, small time steps, 2nd order physics etc.

flat elongated cells are used to save cell numbers when trying to capture waves in vof free surface cases and then only in the free surface zone. for example when trying to capture large droplets that break away from the free surface eg in sloshing and separators then cubic cells are recommended in those locations.

so back to the problem in this case - from the image it looks like the two fluid regions have not been attached to each other using an overset mesh interface.

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
how to set periodic boundary conditions	Ganesh	FLUENT	15	November 18, 2020 06:09
Why does the mesh disappear after 'preview mesh motion'?	dengdeng	Fluent UDF and Scheme Programming	3	September 18, 2018 00:39
mesh quality problem for displacementSBRStress motion solver	zhaozhenkai	OpenFOAM	0	January 22, 2017 11:02
Star CCM Overset Mesh Error (Rotating Turbine)	thezack	Siemens	7	October 12, 2016 11:14
Mesh motion with Translation & Rotation	Doginal	CFX	2	January 12, 2014 06:21

March 28, 2020, 20:19		#2
ping Senior Member Ping Join Date: Mar 2009 Posts: 556 Rep Power: 20	it looks like your two regions have not been interfaced so do this and then use the overset mesh representation and overset status field functions to check the quality of the interfacing. you don’t need elongated cells since these are just used to save cell numbers in the free surface zone to create more cells vertically that horizontally

March 30, 2020, 03:13		#3
ping Senior Member Ping Join Date: Mar 2009 Posts: 556 Rep Power: 20	for a newby to overset mesh large cubic cells will work well and give quick debugging of basic problems that are happening in this case. and there is no reason to have grids initially aligned eg one region could use polyhedral cells although this is not recommendend for the HRIC physics used in star when wanting a good free surface. once those issues are resolved then the user can introduce some mesh refinement in the vertical direction and and possible grid refinement, small time steps, 2nd order physics etc. flat elongated cells are used to save cell numbers when trying to capture waves in vof free surface cases and then only in the free surface zone. for example when trying to capture large droplets that break away from the free surface eg in sloshing and separators then cubic cells are recommended in those locations. so back to the problem in this case - from the image it looks like the two fluid regions have not been attached to each other using an overset mesh interface.