[seregaxvm]

Hello!
I'm trying to use chtMultiRegionFoam solver water cooling calculation of the imported CAD models (in this case FreeCAD).
I've tested my OpenFOAM project with 2D GMSH model and it worked fine. Now, when I import FreeCAD model in STEP format and prepare it using GMSH I have the following problems:

there's no heat transfer between regions (with compressible::turbulentTemperatureCoupledBaffleMix ed boundary condition);
volumetric heat source (neither scalarSemiImplicitSource not scalarCodedSource) doesn't produce any heat.

Could you please look at my project and tell me, what's wrong with it?

PS, boundary types are defined in system/changeDictionaryDict, boundary conditions are defined in system/[region]/changeDictionaryDict, volumetric heat source is defined in constant/heater/fvOptions
PPS, sorry for not following the OpenFOAM scripting convention. One can run project by issuing command

./clean && ./configure && ./run && ./viewfoam

[dlahaye]

Is the fluid domain gradually heating up with time?

[seregaxvm]

Basic setup is this. I have a tungsten heater split into two parts: heating volume (called heated) and the rest of the tungsten part (called tungsten). I's enclosed in copper shell, which is cooled by a water stream. Heater supposed to gradually heat up while the water is cooling it down.
In short my goal is to optimize the geometry of the copper shell and determine the water consumption to cool down a heating tungsten target.

[seregaxvm]

I was able to produce a minimal working example. Here I'm just testing for heat transfer in a solid cylinder (water is a placeholder). It seems that OpenFOAM does not account for boundary conditions when solving for temperature.



question3.zip

[seregaxvm]

I thing I'm onto the source of the problem.
There are two problems here. The first problem is a duplication of the shared surfaces. They can be removed by adding the following line

BooleanFragments{ Volume{:}; Delete; }{}

to the GMSH script (http://geuz.org/pipermail/gmsh/2019/012855.html). Second problem is a sneaky one. GMSH does not respect length units of the imported step file. To convert your step file to meters add line

Mesh.ScalingFactor=0.001;

to the GMSH script (Gmsh units?).

[seregaxvm]

For the sake of completeness, here's a working project watercooling.zip

[seregaxvm]

It's better to use

Geometry.OCCTargetUnit = "M";

instead of

Mesh.ScalingFactor=0.001;