Add support for 64 bit exodus files.
Here is a snippet of an e-mail from @gsjaardema:
As to the issue with the ids – Exodus has the option to store some or all integers in a database as 32-bit signed integers or 64-bit signed integers. Looking at the vtkExodusIIReader.cxx file that was referenced in an earlier email, it looks like it does not support the 64-bit integer mode of exodus; but it would probably be fairly easy to add this support.
An exodus file that contains 64-bit integers can be read by an application that only wants 32-bit integers – the exodus library (actually netcdf) will convert the 64-bit integers to 32-bit integers with no checking on whether the values are truncated. It is possible that this is what is happening in this case, but I’m not sure how many nodes/elements are in Chris’s file. If the file has > 2Billion nodes or elements, then there are likely issues from reading this model in an application that converts 64-bit to 32-bit to 64-bit which is what it looks like Paraview is doing from a cursory examination of vtkExodusIIReader.cxx. If the model has less than 2B nodes and elements, then it is possible that the “global ids” stored in the id maps are larger than 2B. In this case, depending on how things are stored internally in the application, the application should give correct connectivity, but displays of labels would be incorrect due to again the 64-bit to 32-bit to 64-bit conversion.
Note from Alan – this sounds like a feature hole/ bug, as we ramp up to Exascale... Greg - could you elaborate on where you found this 32 bit conversions?
Marking required, since this impacts exascale.