CFD Online Logo CFD Online URL
www.cfd-online.com
[Sponsors]
Home > Forums > OpenFOAM

properties of the interfaceProperties class

Register Blogs Members List Search Today's Posts Mark Forums Read

Reply
 
LinkBack Thread Tools Display Modes
Old   February 19, 2010, 04:54
Default properties of the interfaceProperties class
  #1
Senior Member
 
romant's Avatar
 
Roman Thiele
Join Date: Aug 2009
Location: Stockholm, Sweden
Posts: 348
Rep Power: 10
romant is on a distinguished road
Hej;

I have questions about the interfaceProperties class. What does
Code:
nHatf_
really present? It says something about a flux?

Also:

in the function calculateK()

in the first two lines
Code:
00101     const fvMesh& mesh = alpha1_.mesh();
00102     const surfaceVectorField& Sf = mesh.Sf();
some kind of mesh is created from alpha1, if I understand this correctly. What does this mesh represent? And is it possible to read do something like

Code:
surfaceScalarField& alphaAreas = mesh.magSf() ;
to retrieve some kind of area from the mesh, and if it is an area, is it the area of the alpha1 boundary within a cell?

If this does not work, is it possible to get the interface area between the two phases somehow else?

Thanks in advance!
__________________
~roman
romant is offline   Reply With Quote

Old   February 19, 2010, 06:18
Default
  #2
Senior Member
 
Kathrin Kissling
Join Date: Mar 2009
Location: Besigheim, Germany
Posts: 134
Rep Power: 7
kathrin_kissling is on a distinguished road
Hi romant,

nHatf_ is the normal vector on the interface. Important is: it is stored as a surfaceScalarField. This means, the values are defined at the face centres.
The f indizes this.
The _ means, it is a private variable.

mesh: mesh represents the mesh. The class behind is fvMesh meaning finite volume mesh. alpha_.mesh() gives you the mesh structure liing behind the alpha_ volScalarField. Now you can access different mesh properties like the volume of your cell, the cellCentres...

mesh.Sf() now gives you the the face area vectors of each controll volume face. It is defined as surfaceVectorField

mesh.magSf() will give you the magnitude of those area vectors (of the controll volume faces) which corresponds to the area of those faces.

If I understand you correctly, you want to calculate the area of the interface in that cell. But im afraid you won't get it that way.

If you have further questions, please feel free...

Best

Kathrin
kathrin_kissling is offline   Reply With Quote

Old   February 19, 2010, 06:23
Default
  #3
Senior Member
 
romant's Avatar
 
Roman Thiele
Join Date: Aug 2009
Location: Stockholm, Sweden
Posts: 348
Rep Power: 10
romant is on a distinguished road
nHatf_ cannot be the normal, because it is a scalar, the calculation is
Code:
nHatf_ = nHatfv & Sf;
where you take the inner product of vector, resulting in a scalar (as also the variable type of nHatf_ represents surfaceScalarField), I think nHatfv is the normal vector, but it cannot be easily accessed.
__________________
~roman
romant is offline   Reply With Quote

Old   February 19, 2010, 06:46
Default
  #4
Senior Member
 
J. Cai
Join Date: Apr 2009
Posts: 180
Rep Power: 7
chiven is on a distinguished road
Hi, romant,
I find it is said that "The interface.nHatf() represents a cell face unit interface normal flux." in the thread:
VOF method

chiven
chiven is offline   Reply With Quote

Old   February 19, 2010, 06:53
Default
  #5
Senior Member
 
romant's Avatar
 
Roman Thiele
Join Date: Aug 2009
Location: Stockholm, Sweden
Posts: 348
Rep Power: 10
romant is on a distinguished road
Hej,

I have read the same that it is some kind of flux (it actually says that in the source file as well), but the problem is, I don't completely understand the physical meaning of this flux. In my opinion flux should be some kind of per area per time, but there is not time involved here. So it might just be per area. Now comes the question, what area. From the calculations it should gives the magnitude of the normal vector of the cell faces onto the normal vector of the interface.

What is the physical meaning behind this?
__________________
~roman
romant is offline   Reply With Quote

Old   February 19, 2010, 08:20
Default
  #6
Senior Member
 
Kathrin Kissling
Join Date: Mar 2009
Location: Besigheim, Germany
Posts: 134
Rep Power: 7
kathrin_kissling is on a distinguished road
Sorry,

I was one step behind.
Do you want to acces nHatfv?


The flux: Maybe it ist just a kind of projecting it into the right direction?

Best

Kathrin
kathrin_kissling is offline   Reply With Quote

Old   February 19, 2010, 08:24
Default
  #7
Senior Member
 
romant's Avatar
 
Roman Thiele
Join Date: Aug 2009
Location: Stockholm, Sweden
Posts: 348
Rep Power: 10
romant is on a distinguished road
Nope, I don't want access to nHatfv otherwise I could just rewrite that part of the class.

I am trying to find a way to predict the interface area within the cell, therefore I am looking at almost everything that OpenFOAM can give me and try to make sense of it.
__________________
~roman
romant is offline   Reply With Quote

Reply

Tags
interfoam, multiphase, two-phase

Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are On


Similar Threads
Thread Thread Starter Forum Replies Last Post
mass flow in is not equal to mass flow out saii CFX 2 September 18, 2009 08:07
Properties of air versus temperature AND pressure Vincent Main CFD Forum 5 July 28, 2008 06:28
Errors running allwmake in OpenFOAM141dev with WM_COMPILE_OPTION%3ddebug unoder OpenFOAM Installation 11 January 30, 2008 21:30
Two-Phase Buoyant Flow Issue Miguel Baritto CFX 4 August 31, 2006 12:02
About UList and List class leosding OpenFOAM Running, Solving & CFD 1 December 2, 2005 00:52


All times are GMT -4. The time now is 02:42.