[Bug]: Non-DCI H5DataIO does not passthrough maxshape
property which crashes pynwb Timeseries
#1148
Labels
category: bug
errors in the code or code behavior
priority: medium
non-critical problem and/or affecting only a small set of users
Milestone
What happened?
The pynwb documentation provides an example of passing a
H5DataIO
object as thedata
argument to theTimeSeries
constructor. docs here. However, this only works in the case wheretimestamps=None
because, if timestamps is not None, then theTimeSeries
initializer will check for the presence ofmaxshape
and this fails becauseH5DataIO
does not have.maxshape
, it only has.io_settings["maxshape"]
.I raised this bug in pynwb here: NeurodataWithoutBorders/pynwb#1929
Are there any unintended side-effects of adding a
maxshape
getter toH5DataIO
?Should this be fixed in pynwb? Maybe its
TimeSeries
_check_time_series_dimension
can have a special case if the data object is H5DataIO.For now I will monkey-patch H5DataIO to add a
maxshape
property.Steps to Reproduce
Traceback
Operating System
macOS
Python Executable
Python
Python Version
3.9
Package Versions
h5py==3.11.0
hdmf==3.14.1
hdmf_zarr==0.8.0
pynwb==2.8.0
The text was updated successfully, but these errors were encountered: