Closed PetrKryslUCSD closed 2 years ago
I'm not sure, I'd need to check whether it's a requirement of the file format.
Do you have a minimal example?
ParaView doesn't seem to complain when I switch to Int64
. I'll push a fix.
Oh, that would be fantastic! My minimal example is a 24GB mesh file ;-) Many thanks!
BTW, the documentation refers only to 32-bit integers. I put the question to the technical support on the forum as well.
That's strange, I would expect recent versions of VTK to support Int64
as well.
Before merging #106, do you think you would you be able to test your large dataset on that branch, and then check if you can open the result in ParaView or similar? Thanks!
Will do!
From the file format docs:
The attributes of the DataArray elements are described as follows: type — The data type of a single component of the array. This is one of Int8, UInt8, Int16, UInt16, Int32, UInt32, Int64, UInt64, Float32, Float64. Note: the 64-bit integer types are only supported if VTK_USE_64BIT_IDS is on (a CMake variable—see “CMake” on page 8) or the platform is 64-bit.
So I guess Int64
should work just fine!
For a large mesh (840M tetrahedra), I got this error:
It is apparently due to the
offsets
being created asInt32
. Is this required by the file format? Could this be changed toInt64
?