Skip to content
Snippets Groups Projects
Commit 0b573457 authored by Feliks Kiszkurno's avatar Feliks Kiszkurno
Browse files

Fix link to msh2vtu

parent 1d5e687a
No related branches found
No related tags found
No related merge requests found
......@@ -19,7 +19,7 @@ To use a mesh created by SALOME, it must be converted to the Gmsh file format fi
To extract a surface mesh (in order to define appropriate boundary conditions) one can use the tool [ExtractSurface]({{< ref "extract-surface" >}}) for different kinds of 3D meshes. Different tools like [ParaView](https://www.paraview.org/) are suited as well. Care must be taken to make sure that all element types are of dimension `d-1`, where `d` is the dimension of the bulk mesh, and that no degenerated elements are left in the mesh and all nodes are connected appropriately. Furthermore, ensure that the element orders match. In the current version ExtractSurface stores meshes of first order (linear elements), even when the input mesh was of second order (quadratic elements).
Alternatively, the tool [msh2vtu](https://ogstools.opengeosys.org/stable/user-guide/msh2vtu.html) can be used to convert Gmsh meshes to VTU and to extract boundary meshes directly from physical groups defined in Gmsh.
Alternatively, the tool [msh2vtu](https://ogstools.opengeosys.org/stable/auto_user-guide/plot_msh2vtu.html) can be used to convert Gmsh meshes to VTU and to extract boundary meshes directly from physical groups defined in Gmsh.
Heterogeneous fields, e.g., for the use as initial conditions, can be easily generated using the [VTUinterface](https://github.com/joergbuchwald/VTUinterface) Python package.
......
0% Loading or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment