Contact interface and shared topology

  • 89 Views
  • Last Post 20 February 2019
  • Topic Is Solved
Glibrary posted this 09 February 2019

Hi,

I am trying to make a simple heat transfer simulation in a forced flow for practice and have a question on contact boundary condition.

The model is small aluminum cube inside a hot air domain with forced flow from the bottom.

I created the coupled mesh interface and set the (via system coupling) on the walls for boundary conditions of the cube.

I just wonder what's the difference between using shared topology (generate no contact region) and contact interface for boundary conditions.

As far as I know shared topology make shared nodes between fluid and solid domain and generate no contact region.

So, to me, shared topology seems simpler than using contact interface.

But I found many tutorials and examples using contact interface in the problem like this.

Are these, shared topology and contact interface, just same to each other or have benefits for a specific problem?

Thank you in advance.

  • Liked by
  • sma4t
Order By: Standard | Newest | Votes
rwoolhou posted this 11 February 2019

Shared topology is simpler in the solver, uses marginally less compute resource and is generally preferred. However, it does mean the solid mesh may be overly refined as it's linked to the fluid domain. 

As an aside, you only need system coupling if you want to stretch/strain/bend the metal bit: the CFD solvers are designed to model heat transfer in solids along with everything else in the fluid region. 

  • Liked by
  • peteroznewman
Glibrary posted this 20 February 2019

Thank you for your kind explanation!

Close