Lines Matching refs:mesh

7 - the relationship between the layout of data over a mesh (or similar structure) and the data layou…
13 without explicit reference to the mesh (topology) or discretization (analysis).
15 While `PetscSection` is currently only employed for `DMPlex`, `DMForest`, and `DMNetwork` mesh desc…
16 …l explain the basic concepts of a `PetscSection` that are generalizable to other mesh descriptions.
22 …) in a `Vec` (or a simple array) can be associated with a "location" on a mesh (or other types of …
23 …cInt` that serves as an abstract "index" into arrays from iterable sets, such as k-cells in a mesh.
24 …volume grid, or as complex as the topological entities of an unstructured mesh (cells, faces, edge…
26 …` is a mapping between the mesh points and a tuple `(ndof, offset)`, where `ndof` is the number of…
27 So given the tuple for a mesh point, its data can be accessed by `array[offset + d]`, where `d` in …
29 ### Charts: Defining mesh points
31 The mesh points for a `PetscSection` must be contiguously numbered and are defined to be in some ra…
33 Note that even though the mesh points must be contiguously numbered, the indexes into the array (de…
34 In other words, there may be elements in the array that are not associated with any mesh points, th…
38 Defining the `(ndof, offset)` tuple for each mesh point generally first starts with setting the `nd…
40 If `ndof` is not set for a mesh point, it is assumed to be 0.
42 The offset for each mesh point is usually set automatically by `PetscSectionSetUp()`.
43 This will concatenate each mesh point's dofs together in the order of the mesh points.
46 Alternatively, the offset for each mesh point can be set manually by `PetscSectionSetOffset()`, tho…
60 …y discretizations, it is useful to differentiate between different kinds of dofs present on a mesh.
87 …is now three dimensional, with the outer dimensions being both indexed by mesh points and field po…
92 All the dofs for each mesh point are stored contiguously, meaning the fields are **interlaced**.
155 Assume the mesh points of the "global" mesh are partitioned among processes and that some mesh poin…
156 The shared mesh points define the ghost/halo points needed in many PDE problems.
157 For each shared mesh point, appoint one process to be the owner of that mesh point.
158 To describe this parallel mesh point layout, we use a `PetscSF` and call it the `pointSF`.
159 …intSF` describes which processes "own" which mesh points and which process is the owner of each sh…
161 … describes the mapping between that process's partition (including shared mesh points) and the dat…
224 …ction` associates multiple unit vectors with every mesh point (one for each dof) and divides the m…