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
What I thought was initially a yt bug (yt-project/yt#4334) is in fact an issue with the vtk pieces being loaded (see this comment in the yt PR that started to address it). The gist of it is that for some datasets, the connectivity arrays may contain invalid elements where all of the node indices in a given element point to the same index in the coordinate array. Simply removing those null elements from the connectivity arrays is sufficient -- and they do really seem to be extra (so coming from how those vtk files are originally written?). I'll open a PR here with a fix after the yt discussion is closed out...
The text was updated successfully, but these errors were encountered:
What I thought was initially a yt bug (yt-project/yt#4334) is in fact an issue with the vtk pieces being loaded (see this comment in the yt PR that started to address it). The gist of it is that for some datasets, the connectivity arrays may contain invalid elements where all of the node indices in a given element point to the same index in the coordinate array. Simply removing those null elements from the connectivity arrays is sufficient -- and they do really seem to be extra (so coming from how those vtk files are originally written?). I'll open a PR here with a fix after the yt discussion is closed out...
The text was updated successfully, but these errors were encountered: