Hi Jed,
I cannot reproduce the same problem in C (attached example). The C code works
fine on HDF 1.12.0 without problem. I am still confused why this happens.
Anyway, will use HDF5-1.10.6 with PETSc-3.13 at this moment.
Thanks,
Danyang
On 2020-06-13, 1:39 PM, "Jed Brown" wrote:
Can
Hi Jed,
These three extra arguments in h5dcreate_f are optional so I am not sure if
these three arguments cause the problem. The error is from h5dwrite_f where all
the arguments are provided.
I will try to see if I can reproduce the problem in C.
Thanks,
Danyang
On 2020-06-13, 1:39 PM,
Can you reproduce in C? You're missing three extra arguments that exist in the
Fortran interface.
https://support.hdfgroup.org/HDF5/doc/RM/RM_H5D.html#Dataset-Create
Danyang Su writes:
> Hi Jed,
>
> Attached is the example for your test.
>
> This example uses H5Sset_none to tell H5Dwrite
Hi Jed,
Attached is the example for your test.
This example uses H5Sset_none to tell H5Dwrite call that there will be no data.
4-th process HAS to participate we are in a collective mode.
The code is ported and modified based on the C example from
Danyang Su writes:
> Hi Jed,
>
> Thanks for your double check.
>
> The HDF 1.10.6 version also works. But versions from 1.12.x stop working.
I'd suggest making a reduced test case in order to submit a bug report.
This was the relevant change in PETSc for hdf5-1.12.
Hi Jed,
Thanks for your double check.
The HDF 1.10.6 version also works. But versions from 1.12.x stop working.
Attached is the code section where I have problem.
!c write the dataset collectively
!!!
CODE
Danyang Su writes:
> Hi Barry,
>
> The HDF5 calls fail. I reconfigure PETSc with HDF 1.10.5 version and it works
> fine on different platforms. So, it is more likely there is a bug in the
> latest HDF version.
I would double-check that you have not subtly violated a collective requirement
in
Hi Barry,
The HDF5 calls fail. I reconfigure PETSc with HDF 1.10.5 version and it works
fine on different platforms. So, it is more likely there is a bug in the latest
HDF version.
Thanks.
All the best,
Danyang
On June 11, 2020 5:58:28 a.m. PDT, Barry Smith wrote:
>
>Are you making HDF5
Are you making HDF5 calls that fail or is it PETSc routines calling HDF5 that
fail?
Regardless it sounds like the easiest fix is to switch back to the previous
HDF5 and wait for HDF5 to fix what sounds to be a bug.
Barry
> On Jun 11, 2020, at 1:05 AM, Danyang Su wrote:
>
> Hi All,
Hi All,
After updating to HDF5-1.12.0, I got some problem if some processors have no
data to write or not necessary to write. Since parallel writing is collective,
I cannot disable those processors from writing. For the old version, there
seems no such problem. So far, the problem only
10 matches
Mail list logo