[luca1992]

Hi, I'm new on this forum, I'm trying to simulate a fire in a gallery. Until now I've done tutorials using icoFoam and simpleFoam on which there was material on the internet that helped me. I searched for the material on the internet on this solver, but there is practically nothing. I chose the fireFoam solver and then the folder smallpoolFire3D folder. The mesh that represents the puddle of fire is already present in the solver, now I created in Solidworks with a .stl file the gallery.
Now I created the triSurface folder in the constant folder where I put the .stl file and the surfaceFeatureExtractDict file that I copied from the tutorial of motorbike and I changed this file by putting inside the name of my file .stl. When I go to typing from surfaceFeatureExtract terminal I get some errors. Am I doing right or wrong? You can help me?
Thank you, greetings, Luca.

[ashish.vinayak]

Please read this post first. It is absolutely important that you give enough information before anyone can help you. I cannot promise that I might be able to help, but at least if someone sees your post later, he at least might understand what you're talking about.

I have several questions for you:

Originally Posted by luca1992

The mesh that represents the puddle of fire is already present in the solver, now I created in Solidworks with a .stl file the gallery.

First thing, what do you mean by this? Why do you use it?
Can you post some kind of picture as well?

Did you run blockMesh? What was the output?

What errors did you get?

I should add that your error is related to meshing and not fireFOAM.

Best regards,

Ashish

[luca1992]

Hello, you are perfectly right, my post was not absolutely complete and I knew it, just that I was out and so I had a limited connection and so I had put a point of reference(only few information) to see if there was someone who could help me later. When I said no one had answered me in the other post it was absolutely no criticism for forum users, do not get me wrong, but just did not get the answer. I've read your post and will post a fuller message, thank you for your advice. Sincerely, Luca.

[luca1992]

Thanks very very much for the reply. I will try to be as clear as possible, so maybe I'll be long, I hope not to scare you.

I have to simulate a fire in a tunnel. I chose to use fireFoam and then smallPoolFire3D(I think it is suitable to simulate a truck exploding). The version I'm using for OpenFOAM is 4, while the Linux version is 14.04 LTS. And in this version of OpenFOAM there is an AllRun file in which there are a number of commands to type before executing the solver. From what I understand, the blockMeshDict file contains the mesh of this heat puddle, which is represented by a cube and for me represents the truck exploding. So I have to put this heat puddle in the tunnel. I created with SolidWorks the .stl file of a tunnel and I set mesh coordinates so that I have the heat puddle approximately at the center of the gallery.
Then I wanted to generate the tunnel .emesh file through surfaceFeatureExtract, so I took the surfaceFeatureExtractDict file from the motorbike tutorial and after copying it to the system folder where there were already the blockMeshDict files of the puddle, fvSchemes, fvSolution, snappyHexMeshDict, topoSetDict and others and I adapt this file for my case. In the constant folder I created the triSurface folder and placed in it the tunnel.stl file. I had typed surfaceFeatureExtract on the terminal. Then I copied a file snappyHexMeshDict from the motorbike tutorial and I changed it and typed snappyHexMesh on the terminal, then I started the fireFoam solver typing fireFoam on the terminal. I still have to see how and in which file I have to set the tunnel file boundary conditions because now I started the solver but without these conditions and I do not know if in the end when I will open paraFoam it will still show the results.

The steps I run are these:
1) I create the .stl file of the tunnel and match the dimensions so that the cube that for me represents the heat puddle is in the interior of tunnel.
2) I run all the steps in the Allrun file
3) typed surfaceFeatureExtract on the terminal to generate the .eMesh file
4) Initially I typed in the terminal the command snappyHexMesh and the program created 3 timeframes and when after I typing in the terminal the fireFoam command to start the solver it gave me an error that did not find the pressure files in these three folders, so now I tried to start first fireFoam and then type snappyHexMesh, it all seems to work, but when I start playing on paraWiew then nothing happen and in the drop down menu the speed and pressure fields are not present.

Furthermore I tried to start the tutorial as it was done and it seems to work, when I press play on paraWiew I see the animation inside the cube that moves for the U and p fields. When I start the solver with the files I've added (that is, the .stl file of the tunnel in triSurface, and the two surfaceFeatureExtractDict and snappyHexMeshDict files copied by the motorbike tutorial and edited by me), even if it create the different folders at the various time steps and It all seems to have gone in the right direction, but when I press play on paraWiew, time runs but it stays fixed, without animation or other. So now I do not understand what I'm wrong, I've been looking for guides but there is really little online. I did tutorials on OpenFOAM that worked for me but this is harder than the ones I've done, I'm making many attempts to understand.

In addition to all this I have these doubts:
1) I have put the tunnel outside of the already existing cube made with blockMeshDict, now I am doubting that maybe I need to increase the size of the cube and put the tunnel inside the cube? As if the combustion develops only within the cube that representing the maximum domain of the problem.
2) After I generated the .stl file in ASCII, I should set the contour conditions, in which file I should do it?
3) Can I use a single .stl file or do I have to have multiple .stl files if I have to set contour conditions?
4) The tunnel is a closed semicircle with the diameter, I tried to do it first with a certain thickness and then thin, but I do not know whether it is better or right for one or the other. I did the entrance and exit faces of the tunnel with the mesh and did not leave them empty as they are in reality.

Sorry for the length and for my unfinished English, I hope you can help me. Thank you so much, greetings, Luca.

[luca1992]

This is the checkMesh file:

/*---------------------------------------------------------------------------*\
| ========= | |
| \\ / F ield | OpenFOAM: The Open Source CFD Toolbox |
| \\ / O peration | Version: 4.1 |
| \\ / A nd | Web: www.OpenFOAM.org |
| \\/ M anipulation | |
\*---------------------------------------------------------------------------*/
Build : 4.1-1e03d68d4f4e
Exec : checkMesh
Date : Aug 14 2017
Time : 20:37:19
Host : "ubuntu"
PID : 3095
Case : /home/luca/FoamCases/smallPoolFire3D
nProcs : 1
sigFpe : Enabling floating point exception trapping (FOAM_SIGFPE).
fileModificationChecking : Monitoring run-time modified files using timeStampMaster
allowSystemOperations : Allowing user-supplied system call operations

// * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * //
Create time

Create polyMesh for time = 0

Time = 0

Mesh stats
points: 226981
faces: 658800
internal faces: 637200
cells: 216000
faces per cell: 6
boundary patches: 3
point zones: 0
face zones: 0
cell zones: 0

Overall number of cells of each type:
hexahedra: 216000
prisms: 0
wedges: 0
pyramids: 0
tet wedges: 0
tetrahedra: 0
polyhedra: 0

Checking topology...
Boundary definition OK.
Cell to face addressing OK.
Point usage OK.
Upper triangular ordering OK.
Face vertices OK.
Number of regions: 1 (OK).

Checking patch topology for multiply connected surfaces...
Patch Faces Points Surface topology
base 3600 3721 ok (non-closed singly connected)
outlet 3600 3721 ok (non-closed singly connected)
sides 14400 14640 ok (non-closed singly connected)

Checking geometry...
Overall domain bounding box (125 70 430) (135 80 450)
Mesh has 3 geometric (non-empty/wedge) directions (1 1 1)
Mesh has 3 solution (non-empty) directions (1 1 1)
Boundary openness (1.06859e-16 -5.78848e-15 7.45879e-16) OK.
Max cell openness = 1.45717e-16 OK.
Max aspect ratio = 2 OK.
Minimum face area = 0.0277778. Maximum face area = 0.0555556. Face area magnitudes OK.
Min volume = 0.00925926. Max volume = 0.00925926. Total volume = 2000. Cell volumes OK.
Mesh non-orthogonality Max: 0 average: 0
Non-orthogonality check OK.
Face pyramids OK.
Max skewness = 1.36424e-12 OK.
Coupled point location match (average 0) OK.

Mesh OK.

--> FOAM Warning :
From function virtual Foam::polyMesh::readUpdateState Foam::polyMesh::readUpdate()
in file meshes/polyMesh/polyMeshIO.C at line 203
unexpected consequences. Proceed with care.
Time = 4.02

Mesh stats
points: 226981
faces: 658800
internal faces: 637200
cells: 216000
faces per cell: 6
boundary patches: 5
point zones: 0
face zones: 0
cell zones: 0

Overall number of cells of each type:
hexahedra: 216000
prisms: 0
wedges: 0
pyramids: 0
tet wedges: 0
tetrahedra: 0
polyhedra: 0

Checking topology...
Boundary definition OK.
Cell to face addressing OK.
Point usage OK.
Upper triangular ordering OK.
Face vertices OK.
Number of regions: 1 (OK).

Checking patch topology for multiply connected surfaces...
Patch Faces Points Surface topology
base 3600 3721 ok (non-closed singly connected)
outlet 3600 3721 ok (non-closed singly connected)
sides 14400 14640 ok (non-closed singly connected)
inlet 0 0 ok (empty)
galleria 0 0 ok (empty)

Checking geometry...
Overall domain bounding box (125 70 430) (135 80 450)
Mesh has 3 geometric (non-empty/wedge) directions (1 1 1)
Mesh has 3 solution (non-empty) directions (1 1 1)
Boundary openness (1.06859e-16 -5.78848e-15 7.45879e-16) OK.
Max cell openness = 1.45717e-16 OK.
Max aspect ratio = 2 OK.
Minimum face area = 0.0277778. Maximum face area = 0.0555556. Face area magnitudes OK.
Min volume = 0.00925926. Max volume = 0.00925926. Total volume = 2000. Cell volumes OK.
Mesh non-orthogonality Max: 0 average: 0
Non-orthogonality check OK.
Face pyramids OK.
Max skewness = 1.36424e-12 OK.
Coupled point location match (average 0) OK.

Mesh OK.

Time = 4.04

Mesh stats
points: 226981
faces: 658800
internal faces: 637200
cells: 216000
faces per cell: 6
boundary patches: 5
point zones: 0
face zones: 0
cell zones: 0

Overall number of cells of each type:
hexahedra: 216000
prisms: 0
wedges: 0
pyramids: 0
tet wedges: 0
tetrahedra: 0
polyhedra: 0

Checking topology...
Boundary definition OK.
Cell to face addressing OK.
Point usage OK.
Upper triangular ordering OK.
Face vertices OK.
Number of regions: 1 (OK).

Checking patch topology for multiply connected surfaces...
Patch Faces Points Surface topology
base 3600 3721 ok (non-closed singly connected)
outlet 3600 3721 ok (non-closed singly connected)
sides 14400 14640 ok (non-closed singly connected)
inlet 0 0 ok (empty)
galleria 0 0 ok (empty)

Checking geometry...
Overall domain bounding box (125 70 430) (135 80 450)
Mesh has 3 geometric (non-empty/wedge) directions (1 1 1)
Mesh has 3 solution (non-empty) directions (1 1 1)
Boundary openness (1.06859e-16 -5.78848e-15 7.45879e-16) OK.
Max cell openness = 1.45717e-16 OK.
Max aspect ratio = 2 OK.
Minimum face area = 0.0277778. Maximum face area = 0.0555556. Face area magnitudes OK.
Min volume = 0.00925926. Max volume = 0.00925926. Total volume = 2000. Cell volumes OK.
Mesh non-orthogonality Max: 0 average: 0
Non-orthogonality check OK.
Face pyramids OK.
Max skewness = 1.36424e-12 OK.
Coupled point location match (average 0) OK.

Mesh OK.

--> FOAM Warning :
From function virtual Foam::polyMesh::readUpdateState Foam::polyMesh::readUpdate()
in file meshes/polyMesh/polyMeshIO.C at line 203
unexpected consequences. Proceed with care.
Time = 4.06

Mesh stats
points: 226981
faces: 658800
internal faces: 637200
cells: 216000
faces per cell: 6
boundary patches: 3
point zones: 0
face zones: 0
cell zones: 0

Overall number of cells of each type:
hexahedra: 216000
prisms: 0
wedges: 0
pyramids: 0
tet wedges: 0
tetrahedra: 0
polyhedra: 0

Checking topology...
Boundary definition OK.
Cell to face addressing OK.
Point usage OK.
Upper triangular ordering OK.
Face vertices OK.
Number of regions: 1 (OK).

Checking patch topology for multiply connected surfaces...
Patch Faces Points Surface topology
base 3600 3721 ok (non-closed singly connected)
outlet 3600 3721 ok (non-closed singly connected)
sides 14400 14640 ok (non-closed singly connected)

Checking geometry...
Overall domain bounding box (125 70 430) (135 80 450)
Mesh has 3 geometric (non-empty/wedge) directions (1 1 1)
Mesh has 3 solution (non-empty) directions (1 1 1)
Boundary openness (1.06859e-16 -5.78848e-15 7.45879e-16) OK.
Max cell openness = 1.45717e-16 OK.
Max aspect ratio = 2 OK.
Minimum face area = 0.0277778. Maximum face area = 0.0555556. Face area magnitudes OK.
Min volume = 0.00925926. Max volume = 0.00925926. Total volume = 2000. Cell volumes OK.
Mesh non-orthogonality Max: 0 average: 0
Non-orthogonality check OK.
Face pyramids OK.
Max skewness = 1.36424e-12 OK.
Coupled point location match (average 0) OK.

Mesh OK.

End

[luca1992]

This is blockMesh:

blockMesh
/*---------------------------------------------------------------------------*\
| ========= | |
| \\ / F ield | OpenFOAM: The Open Source CFD Toolbox |
| \\ / O peration | Version: 4.1 |
| \\ / A nd | Web: www.OpenFOAM.org |
| \\/ M anipulation | |
\*---------------------------------------------------------------------------*/
Build : 4.1-1e03d68d4f4e
Exec : blockMesh
Date : Aug 14 2017
Time : 20:32:17
Host : "ubuntu"
PID : 2967
Case : /home/luca/FoamCases/smallPoolFire3D
nProcs : 1
sigFpe : Enabling floating point exception trapping (FOAM_SIGFPE).
fileModificationChecking : Monitoring run-time modified files using timeStampMaster
allowSystemOperations : Allowing user-supplied system call operations

// * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * //
Create time

Creating block mesh from
"/home/luca/FoamCases/smallPoolFire3D/system/blockMeshDict"
Creating curved edges
Creating topology blocks
Creating topology patches

Creating block mesh topology

Check topology

Basic statistics
Number of internal faces : 0
Number of boundary faces : 6
Number of defined boundary faces : 6
Number of undefined boundary faces : 0
Checking patch -> block consistency

Creating block offsets
Creating merge list .

Creating polyMesh from blockMesh
Creating patches
Creating cells
Creating points with scale 1
Block 0 cell size :
i : 0.166667 .. 0.166667
j : 0.166667 .. 0.166667
k : 0.333333 .. 0.333333


Writing polyMesh
----------------
Mesh Information
----------------
boundingBox: (125 70 430) (135 80 450)
nPoints: 226981
nCells: 216000
nFaces: 658800
nInternalFaces: 637200
----------------
Patches
----------------
patch 0 (start: 637200 size: 3600) name: base
patch 1 (start: 640800 size: 3600) name: outlet
patch 2 (start: 644400 size: 14400) name: sides

End

[ashish.vinayak]

Originally Posted by luca1992

Mesh OK.

--> FOAM Warning :
From function virtual Foam:olyMesh::readUpdateState Foam:olyMesh::readUpdate()
in file meshes/polyMesh/polyMeshIO.C at line 203
unexpected consequences. Proceed with care.
Time = 4.02

1. Well, your post has scared me for certain, however, it also did interest me. I ca look at it over the weekend as I am not sure how the surfaceFeatureExtract works. Until then, I would say (a little prematurely though, so proceed with care) that this warning that you are receiving, is the first point of contact. Why are you receiving it? (the blockMesh file is run at time=0 usually and hence this seems a little odd. Run the cavity tutorial to see a correct blockMesh file).

Originally Posted by luca1992

Initially I typed in the terminal the command snappyHexMesh and the program created 3 timeframes and when after I typing in the terminal the fireFoam command to start the solver it gave me an error that did not find the pressure files in these three folders, so now I tried to start first fireFoam and then type snappyHexMesh, it all seems to work, but when I start playing on paraWiew then nothing happen and in the drop down menu the speed and pressure fields are not present.

2. If it is missing pressure files in 3 folders, why don't you have them there? A nice tip here would be to simplify your case even further so that you can apply the most basic boundary conditions every, no burning no nothing, just "move some fluid within the system" and see if everything works.
Side question: What are these 3 folders you are talking about?

3. Again, this is a little premature but I would ideally use the blockMesh as an approximation for a tunnel, and use the snappyHexMesh feature to create another cube inside it that can you used as your burning truck. But again, I don't have a lot of experience with SHM.

I'll look into the SHM thing over the weekend, but I am writing my thesis so I'm a little short on time. Good luck!

[Roman1]

Hello. I am not quite sure what your task is, but after having read your post:
- examples always work fine, there are all files that needed for running the case. Try to find the files that you need in the other examples;
- to create .stl or .obj file one can use the site clara.io.
-try to print commands by yourself like -blockMesh, -snappyHexMesh instead of AllRun. It is useful for understanding how it all works.

[luca1992]

Hi ashish.vinayak, thanks first for the answer. I understand that you have to devote yourself to your thesis, obviously only answer me if you have time, good luck also to you and thank you.

As for the error that gave me blockMesh, I resumed the original file and now it does not give me any errors and even checkMesh is all right. I thought the mistake was due to the fact that I had modified the proportions of the cube, but now I did another attempt and even modifying the proportions is all right, I do not know what had happened. When I start snappyHexMesh this command creates three folders that are 0.01 then 0.02 and 0.03 and what I understand from this other post in the forum are the various steps of creating the mesh and so it is right that they do not contain the files like the pressure, only that when I start the fireFoam solver it thinks it is time step folder and then gives me that error that does not find the pressure, then following the forum post's advice(https://www.cfd-online.com/Forums/op...pyhexmesh.html) I copied the files that were in the 0.03 folder and copied them into folder 0 after I deleted the three folders 0.01 and 0.02 and 0.03. After that I started the fireFoam solver and after opening the paraWiew I clicked on the play button and the U and p fields produced an animation but only inside the cube. I used snappyHexMesh because of what I understand to make more complex shapes this is to be used, and since the gallery was curved instead of making use of all the arc functions I used this feature. I do not understand why I have to create another cube that represents the truck, is not the heat puddle present in the original case representing what explodes? My question is therefore, the original cube created with blockMeshDict represents the maximum domain? So I have to put the tunnel inside this cube? I have until now put the tunnel out of the cube but never came out of the cube, maybe that's why?(you can see the photo that I attached)

Hi Roman1, thanks for the reply. The original example works well and has all the files to launch the case, but I have to add files to create the tunnel and it did not work. Now, however, when starting paraWiew and pressing play the U and p fields move (there is an animation) even if the tunnel geometry is present. Thanks for the site's advice, I'm seeing it, it's the first time I see it then it seems a bit complicated, before learning how to use this new program, I would like to see if the .stl file I created with SolidWorks works so to understand what am I doing wrong(but I will try to use this program when I have a bit of time). If I do not start the commands in the Allrun file then when I go to start the fireFoam solver I'm from errors.

I attach 2 photo of the file allrun and the total geometry

[ashish.vinayak]

Hi Luca,

What you did by deleting the 0.01 etc. folders is correct. That is what I would have done as well.

In the Allrun script you have something called ph_rgh. Are you sure this must be ph_rgh and not p_rgh?

Your question of blockMesh setting bounds to the entire mesh may be right, however, I cannot confirm this with full certainty. I say this because when you run checkMesh the following statement in the output:

Overall domain bounding box (125 70 430) (135 80 450)

As far as I understand this is the bound set by the blockMesh file.

To confirm whether this is the case, you could possibly reduce the dimensions of your .stl file and place it within the blockMesh box and use it as a truck. (just for now, use a simple geometry), and see what happens. Maybe that might help to understand what the error is.

Secondly, you say that you are able to run to run the script, could you post the log file for the entire Allrun script ?

Best regards,
Ashish

[luca1992]

Hello,

perfect , I deleted those 3 folders and first put the contents of the last one in folder 0. No I'm not sure what it should be, I thought that file was just right so and for this reason before running the solver I typed the instructions (I attach the photo of the files in the folder 0), regarding the Allrun commands I think it have all gone well except that where says

# set application nameApplication = `getApplication`

in which I did not understand well what to do if I have to choose a name, I also searched for guides on this file but I did not find anything. Those coordinates represent the dimensions of the central parallelepiped which represents the heat puddle. I will try to put the tunnel in the cube.

I did not understand what to do about the log file of the Allrun script.

Since I had errors this morning with snappyHexMesh I wanted to try to simplify it how you said, and so I want to try to create a tunnel but instead with file.stl and snappyHexMesh, with blockMesh and I do a tunnel with a rectangular section which in any case also exist in reality. In this case, since I have two blockMeshDict files, I'm not sure how to distinguish between calls to the two files(and when I run blockMesh), I leave one of the file in the system folder (that of the heat puddle) and the other(the tunnel) put it in constant / polyMesh?

Thank you, Luca.

[ashish.vinayak]

I would suggest you to take it one step at a time. Since you are not sure what to do with the two blockMesh files, go back to the basics and look online for tutorials on chtmultiRegionFoam. That will help you understand what to do when you have multiple blockMeshDict (i.e multiple regions) files and how to set up the case.


Run the following command in terminal:
./Allrun and post the log files generated as an attachment or zip folder. In your case, the following log files should be generated:
log.blockMesh
log.topoSet
log.createPatch
log.decomposePar
log.fireFoam

The application='getApplication' looks for which solver is asked for in the controlDict file.
I just noticed in your ./Allrun file that you are using a parallel run. Is your computer set up correctly to execute this? Run a serial case first! Its easier to debug. In this case, comment out the decomposePar line and replace runParallel by runApplication.

Another thing in the ./Allrun file, I don't see that you used any snappyHexMesh commands. Where are they/ why are you running them separately ?
--
Sorry to repeat this, but keep things simple. When a simple thing works correctly and you are sure about it, go further with making it more complicated. There is no other way

[luca1992]

Hello,

I agree with you and i am trying to go step by step, i have done other tutorials before this,i am new on this forum but before i worked on OpenFOAM, i have translated guides, i did not start now using openfoam, i would not you think that i was engage a little and i want others to do my job, just that every time there is more difficulty and new problems that I encountered. I want to learn and I'm engage but I do not understand these programs done in this way where there is not a precise, official and complete guide that tells you what you have to do clearly, or at least orientally what you have to do, so it just seems to go to try and surely it improves and I learn from mistakes, but without knowing clearly why and it seems very casual and costly from the point of view of time, so I do not like it. I agree to spend time behind this job, but much is unprofitable and lost time. And I am very sorry to waste time on other people on my job by asking many questions on the forum but I do not know how else to do. I searched tutorials on chtmultiRegionFoam, but I only saw that users make subfolders for each mesh or geometry. Others use mergeMeshes <master case> <add houses> and stitchMesh <master patch> <slave patch> while others merge in file blockMeshDict through mergePatchPairs commands and then choose between face matching and face merging but i do not think it is my case.

I launched ./Allrun but at one point it stopped and made a mistake and then generated the files in part. Now i'm doing other attempts but i will load these log files.

I tried to do it in serial and not in parallel but I'm having memory problems it seems to me.

So in place of getApplication do I have to put 'fireFoam'?

In the allRun file there are no snappyHexMesh commands because I run all the commands by simply typing them to the terminal and then the Allrun file contains only the original commands, this is because if I start up then it does not let me see the individual steps.

Do you know some complete guide on openfoam and especially on firefoam and smallpoolfire?

Now I am looking for information on this error on the internet when I start firefoam:

--> FOAM FATAL IO ERROR:
Cannot find patchField entry for galleria

file: /home/luca/FoamCases/smallPoolFire3D/0/p.boundaryField from line 26 to line 20.

From function void Foam::GeometricField<Type, PatchField, GeoMesh>::Boundary::readField(const Foam:imensionedField<TypeR, GeoMesh>&, const Foam::dictionary&) [with Type = double; PatchField = Foam::fvPatchField; GeoMesh = Foam::volMesh]
in file /home/ubuntu/OpenFOAM/OpenFOAM-4.1/src/OpenFOAM/lnInclude/GeometricBoundaryField.C at line 191.

FOAM exiting

Thank you , best regard, Luca.

[ashish.vinayak]

You do not have to replace 'getApplication' by fireFoam, it does it automatically for you in the script. The functions which does it automatically are loaded from the following line in the ./Allrun script. The getApplication makes the call to fireFoam so you don't need to alter it.

. $WM_PROJECT_DIR/bin/tools/RunFunctions

Why do you think you are having memory problems?

As far as I know, there are no tutorials on fireFoam. However, I myself am writing one, and will share it to CFD-online once I'm done with it. This will take some time.

The chtMultiRegionFOAM tutorials will help you set up a case when you have 2 blockMesh files.
Hint: do you know what happens when you write the blockMesh command?


The error that you have received means that you have not defined a boundary patch field called 'galleria' in 0/p.

Look at the poolfire tutorial again, and see if you understand everything in it, especially with regards to boundary conditions, alter things, experiment with it. Create errors on purpose, only then will you learn. You don't need to be sorry about anything. I'm happy to help you, since I find that even though OpenFOAM can be frustrating at times, it is very rewarding in the long run.

Good luck.

[luca1992]

Hello

ah ok for Allrun, thank you.

I think i have memory problems because some times i started snappyHexMesh gave me this kind of error (place 2 photos). I might have too many cells, even though it says I did not necessarily go out of the memory. Now I have try to reduce the number of refinement.

I think I know what happens when typing blockMesh. In short the blockMeshDict file is invoked and instructions inside it are executed, and then the mesh is generated.

I went to tutorials / heatTransfer / chtMultiRegionSimpleFoam / heatExchanger / system and found two folders named "air" and "porous" where inside each there is a blockMeshDict file. The same two folders with other files inside are also present in the "constant" and "0.orig" folder of the case. So should I also do this division to have two blockMeshDict files?

I'm still experimenting, but I have not yet realized if the geometry I create I have to put out or inside the boundaries of the original blockMeshDict file, i'm trying.

Thanks for the tips and suggestions.

Thank you very much , Luca.