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
The latest version of exo2nek changes the sideset IDs of the mesh, adding at least 100 to every sideset (and sometimes more if you are merging multiple meshes). The sideset IDs should remain untouched for nekRS, however, because the boundaryTypeMap parameter associates the boundary character ID (i.e. v, f, etc.) to the boundary with the same number as that character's position in the list. Therefore, the new exo2nek is incompatible with boundaryTypeMap.
The text was updated successfully, but these errors were encountered:
The latest version of
exo2nek
changes the sideset IDs of the mesh, adding at least 100 to every sideset (and sometimes more if you are merging multiple meshes). The sideset IDs should remain untouched for nekRS, however, because theboundaryTypeMap
parameter associates the boundary character ID (i.e.v
,f
, etc.) to the boundary with the same number as that character's position in the list. Therefore, the newexo2nek
is incompatible withboundaryTypeMap
.The text was updated successfully, but these errors were encountered: