For complex meshes, it's possible for extraneous sidesets to exist in the mesh, possibly as artifacts of the mesh generation process (e.g. stitching). Users may also sometimes define sidesets for postprocessing operations, such as visualizing the solution on a complex surface. However, NekRS currently aborts if there is a sideset ID in the mesh that isn't mapped to a boundary condition. We can change the error into a warning instead to provide more flexibility in meshing.
stgeke
commented
2 years ago
For complex meshes, it's possible for extraneous sidesets to exist in the mesh, possibly as artifacts of the mesh generation process (e.g. stitching). Users may also sometimes define sidesets for postprocessing operations, such as visualizing the solution on a complex surface. However, NekRS currently aborts if there is a sideset ID in the mesh that isn't mapped to a boundary condition. We can change the error into a warning instead to provide more flexibility in meshing.