[petsc-users] Problem with PETSc + HDF5 VecView

Barry Smith bsmith at mcs.anl.gov
Thu Nov 27 11:30:31 CST 2014

> On Nov 26, 2014, at 11:53 PM, Jed Brown <jed at jedbrown.org> wrote:
> Barry Smith <bsmith at mcs.anl.gov> writes:
>>> On Nov 26, 2014, at 3:35 PM, Håkon Strandenes <haakon at hakostra.net> wrote:
>>> Is it really PETSc's taks to warn about this? PETSc should trust HDF5 to "just work" and HDF5 should actually print sensible warnings/error messages. Shouldn't it?
>>   Yes, but if we produce a nice error message it makes everyone's
>>   lives easier, including ours because we don't have to constantly
>>   answer emails about the same problem discovered by a new person
>>   over and over again. Hence we do this kind of thing a lot.
> The only concern is that the user might not exceed that depth, so why
> should they have to set an arbitrary and excessively big value?

   We could check the value of the environmental variable and print the error message when the error occurs and is returned up the HDF5 stack only.

> MPI_REQUEST_MAX and MPI_COMM_MAX also look like candidates for needing
> increases.
> Whoever is responsible for this perversion should be fired.

More information about the petsc-users mailing list