Re: [petsc-users] VecView output to HDF5 in 3.12.0 broken ?

Hi Barry, Looking at the current code, am I right in assuming that the change is only in naming conventions and not in logic? I'll make a MR soon. Thank You, Sajid Ali Applied Physics Northwestern University s-sajid-ali.github.io

Re: [petsc-users] VecView output to HDF5 in 3.12.0 broken ?

Thanks for figuring this out. We should have done this debugging and figured it out. I hunted through the HDF5 docs and includes and though they document the maximum chunk size they do not seem to have any way of getting it using the preprocessor or compiler (that it is not defined by a

Re: [petsc-users] VecView output to HDF5 in 3.12.0 broken ?

Hi PETSc-developers, I think I’ve found the commit that broke this. In MR-1706 , the definition of PETSC_HDF5_INT_MAX was changed from being set to 2147483647 to (~(hsize_t)0). This new

Re: [petsc-users] VecView output to HDF5 in 3.12.0 broken ?

Also, both versions of PETSc were built with ^hdf5@1.10.5 ^mpich@3.3 %gcc@8.3.0 so the error is most likely not from hdf5.

Re: [petsc-users] VecView output to HDF5 in 3.12.0 broken ?

Hi Stefano/PETSc Developers, The chunksize is indeed limited to 4GB as per this page : https://portal.hdfgroup.org/pages/viewpage.action?pageId=48808714. With a (complex) DMDA vector of size (16384,16384,2) I see that PETSc saves it as a hdf5 file with chunks of size (1024,1024,2). But with a