CFD Online Discussion Forums

CFD Online Discussion Forums (https://www.cfd-online.com/Forums/)
-   OpenFOAM Meshing & Mesh Conversion (https://www.cfd-online.com/Forums/openfoam-meshing/)
-   -   [Commercial meshers] foam Mesh to Fluent (https://www.cfd-online.com/Forums/openfoam-meshing/69321-foam-mesh-fluent.html)

tachyon_me October 19, 2009 16:25
foam Mesh to Fluent
 
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

ronaldo October 21, 2009 02:59
Hi tachyon_me,

let me know ! It is 2D or 3D?

tachyon_me October 21, 2009 10:16
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 ....

ronaldo October 22, 2009 02:06
use fluent3DMeshToFoam and let me know ...

gwierink October 22, 2009 07:02
Code:
fluentMeshToFoam myMesh.msh -writeSets -writeZones -scale 0.001
also works most of the time for me (for a mesh called myMesh.msh in mm).

Cheers, Gijs

tachyon_me October 22, 2009 10:26
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 ...

jignesh_thaker2007 September 9, 2011 06:39
hello every one
 
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

Toorop January 27, 2012 06:43
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
I can make cellSets based on the regions, but it wont help foamMeshToFluent and I cannot see any special flag for the command.

nwpukaka October 20, 2014 22:39
Quote:
Originally Posted by Toorop (Post 341481)
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
I can make cellSets based on the regions, but it wont help foamMeshToFluent and I cannot see any special flag for the command.
Hi Tibor:

Are you now able to solve this limitation for foamMeshtoFluent?

Rophys September 16, 2015 14:02
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
Warning during the initialization

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.

Tobi February 2, 2017 06:10
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.

robboflea March 16, 2017 04:12
1 Attachment(s)
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

Tobi March 16, 2017 04:18
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.

arjun March 20, 2017 08:48
Quote:
Originally Posted by Tobi (Post 640949)
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.
Is there any way to know about mesh format that openfoam uses. If there is any information and someone willing to provide multi-region sample meshes then i might write down tool to convert openfoam to fluent.
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.

Tobi March 20, 2017 09:15
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.

KaLium April 21, 2017 05:24
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)

lukasf September 16, 2019 12:47
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.


All times are GMT -4. The time now is 23:33.