|
[Sponsors] |
January 26, 2012, 09:10 |
Hypermesh Update????
|
#1 |
Senior Member
n/a
Join Date: Sep 2009
Posts: 199
Rep Power: 16 |
Hello Foamers. I am in the process of creating my 3D meshes with hypermesh, and need to know if there is any update regarding converting these hypermesh files into OpenFOAM? I did see a couple of threads regarding this same topic, but they are quite old. Can anyone please give me some feedback on this?
Cheers, Deji |
|
January 26, 2012, 09:13 |
|
#2 |
Senior Member
n/a
Join Date: Sep 2009
Posts: 199
Rep Power: 16 |
I think I've found the answer to my question,
Deji |
|
January 30, 2012, 04:26 |
|
#3 |
Senior Member
BastiL
Join Date: Mar 2009
Posts: 530
Rep Power: 20 |
||
January 30, 2012, 07:47 |
|
#4 |
New Member
Slawek
Join Date: Feb 2010
Posts: 1
Rep Power: 0 |
Hi,
you can export your mesh from Hypermesh directly to OpenFoam (it is possible from Hypermesh version 10.0). Or you can export from HM to fluent and then use fluentMeshToFoam. Slawek |
|
May 3, 2013, 07:51 |
|
#5 |
Senior Member
Rishi .
Join Date: Mar 2009
Posts: 149
Rep Power: 17 |
Although there is a direct way to export from HyperMesh to OpenFOAM, exporting via Fluent remains the most robust method (as of HyperMesh 12.0).
|
|
May 3, 2013, 08:14 |
|
#6 |
Member
Daniel Pielmeier
Join Date: Apr 2012
Posts: 99
Rep Power: 14 |
Currently exporting to fluent mesh is the more robust method as hellorishi already mentioned.
This is especially true for multi-region cases and if internal faces are required which is because the direct export from Hypermesh to Openfoam does not distinguish between internal and external faces. Everything is exported as a boundary. Exporting to fluent format first and using fluent*MeshToFoam creates boundaries for external faces and faceZones for internal faces if the recommended naming scheme is used in Hypermesh (i. e. prefixing internal faces with inte_). There are also some face ordering problems which can occur when using the direct export method. This however can be fixed by using renumberMesh. I have reported this issues to Altair and maybe this will be fixed eventually. |
|
May 14, 2013, 07:08 |
|
#7 |
Member
Daniel Pielmeier
Join Date: Apr 2012
Posts: 99
Rep Power: 14 |
Today I received an email from the Altair support. The issues I have reported will be fixed in the next Update which will be Hyperworks 12.0-110. Lets see if this improves direct export to OpenFOAM from Hyperworks.
|
|
October 3, 2013, 04:45 |
|
#8 | |
Member
Daniel Pielmeier
Join Date: Apr 2012
Posts: 99
Rep Power: 14 |
Quote:
The Hyperworks 12.0 SA Update which includes Hypermesh 12.0.110.40 fixes the above mentioned issues. Direct export to OpenFOAM significantly improved with this version.
|
||
|
|
Similar Threads | ||||
Thread | Thread Starter | Forum | Replies | Last Post |
Change "Implicit Mesh Update Interval" using UDF | ASimonsen | Fluent UDF and Scheme Programming | 2 | October 12, 2017 09:38 |
libsampling for DyM solver exporting vtk patch. Problem to update geometry | be_inspired | OpenFOAM Post-Processing | 3 | October 9, 2015 07:58 |
Using Workbench, CFX-Pre doesn't update mesh from upstream data | Shawn_A | CFX | 2 | November 25, 2012 13:06 |
Hypermesh Exporting | eishinsnsayshin | ANSYS | 0 | April 3, 2012 18:16 |
Hypermesh file to Fluent | Logesh | FLUENT | 1 | November 30, 2011 13:46 |