You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I've noticed that since updating h5fortran from v4.2.11 to v4.10.2 (the latest release) that the sliced write of a lower-rank array into a larger-rank dataspace raises an error.
I'm referring to the case when some of the indices in istart and iend in sliced write are equal
This occurs when I want to write an essentially a lower-rank array dset into a larger-rank dataspace, and I extend the rank of dset with size-1 dimensions to match that of the dataspace. For those dimensions i, istart(i) == iend(i) and h5fortran raises an error.
It seems this is due to line 84 in write.f90, where an error is raised if any(iend <= istart)
if(any(iend <= istart)) error stop'ERROR:h5fortran:create: iend must be > istart'
If this condition is modified to allow for some iend == istart, as well as addressing lines 293--295 in utils.f90, the code executes without issues and the HDF5 file is written as expected.
Am I using the new API in a wrong way or is this a bug?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
I've noticed that since updating h5fortran from v4.2.11 to v4.10.2 (the latest release) that the sliced write of a lower-rank array into a larger-rank dataspace raises an error.
I'm referring to the case when some of the indices in
istart
andiend
in sliced write are equalThis occurs when I want to write an essentially a lower-rank array
dset
into a larger-rank dataspace, and I extend the rank ofdset
with size-1 dimensions to match that of the dataspace. For those dimensionsi
,istart(i) == iend(i)
and h5fortran raises an error.It seems this is due to line 84 in
write.f90
, where an error is raised ifany(iend <= istart)
If this condition is modified to allow for some
iend == istart
, as well as addressing lines 293--295 inutils.f90
, the code executes without issues and the HDF5 file is written as expected.Am I using the new API in a wrong way or is this a bug?
Beta Was this translation helpful? Give feedback.
All reactions