First Steps

First Steps

This section describes a possible general pre-processing workflow using some of the tools provided by OGS.

To set up a model domain, the project file *.prj requires additional files for the mesh and geometry to apply the boundary conditions accordingly.

The bulk mesh must be provided in VTKs *.vtu format, whereas the boundary and source term domains can be provided either in OGS’ internal geometry file format (filename extension: *.gml, not to be confused with the Geography Markup Language) or as a *.vtu file as well, containing a subdomain of the bulk mesh. Multiple *.vtu files can be provided in the project file using the <meshes> tag. We recommend the usage of the first method for simple 2D meshes with constant boundary conditions, whereas more complicated geometries and conditions might require the latter method. One general advantage in the utilization of *.vtu files is that they allow a definition of additional field variables at each mesh node/element in order to implement spatially varying boundary conditions in a similar manner as, e.g., defining inhomogeneous material properties in the bulk mesh.

The finite-element mesh must be created using external mesh generators. Simple meshes can be created using the OGS utility generateStructuredMesh or PyVista. More complicated geometries can be generated and meshed using, e.g., SALOME Platform or Gmsh.

To use a mesh created by SALOME, it must be converted to the Gmsh file format first. To exchange mesh files between SALOME and Gmsh, one can use the *.unv file format. Finally, the tool GMSH2OGS can be used for the creation of *.vtu files (Attention: GMSH2OGS currently accepts the Gmsh v2. ASCII format only. It might also be necessary to use the -e option to exclude lines before using the mesh files in OGS).

To extract a surface mesh (in order to define appropriate boundary conditions) one can use the tool ExtractSurface for different kinds of 3D meshes. Different tools like ParaView 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 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 Python package.

Finally, use the OGS utility identifySubdomains to make sure that the boundary and subdomain meshes are compatible with the bulk mesh in terms of node and element numbering. Using msh2vtu you may skip this step, since all submeshes are extracted from the bulk mesh.

This article was written by Joerg Buchwald. If you are missing something or you find an error please let us know.
Generated with Hugo 0.122.0 in CI job 437561 | Last revision: April 3, 2024
Commit: [PL/CT] Pass shape matrix cache to local assemblers of ComponentTransport 845cbb1  | Edit this page on