Split volume

maria.mg · October 18, 2019, 06:01

Hello!
In order to create a dinamic mesh, I have an interior mesh, moving along with the train and another exterior mesh which will be deformed. I tried to create 2 enclosures, but the problem is that I can't setup the walls of the interior enclosure as "interior". Is there a posibility to create an enclosure and split that volume in a certain way? I tried with split body in space claim, but I didn't obtaine what I want. (What I want to have is a rectangular parallelepiped inside of box).
If you have any idea, please do not hesitate to contact me. Thanks!

set::set() · October 20, 2019, 20:27

Maybe it's me. But I don't catch the details. Which code are you using to do it? What is a "train"? Why did you mention something about deforming mesh?

I guess you want to define as "transparent" the surface that separates both sides of your mesh by marking it as "interior". Because one mesh is doing something more complex and the other one is extending the domain. But probably you don't need to go this way by just merge both meshes.

The problem is this. If you treat both meshes separately even if you mark the intersection surface as interior. Any solver won't know how to deal with this unless it was specifically designed for this. Because each mesh has its own table for vertex to conform its cells, and hence, surfaces will be also duplicated even you said that this surface is interior. Ok, but how do you compute the fluxes in each face? Your solver should know how to pass the flux from one face to the other even if they are lying together.

The best way to fix this is by merge both meshes at some point of your workflow, then any duplicity entity will be removed and you will be safe.

Sorry if this answer doesn't help you, it is just what I understood.

October 18, 2019, 06:01	Split volume	#1
maria.mg New Member Maria Margaritoiu Join Date: Oct 2019 Posts: 2 Rep Power: 0	Hello! In order to create a dinamic mesh, I have an interior mesh, moving along with the train and another exterior mesh which will be deformed. I tried to create 2 enclosures, but the problem is that I can't setup the walls of the interior enclosure as "interior". Is there a posibility to create an enclosure and split that volume in a certain way? I tried with split body in space claim, but I didn't obtaine what I want. (What I want to have is a rectangular parallelepiped inside of box). If you have any idea, please do not hesitate to contact me. Thanks!

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
multiphaseEulerFoam (OF2.3.0) : Courant number explodes when running in parallel	Mehrez	OpenFOAM Running, Solving & CFD	10	May 18, 2016 12:44
multiphase turbulance case floating error	harsha_kulkarni	OpenFOAM Running, Solving & CFD	3	February 18, 2016 06:06
channelFoam for a 3D pipe	AlmostSurelyRob	OpenFOAM	3	June 24, 2011 14:06
On the damBreak4phaseFine cases	paean	OpenFOAM Running, Solving & CFD	0	November 14, 2008 22:14
split volume	Kabo	FLUENT	1	January 28, 2008 08:08

October 20, 2019, 20:27		#2
set::set() New Member Join Date: Mar 2019 Posts: 2 Rep Power: 0	Maybe it's me. But I don't catch the details. Which code are you using to do it? What is a "train"? Why did you mention something about deforming mesh? I guess you want to define as "transparent" the surface that separates both sides of your mesh by marking it as "interior". Because one mesh is doing something more complex and the other one is extending the domain. But probably you don't need to go this way by just merge both meshes. The problem is this. If you treat both meshes separately even if you mark the intersection surface as interior. Any solver won't know how to deal with this unless it was specifically designed for this. Because each mesh has its own table for vertex to conform its cells, and hence, surfaces will be also duplicated even you said that this surface is interior. Ok, but how do you compute the fluxes in each face? Your solver should know how to pass the flux from one face to the other even if they are lying together. The best way to fix this is by merge both meshes at some point of your workflow, then any duplicity entity will be removed and you will be safe. Sorry if this answer doesn't help you, it is just what I understood.