Meshes

Here, a minimum of two files has to be provided. One for the mesh of the domain and one for the boundaries. However, arbitrary many mesh files can be provided. Generally, if the boundary conditions vary between boundaries, there should be one mesh file provided for each set of boundaries sharing the same conditions. Alternatively, boundary conditions can be manipulated via Python, too.

  <mesh>mesh_file_name.mesh_extension</mesh>

Axial symmetry

Additionally it can be specified, that the provided mesh should be axially symmetric:

  <mesh axially_symmetric="true">
      mesh_file_name.mesh_extension
  </mesh>

If this flag is set to “True”, the mesh will be “fully”, i.e., 360° symmetric. This also has an influence on the appropriate scaling of the source term (see Source term).

OGS follows a standard axis convention: XY is a horizontal plane and Z is vertical. By default the rotation will be around the Y-axis. Moreover, see specific body force for details on including the gravitational force in accordance with the axis definitions.


This article was written by Feliks Kiszkurno. If you are missing something or you find an error please let us know.
Generated with Hugo 0.122.0 in CI job 408829 | Last revision: January 12, 2024
Commit: [App|NodeWiseMeshPartitioner] Determine / append ghost nodes 8da02368  | Edit this page on