fireFoam "smallPoolFire3D" BlockMeshDict Input File

DineshMyilsamy · June 29, 2018, 03:42

Hi everyone I am a beginner to OpenFoam. Currently, I am practising OpenFOAM on Windows computer using blueCFD-Core2017.
I am specifically interested in fireFoam section. In the fireFoam section, I am practising a tutorial entitled as "smallPoolFire3D". Although I could simulate the tutorial I couldn't understand one thing in "blockMeshDict" input file. In that input file why the "inlet boundary" vertices have not mentioned? while the outlet, base and side vertices have specified.
Suppose if I want to change the inlet boundary face, what are the other input files that I have to consider?
I kindly request for your guidance.

Bloerb · June 29, 2018, 09:34

Only part of the wall is considered inlet.

if you execute blockMesh your mesh will not have an inlet.
You need to run

topoSet (puts all faces inside a box defined in topoSetDict into a faceZone)
createPatch -overwrite (creates an inlet patch using that faceZone, defined in createPatchDict)

to have the inlet.

Instead you could ofcourse also use more than 1 block in your blockMeshDict or specify an entire wall as inlet.

MiriDR · June 21, 2019, 10:08

Hi, I'm using smallPoolFire3D too.
My question is, should i define my inlet through the TopoSetDict or is it possible to select just a portion of my geometry, directly in the blockMeshDict, as inlet?

Bloerb · June 21, 2019, 11:05

Both options are viable.

You can either create a blockMeshDict with several blocks and assign the walls to different patches inside said blockMeshDict, or you can use topoSet.

topoSet takes an existing mesh and puts parts of it, in this case the boundary faces, into a group. That group is then used by createPatch to add a new patch. E.g inlet etc.

The advantage of topoSet is that you only need one block, the disadvantage is that you can't define the size of the said patch independently from the mesh. Since topoSet uses existing faces of an existing mesh, said mesh might not have faces which form an inlet of a certain size.

MiriDR · June 21, 2019, 11:17

The thing is I have already created the Input through the blockMeshDict, I selected a portion of a wall as inlet.
The problem is that the simulation just creates the mesh, it reads the pfile and then it stops. It does not compute the iterations. So i don't know where it can be the problem. Any idea?

June 29, 2018, 03:42	fireFoam "smallPoolFire3D" BlockMeshDict Input File	#1
DineshMyilsamy New Member Dinesh Join Date: Jun 2018 Posts: 15 Rep Power: 8	Hi everyone I am a beginner to OpenFoam. Currently, I am practising OpenFOAM on Windows computer using blueCFD-Core2017. I am specifically interested in fireFoam section. In the fireFoam section, I am practising a tutorial entitled as "smallPoolFire3D". Although I could simulate the tutorial I couldn't understand one thing in "blockMeshDict" input file. In that input file why the "inlet boundary" vertices have not mentioned? while the outlet, base and side vertices have specified. Suppose if I want to change the inlet boundary face, what are the other input files that I have to consider? I kindly request for your guidance.

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
[swak4Foam] funkyDoCalc with OF2.3 massflow	NiFl	OpenFOAM Community Contributions	14	November 25, 2020 04:30
polynomial BC	srv537	OpenFOAM Pre-Processing	4	December 3, 2016 10:07
[OpenFOAM.org] Error creating ParaView-4.1.0 OpenFOAM 2.3.0	tlcoons	OpenFOAM Installation	13	April 20, 2016 18:34
[swak4Foam] Problem installing swak_2.x for OpenFoam-2.4.0	towanda	OpenFOAM Community Contributions	6	September 5, 2015 22:03
[swak4Foam] funkySetFields compilation error	tayo	OpenFOAM Community Contributions	39	December 3, 2012 06:18

June 29, 2018, 09:34		#2
Bloerb Senior Member Join Date: Sep 2013 Posts: 353 Rep Power: 21	Only part of the wall is considered inlet. if you execute blockMesh your mesh will not have an inlet. You need to run topoSet (puts all faces inside a box defined in topoSetDict into a faceZone) createPatch -overwrite (creates an inlet patch using that faceZone, defined in createPatchDict) to have the inlet. Instead you could ofcourse also use more than 1 block in your blockMeshDict or specify an entire wall as inlet.

June 21, 2019, 10:08		#3
MiriDR New Member Miriana De Rose Join Date: Jun 2019 Posts: 8 Rep Power: 7	Hi, I'm using smallPoolFire3D too. My question is, should i define my inlet through the TopoSetDict or is it possible to select just a portion of my geometry, directly in the blockMeshDict, as inlet?

June 21, 2019, 11:05		#4
Bloerb Senior Member Join Date: Sep 2013 Posts: 353 Rep Power: 21	Both options are viable. You can either create a blockMeshDict with several blocks and assign the walls to different patches inside said blockMeshDict, or you can use topoSet. topoSet takes an existing mesh and puts parts of it, in this case the boundary faces, into a group. That group is then used by createPatch to add a new patch. E.g inlet etc. The advantage of topoSet is that you only need one block, the disadvantage is that you can't define the size of the said patch independently from the mesh. Since topoSet uses existing faces of an existing mesh, said mesh might not have faces which form an inlet of a certain size.

June 21, 2019, 11:17		#5
MiriDR New Member Miriana De Rose Join Date: Jun 2019 Posts: 8 Rep Power: 7	The thing is I have already created the Input through the blockMeshDict, I selected a portion of a wall as inlet. The problem is that the simulation just creates the mesh, it reads the pfile and then it stops. It does not compute the iterations. So i don't know where it can be the problem. Any idea?