Lines Matching refs:mesh

18 treats all the different pieces of a mesh, e.g. cells, faces, edges, and
24 All pieces of the mesh (vertices, edges, faces, and cells) are treated as *points* (or mesh entitie…
25 `PetscInt`. A mesh is built by relating points to other points, in
34 For example, we can encode the doublet mesh as in {numref}`fig_doubletMesh`,
39 A 2D doublet mesh, two triangles sharing an edge.
48 The Hasse diagram for our 2D doublet mesh, expressed as a DAG.
51 To use the PETSc API, we consecutively number the mesh pieces. The
62 First, we declare the set of points present in a mesh,
124 …ng functions over the mesh, such as the coordinates. The second method is to use a non-periodic to…
126 …mesh creation) creates a second, discontinuous coordinate field. These values can be accessed usin…
151 Specifically, it assigns a number of dofs to each mesh entity on the DAG.
153 Using the mesh from {numref}`fig_doubletMesh`, we provide an example of creating a `PetscSection` f…
215 …mesh point orientation information specifies how one mesh point is oriented with respect to anothe…
249 but the mesh itself. Once the mesh is partitioned and
257 pattern is determined jointly by the computational mesh and
270 the variables couple to the set of neighboring cells containing the mesh
290 - Traverse the mesh, picking out pieces (which in general overlap),
296 DMPlex separates these different concerns by passing sets of points from mesh traversal routines to…
299 about the mesh inside a `DMPLEX`.
301 The most common mesh traversal is the transitive closure of a point,
312 element point in the mesh DAG, where each point also has an orientation.
336 taking into account the orientations of various mesh points:
351 the mesh in the code above, so it will work for polyhedral cells, hybrid
409 As `dm` is a `DMPLEX` object representing a mesh, we first give it a *mesh name*, "plexA", and save…
426 If the *mesh name* is not explicitly set, the default name is used.
427 … the above `PETSC_VIEWER_HDF5_PETSC` format was used to save the entire representation of the mesh.
428 This format also saves global point numbers attached to the mesh points.
443 The first argument of `DMPlexSectionView()` is a `DMPLEX` object that represents the mesh, and the …
444 They are, in general, two different objects, and the former carries a *mesh name*, while the latter…
446 …mesh points, so each of them can also be tagged with a global point number in $X$; `DMPlexSectionV…
515 …lementation, and good load balancing, the 3.0.0 format changes the way the mesh topology is stored.
516 Different strata (sets of mesh entities with an equal dimension; or vertices, edges, faces, and cel…
548 DAG points (mesh entities) have an implicit global numbering, given by the position in `orientation…
566 We then create a `DMPLEX` object, give it a *mesh name*, "plexA", and load
567 the mesh as:
593 `PetscSF` that pushes forward $X$ to the loaded mesh,
595 number tags that we saved along with the mesh points.
597 As the `DMPLEX` mesh just loaded might not have a desired distribution,
598 it is common to redistribute the mesh for a better distribution using
617 Note that the new `DMPLEX` does not automatically inherit the *mesh name*,
619 that pushes forward the loaded mesh to the redistributed mesh, so, composed
621 directly to the redistributed mesh, which we call `sf`.
642 data layout directly to the redistributed mesh. It then
643 reconstructs the data layout `s` on the redistributed mesh and
682 ## Metric-based mesh adaptation
684 `DMPLEX` supports mesh adaptation using the *Riemannian metric framework*.
686 metric space dictates how mesh resolution should be distributed across
687 the domain. Using this information, the remesher transforms the mesh such
688 that it is a *unit mesh* when viewed in the metric space. That is, the image
692 One of the main advantages of metric-based mesh adaptation is that it allows
694 the shape and orientation of elements in the adapted mesh, as well as their
698 See {cite}`alauzet2010` for further details on metric-based anisotropic mesh
701 The two main ingredients for metric-based mesh adaptation are an input mesh
747 mesh (in an approximate sense). This is achieved using the $L^p$ normalization
770 Two different metric-based mesh adaptation tools are available in PETSc:
787 mesh adaptation using the routine