Update on the development of the OpenFOAM CFD workbench (CFDOF)

[thschrader]

Hello Oliver,

I tried to do the same simulation like the "flooding-tank" tutorial from Jozsef Nagy on YT.
(The tank is flooded with water against gravity, like a fountain. The result should look like
the picture below). The calculation allways stops after 30s with openFOAM fatal error.
Probably I do something wrong with the field initialization or my workflow is garbage.
Please have a look at the FC-file. After writing the case you will see in the alpha.water-dict,
that the inlet/outlet values are not assigned (like in the alpha.water from tutorial), there
is a "TODO" entry. The blue cube is the initialization-zone for water.
regards Thomas
(the error "out of scope" on the mesh in tree has no effect...)

testCFD.FCStd

(183.19 KiB) Downloaded 34 times

floodingTank.JPG (51.57 KiB) Viewed 1166 times

alphaWaterCFDwb.JPG (25.52 KiB) Viewed 1166 times

alphaWaterTutorial.JPG (29.25 KiB) Viewed 1166 times

result_tutorial.JPG (24.12 KiB) Viewed 1166 times

[oliveroxtoby]

I tried to do the same simulation like the "flooding-tank" tutorial from Jozsef Nagy on YT.
(The tank is flooded with water against gravity, like a fountain. The result should look like
the picture below). The calculation allways stops after 30s with openFOAM fatal error.
Probably I do something wrong with the field initialization or my workflow is garbage.
Please have a look at the FC-file. After writing the case you will see in the alpha.water-dict,
that the inlet/outlet values are not assigned (like in the alpha.water from tutorial), there
is a "TODO" entry. The blue cube is the initialization-zone for water.

I thought that the alpha initialisation zone would cause the inlet alpha value to be set to 1, but I see that it doesn't work out like that.

The alpha inflow value can now be set in the boundary condition, and a couple of bugs are fixed. Should work now.

[thschrader]

@Oliver, short info
after updating CFDOF via addon-manager, close/restart FC:
try to mesh a cube. snappyhexMesh breaks,
gmsh/cfmesh works. system:
OS: Windows 10
Word size of OS: 64-bit
Word size of FreeCAD: 64-bit
Version: 0.17.12284 (Git)
Build type: Release
Branch: master
Hash: 2244292552c004e6b506af9e1e98d3423e524ee7
Python version: 2.7.8
Qt version: 4.8.7
Coin version: 4.0.0a
OCC version: 7.1.0
Locale: German/Germany (de_DE)

errorMesh.JPG (55.57 KiB) Viewed 1080 times

gmsh.JPG (117.46 KiB) Viewed 1080 times

[oliveroxtoby]

@Oliver, short info
after updating CFDOF via addon-manager, close/restart FC:
try to mesh a cube. snappyhexMesh breaks,
gmsh/cfmesh works. system:

Thanks - fixed.

[Worufu]

Is it possibile to have the "volumetric flow rate" and "mass flow rate" also in outlet as in inlet?

[oliveroxtoby]

Is it possibile to have the "volumetric flow rate" and "mass flow rate" also in outlet as in inlet?

At present the OpenFOAM boundary condition is only designed as an inlet (all three components of velocity are constrained); of course you can achieve much the same effect with the 'uniform velocity' outlet. If you would be interested, you could code up a new BC which allows users to specify mass flow rate and divides this by density and area to get the normal component of velocity.

[Worufu]

Is it possibile to have the "volumetric flow rate" and "mass flow rate" also in outlet as in inlet?

At present the OpenFOAM boundary condition is only designed as an inlet (all three components of velocity are constrained); of course you can achieve much the same effect with the 'uniform velocity' outlet. If you would be interested, you could code up a new BC which allows users to specify mass flow rate and divides this by density and area to get the normal component of velocity.

Thank for the information. It can be a good start to put me on coding in freecad. In your opinion is it possible to code all through python?

[makkemal]

believe this post is actually part of this thread
https://forum.freecadweb.org/viewtopic.php?f=18&t=24857

[oliveroxtoby]

Is it possibile to have the "volumetric flow rate" and "mass flow rate" also in outlet as in inlet?

At present the OpenFOAM boundary condition is only designed as an inlet (all three components of velocity are constrained); of course you can achieve much the same effect with the 'uniform velocity' outlet. If you would be interested, you could code up a new BC which allows users to specify mass flow rate and divides this by density and area to get the normal component of velocity.

Thank for the information. It can be a good start to put me on coding in freecad. In your opinion is it possible to code all through python?

Great! Yes, definitely possible in python.

[oliveroxtoby]

believe this post is actually part of this thread
https://forum.freecadweb.org/viewtopic.php?f=18&t=24857

Thanks for the notification.