Surfaces output for two regions.

Jan995 · October 28, 2020, 07:31

Hi,

I am doing conjugate heat transfer simulations, where I have two different regions. At those separate regions, I want to write temperature fields for specified surfaces. The problem is, that no matter how I write my code, OpenFOAM outputs only surfaces of one regions.

Please find the surfaces files in the attachment.

In controldict I simply put:
functions
{
include "surfaces"
include "surfaces2"
}

Thanks for the suggestions.

EDIT:
The above code works. If anyone needs it, take it.

olesen · October 31, 2020, 15:31

What you've noted is quite true and is a missing feature in OpenFOAM. Supporting it would take some additional work, here's my thoughts or explanation.
The surface sampling are built on top of region/mesh function object, which means their "natural" context is a single mesh region. For sampled patches (for an example) sampling on multiple regions doesn't make much sense. For samplers such as an isoSurface, cutting plane or a triSurface, covering multi-regions makes sense, but still has other issues. Probably cannot sample quantities that only exist in one region (eg, U) - need a zero of undefined for the other region? The various mesh searchers are for a single domain only.

So with these various issues, which sampler types do you think are absolutely needed to handle multi-domain?

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
[snappyHexMesh] handling of baffle regions or surfaces with zero thickness with snappyHexMesh	StSchiff	OpenFOAM Meshing & Mesh Conversion	5	March 8, 2017 10:45
[snappyHexMesh] Using snappyHexMesh for multiple enclosed regions	richard_vega	OpenFOAM Meshing & Mesh Conversion	0	November 13, 2014 15:28
Questions about data output	aki_yafuji	OpenFOAM Running, Solving & CFD	3	September 9, 2010 02:59
lift and drag on ship superstructures	vaina74	OpenFOAM Running, Solving & CFD	3	June 8, 2010 13:30
Help with DPM UDF for OUTPUT needed	Zhengcai Ye	FLUENT	0	January 5, 2004 17:58

October 31, 2020, 15:31		#2
olesen Senior Member Mark Olesen Join Date: Mar 2009 Location: https://olesenm.github.io/ Posts: 1,715 Rep Power: 40	What you've noted is quite true and is a missing feature in OpenFOAM. Supporting it would take some additional work, here's my thoughts or explanation. The surface sampling are built on top of region/mesh function object, which means their "natural" context is a single mesh region. For sampled patches (for an example) sampling on multiple regions doesn't make much sense. For samplers such as an isoSurface, cutting plane or a triSurface, covering multi-regions makes sense, but still has other issues. Probably cannot sample quantities that only exist in one region (eg, U) - need a zero of undefined for the other region? The various mesh searchers are for a single domain only. So with these various issues, which sampler types do you think are absolutely needed to handle multi-domain?