|
[Sponsors] |
October 19, 2009, 16:25 |
foam Mesh to Fluent
|
#1 |
New Member
Join Date: Sep 2009
Posts: 17
Rep Power: 17 |
I'm trying to get foam mesh converted to fluent with
foamMeshToFluent I'm not sure how to get this correct ... my fluent mesh is missing all the cellZone information. So I dont have any additional fluid/porous zones in the mesh converted in fluent format .. Any help appreciated .. thanks |
|
October 21, 2009, 02:59 |
|
#2 |
Member
toto
Join Date: Jun 2009
Posts: 71
Rep Power: 17 |
Hi tachyon_me,
let me know ! It is 2D or 3D? |
|
October 21, 2009, 10:16 |
|
#3 |
New Member
Join Date: Sep 2009
Posts: 17
Rep Power: 17 |
Thanks, it's 3d mesh. I was able to get them after splitting the mesh based on cellzones. Let me also know if there are quick and better way of doing ....
|
|
October 22, 2009, 02:06 |
|
#4 |
Member
toto
Join Date: Jun 2009
Posts: 71
Rep Power: 17 |
use fluent3DMeshToFoam and let me know ...
|
|
October 22, 2009, 07:02 |
|
#5 |
Senior Member
Gijsbert Wierink
Join Date: Mar 2009
Posts: 383
Rep Power: 18 |
Code:
fluentMeshToFoam myMesh.msh -writeSets -writeZones -scale 0.001 Cheers, Gijs |
|
October 22, 2009, 10:26 |
|
#6 |
New Member
Join Date: Sep 2009
Posts: 17
Rep Power: 17 |
Thanks , Thats helpful...
But In my case I would like to convert SnappyHexMesh "FOAM Mesh" to fluent format while keeping all cellZone as separate fluid zones in fluent... I guess for this matter I cant do foamMeshToFluent -time 4 -writeSets -writeZones But otherwise if you would like to convert fluent mesh to foam the command suggested by Wierink works without a problem ... |
|
September 9, 2011, 06:39 |
hello every one
|
#7 |
Member
|
hi
how i run my openfoam case in to fluent. because when i apply foamDataToFluent then it only convert .dat file but how i generate case file? plz tel me |
|
January 27, 2012, 06:43 |
|
#8 |
Member
Tibor Nyers
Join Date: Jul 2010
Location: Hungary
Posts: 91
Rep Power: 17 |
Hi,
as I see, the problem of exporting the correct region names from a foamMesh to fluentMesh is still present in foamMeshToFluent command. The whole domain is exported, all the regions, but without any distinctive label, merged under the same placeholder / default region name. How can one overcome this limitation? How does the splitting method works that is mentioned earlier? I came up with this one: Code:
splitMeshRegions -cellZonesOnly -makeCellZones -overwrite |
|
October 20, 2014, 22:39 |
|
#9 | |
Member
Kan
Join Date: Feb 2014
Location: Australia
Posts: 54
Rep Power: 12 |
Quote:
Are you now able to solve this limitation for foamMeshtoFluent? |
||
September 16, 2015, 14:02 |
|
#10 |
Member
R. P.
Join Date: Jul 2010
Posts: 73
Rep Power: 16 |
Hi all,
I manage to export a mesh from fluent to OpenFoam; however, when I check the mesh (command checkMesh), I have 5 failures (see below). In addition, when I initialized the case I received a warming (see below). Anybody knows how to solve this problem? Thanks. CheckMesh Code:
Create time Create polyMesh for time = 0 Time = 0 Mesh stats points: 1463379 faces: 4298112 internal faces: 4207320 cells: 1417572 faces per cell: 6 boundary patches: 5 point zones: 0 face zones: 1 cell zones: 1 Overall number of cells of each type: hexahedra: 1417572 prisms: 0 wedges: 0 pyramids: 0 tet wedges: 0 tetrahedra: 0 polyhedra: 0 Checking topology... ****Problem with boundary patch 0 named Inlet of type patch. The patch should start on face no 4207320 and the patch specifies 4229394. Possibly consecutive patches have this same problem. Suppressing future warnings. ***Boundary definition is in error. 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 Inlet 9945 10132 ok (non-closed singly connected) Sym 39780 40512 ok (non-closed singly connected) Outlet 7527 7683 ok (non-closed singly connected) Inlet2 11466 11692 ok (non-closed singly connected) Wall 22074 22397 ok (non-closed singly connected) Checking geometry... Overall domain bounding box (-0.3000000142 -3.024070027e-14 -3.241690292e-09) (0.6500000309 0.800000038 0.800000038) Mesh (non-empty, non-wedge) directions (1 1 1) Mesh (non-empty) directions (1 1 1) ***Boundary openness (1.281722558e-05 0.01952710315 0.01952386798) possible hole in boundary description. ***Open cells found, max cell openness: 0.9711407906, number of open cells 4602 <<Writing 4602 non closed cells to set nonClosedCells <<Writing 89739 cells with high aspect ratio to set highAspectRatioCells Minimum face area = 3.116805768e-07. Maximum face area = 0.0001277530998. Face area magnitudes OK. ***Zero or negative cell volume detected. Minimum negative volume: -2.707374999e-08, Number of negative volume cells: 89739 <<Writing 89739 zero volume cells to set zeroVolumeCells Mesh non-orthogonality Max: 179.8440355 average: 35.79636703 ***Number of non-orthogonality errors: 265395. <<Writing 265395 non-orthogonal faces to set nonOrthoFaces ***Error in face pyramids: 538434 faces are incorrectly oriented. <<Writing 273039 faces with incorrect orientation to set wrongOrientedFaces Max skewness = 1.793962489 OK. Coupled point location match (average 0) OK. Failed 5 mesh checks. End Create time Create polyMesh for time = 0 Time = 0 Mesh stats points: 1463379 faces: 4298112 internal faces: 4207320 cells: 1417572 faces per cell: 6 boundary patches: 5 point zones: 0 face zones: 1 cell zones: 1 Overall number of cells of each type: hexahedra: 1417572 prisms: 0 wedges: 0 pyramids: 0 tet wedges: 0 tetrahedra: 0 polyhedra: 0 Checking topology... ****Problem with boundary patch 0 named Inlet of type patch. The patch should start on face no 4207320 and the patch specifies 4229394. Possibly consecutive patches have this same problem. Suppressing future warnings. ***Boundary definition is in error. 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 Inlet 9945 10132 ok (non-closed singly connected) Sym 39780 40512 ok (non-closed singly connected) Outlet 7527 7683 ok (non-closed singly connected) Inlet2 11466 11692 ok (non-closed singly connected) Wall 22074 22397 ok (non-closed singly connected) Checking geometry... Overall domain bounding box (-0.3000000142 -3.024070027e-14 -3.241690292e-09) (0.6500000309 0.800000038 0.800000038) Mesh (non-empty, non-wedge) directions (1 1 1) Mesh (non-empty) directions (1 1 1) ***Boundary openness (1.281722558e-05 0.01952710315 0.01952386798) possible hole in boundary description. ***Open cells found, max cell openness: 0.9711407906, number of open cells 4602 <<Writing 4602 non closed cells to set nonClosedCells <<Writing 89739 cells with high aspect ratio to set highAspectRatioCells Minimum face area = 3.116805768e-07. Maximum face area = 0.0001277530998. Face area magnitudes OK. ***Zero or negative cell volume detected. Minimum negative volume: -2.707374999e-08, Number of negative volume cells: 89739 <<Writing 89739 zero volume cells to set zeroVolumeCells Mesh non-orthogonality Max: 179.8440355 average: 35.79636703 ***Number of non-orthogonality errors: 265395. <<Writing 265395 non-orthogonal faces to set nonOrthoFaces ***Error in face pyramids: 538434 faces are incorrectly oriented. <<Writing 273039 faces with incorrect orientation to set wrongOrientedFaces Max skewness = 1.793962489 OK. Coupled point location match (average 0) OK. Failed 5 mesh checks. End Code:
--> FOAM Warning : From function List<tetIndices> polyMeshTetDecomposition::faceTetIndices(const polyMesh&, label, label) in file meshes/polyMesh/polyMeshTetDecomposition/polyMeshTetDecomposition.C at line 570 No base point for face 544557, 4(4 192002 192003 6), produces a valid tet decomposition. |
|
February 2, 2017, 06:10 |
|
#11 |
Super Moderator
Tobias Holzmann
Join Date: Oct 2010
Location: Bad Wörishofen
Posts: 2,711
Blog Entries: 6
Rep Power: 51 |
Dear all,
it is a bit terrible to read through this thread because everybody is talking about different things. The thread starter mentioned that he wants to convert an OpenFOAM mesh to a fluent mesh and not vice versa. Based on that, he had problems in converting the cell zone information. Thats simply because in the foamMeshToFluent application this is not considered. I am also looking for some modification to get the cellZone information. Does anyone has done this already or can provide a *.msh file with cellZones (simple cube with two cellZones and 100 cells) in ascii format? If yes, I can make a workaround and solve the problem.
__________________
Keep foaming, Tobias Holzmann |
|
March 16, 2017, 04:12 |
|
#12 |
Senior Member
Join Date: Nov 2011
Posts: 109
Rep Power: 14 |
Dear Tobi,
I came across this post and I thought I could post a mesh. It would be great if you could provide the CFD communitiy a workaround Thanks for the help! Rob |
|
March 16, 2017, 04:18 |
|
#13 |
Super Moderator
Tobias Holzmann
Join Date: Oct 2010
Location: Bad Wörishofen
Posts: 2,711
Blog Entries: 6
Rep Power: 51 |
Dear Robert,
my colleague does not need it anymore and I have a lot of things to do. I will check it out - maybe during the weekend but I cannot promise it. If I will succeed, I will kindly ask Henry Weller to patch the application. Thanks for your help.
__________________
Keep foaming, Tobias Holzmann |
|
March 20, 2017, 08:48 |
|
#14 | |
Senior Member
Arjun
Join Date: Mar 2009
Location: Nurenberg, Germany
Posts: 1,283
Rep Power: 34 |
Quote:
The reason is that FVUS-wildkatze solver can convert from Fluent and from starccm to its format. FVUS can also write in fluent format (i need to check if current version has but i know that there is code to write fluent file somewhere so its not a big deal). This opens up possiblity of openfoam users to use FVUS too, so it does interest me. |
||
March 20, 2017, 09:15 |
|
#15 |
Super Moderator
Tobias Holzmann
Join Date: Oct 2010
Location: Bad Wörishofen
Posts: 2,711
Blog Entries: 6
Rep Power: 51 |
You can just check out the foam converters. I think you will find all necessary information there. If you have a foamToFluentMeshExtend converter, please let the community know. I have not time to investigate into that right now.
__________________
Keep foaming, Tobias Holzmann |
|
April 21, 2017, 05:24 |
|
#16 |
Senior Member
Kal-El
Join Date: Apr 2017
Location: Finland
Posts: 150
Rep Power: 9 |
I don't know how to fix this, but you can go around it.
use foamToEnsightParts. You can import the part to fluent (file -> import -> Ensight) |
|
September 16, 2019, 12:47 |
|
#17 |
Senior Member
Lukas Fischer
Join Date: May 2018
Location: Germany, Munich
Posts: 117
Rep Power: 8 |
Use
foamMeshToFluent within the OpenFOAM case directory. It will create a folder fluentInterface in which you will find the OF mesh in fluent format. This command works with OpenFOAM 4.1. |
|
Thread Tools | Search this Thread |
Display Modes | |
|
|
Similar Threads | ||||
Thread | Thread Starter | Forum | Replies | Last Post |
[snappyHexMesh] How to define to right point for locationInMesh | Mirage12 | OpenFOAM Meshing & Mesh Conversion | 7 | March 13, 2016 14:07 |
Running UDF with Supercomputer | roi247 | FLUENT | 4 | October 15, 2015 13:41 |
Problem with rhoSimpleFoam | matteo_gautero | OpenFOAM Running, Solving & CFD | 0 | February 28, 2008 06:51 |
fluent add additional zones for the mesh file | SSL | FLUENT | 2 | January 26, 2008 11:55 |
[blockMesh] Axisymmetrical mesh | Rasmus Gjesing (Gjesing) | OpenFOAM Meshing & Mesh Conversion | 10 | April 2, 2007 14:00 |