Which solvers and mesh export formats are compatible with CF-MESH+?
CF-MESH+ is a solver agnostic software and it is compatible with various other solvers, not just certain forks of OpenFOAM. However, we do understand the possible confusion and misunderstanding, that may arise from cfMesh history. Back in 2014, when we first launched cfMesh, it was originally built on top of foam-extend and/or OpenFOAM® libraries. Over time, the code base of cfMesh and CF-MESH+ has evolved. It is now possible to use CF-MESH+ with various solvers and mesh export formats, including those from the OpenFOAM Foundation as well as Fluent, AVL FIRE and SU2.
How to use CF-MESH+ with OpenFOAM released by the OpenFOAM Foundation?
By default, CF-MESH+ saves the mesh in binary/uncompressed OpenFOAM format. However, when the binary/compressed format is encountered by the newer OpenFOAM version, released by the OpenFOAM Foundation, it assumes the faces are written as a compact list. This is a slight deviation from the standard, and hence we offer the utility to convert the faces into the required format.
We have noticed that the problem does not occur when the -ascii and -uncompressed options are used. It is possible to use these options when the mesher is started from a console. They are also available from the GUI.
What about other solvers?
Whether you’re exploring alternative solvers, validating results across platforms, or prefer SU2 for specific simulations, you can integrate CF-MESH+ into your workflow with minimal effort since it also provides tetrahedral and hexahedral mesh templates and converters needed to export the mesh for the SU2 solver.
Which mesh export formats are available?
CF-MESH+ has long supported a range of mesh export formats, including Fluent, SU2, CGNS, and AVL FIRE.
We hope you have found this post useful, and that it has made you curious to try out our latest CF-MESH+, designed to alleviate you from the pain of meshing. Feel free to subscribe to our newsletter to follow the latest news in CFD meshing techniques.
