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
Here is the same mesh as a WaveFront .obj file nd STL format mesh. I can easily convert the vtk format file, but the converting the obj file results in a iwm.cbor file that has nonsense values.
The cells from the STL file are BigUint64Array with each triangle listed as 2 3 i j k where 2 is indicates a triangle type and 3 indicates that three indices follows, with i j k being the indices:
In contrast, all the values for the converted OBJ files are huge - out of range of all triangles and of invalid cell types:
3DSlicer, Meshlab, Surfice and NiiVue all open the OBJ file fine. I note that the ITK code is designed to read faces (f), vertices (v) and the optional vertex normals (vn), while this file only has vertices and faces, so perhaps ITK demands the normals.
The text was updated successfully, but these errors were encountered:
Here is the same mesh as a WaveFront .obj file nd STL format mesh. I can easily convert the vtk format file, but the converting the obj file results in a iwm.cbor file that has nonsense values.
The cells from the STL file are BigUint64Array with each triangle listed as
2 3 i j k
where2
is indicates a triangle type and 3 indicates that three indices follows, with i j k being the indices:In contrast, all the values for the converted OBJ files are huge - out of range of all triangles and of invalid cell types:
3DSlicer, Meshlab, Surfice and NiiVue all open the OBJ file fine. I note that the ITK code is designed to read faces (
f
), vertices (v
) and the optional vertex normals (vn
), while this file only has vertices and faces, so perhaps ITK demands the normals.The text was updated successfully, but these errors were encountered: