How many mesh continuum for 2physic continuums in conjugate heat transfer?two or one?
 

I want to simulate a conjugate heat transfer model.
Consider a Block with a solid continuum which is surrounded by another block which has fluid continuum.
Is there anyone knows the difference between :
a ) having one mesh continuum for each physic continuum.
in comparison to:
b ) having one mesh continuum for both of them.
(the mesh model can be surface remesher and any Volume mesh....)
As you know, Both of "a" and "b" are possible.

You have to use one mesh continuum for both regions. Because you need interfaces with conformal meshs and this can only be created with one mesh continuum. If you use one mesh continuum for each region (two mesh continua) the interface will not have a conformal mesh.

willimanilli is right. Although it's possible to have a separate mesh continuum for each region (and sometimes necessary), it is not recommended. Better to mesh all regions at at time with one mesh continuum ("per region meshing" unticked).

Hi,
I have read your answer.

I want to create a mesh with different base size (in bulk but with conformal mesh at the interface).
What do I have to do?

Best Regards,
tH3f0rC3

I'm new to STAR-CCM+ but i think by using 'volumetric control' you can have different mesh size in the places and areas you want.
e.g. making a block in the volume you want to have a finer mesh.
make a new volumetric control and assign the block to this volumetric control.then you will be able to set different mesh sizes...

Thanks for your answer.
I will try...

I've tried after reading the user manual page 7171 ff.
I'm afraid it doesn't work. The volumetric conrol doesn't seem to have an influence on the mesh creation. The mesh is still uniform.

Maybe you know how to proceed?!

Best regards,
tH3f0rC3

Now it works.

You have to define the volume control to the volume where you want to have a finer mesh. I did it the other way round. Than I specified an absolute size greater than the base size of the mesh. Star-CCM+ doesn't like this way :-)

sorry, wrong thread