[willsen]

Hello everyone,

Say that I have two fluid domains that share a common interface (the two domains have the same fluid but I define the domain as separate because I add a source term to one of the domain). What is the best interface modelling such that If a fluid particle is coming out from one domain and entering the adjacent domain that it will behave as if 'there is no interface separating the two domains'.
Currently I use translational periodicity for this interface modelling.

[Opaque]

NO need for interfaces, create a single domain with two meshes

create a subdomain on the region you want the source, and add the source as needed.

Nothing else, and it should work.

[willsen]

Hi,

Thank you for your reply! Appreciate it. But if one day i require to define two different domain types (say fluid domain and porous domain) that are adjacent to each other. Would it be appropriate to use translational periodicity for the interface modelling? Or do i need to use more advance interface modelling type like general connection?

[willsen]

I am not too sure how to define two separate meshes in one domain. To allow myself to choose different volumes within the same domain, I created an assembly file from CREO and then meshed in ANSYS CFX. In CFX-pre, it recognizes this geometry as consists of different parts which require interface modeling to be defined. I tried to create a single domain for this assembly, but default interface is created instead.

The geometry that i am referring to can be seen in the attached picture.

[Opaque]

It is OK to have an interface within a single domain. In such cases, the most common interface is the "General Connection", unless there is some type of periodicity (rotational or translational)

The need for a second domain usually comes from some physics modeling differences such as frame change, and domain type.