You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
#189 discusses multiple approaches to handling the_FillValue, which is used to to indicate faces with fewer nodes than MaxNumNodesPerFace for a mixed-topology grid (UGRID Conventions) Adtionally, if a face has fewer corners/edges than MaxNumNodesPerFace then the last face (column) indices shall be equal to _FillValue.
From what I've read, there doesn't appear to be a variable in the UGRID conventions that specifies the geometry of each face. However, knowing what geometry is constructed from each face is important for proper indexing and for creating geometries for visualization or locating the first instance of a _FillValue. See the figure below:
In this example, we have a mixed topology with MaxNumNodesPerFace = 6. Proposed in the introduction of a new variable i.e. Mesh2_face_geometry which would contain the geometry of each face based on the location of _FillValue. Alternately, the value representing each face would act as a maximum index for slicing, used to only return the values representing our geometry (no _FillValue is returned)
The text was updated successfully, but these errors were encountered:
Hi, Philip. We use a hybrid grid, and this would be a nice (and a necessary) feature for us. Adding a new uxarray variable seems OK if it makes the code efficient.
#189 discusses multiple approaches to handling the_FillValue, which is used to to indicate faces with fewer nodes than MaxNumNodesPerFace for a mixed-topology grid (UGRID Conventions) Adtionally, if a face has fewer corners/edges than MaxNumNodesPerFace then the last face (column) indices shall be equal to _FillValue.
From what I've read, there doesn't appear to be a variable in the UGRID conventions that specifies the geometry of each face. However, knowing what geometry is constructed from each face is important for proper indexing and for creating geometries for visualization or locating the first instance of a
_FillValue
. See the figure below:In this example, we have a mixed topology with MaxNumNodesPerFace = 6. Proposed in the introduction of a new variable i.e.
Mesh2_face_geometry
which would contain the geometry of each face based on the location of_FillValue
. Alternately, the value representing each face would act as a maximum index for slicing, used to only return the values representing our geometry (no_FillValue
is returned)The text was updated successfully, but these errors were encountered: