Closed lungsi closed 5 years ago
@lungsi It's going to be hard to diagnose this without more information. Could you please include either a minimal script to generate the NWB file or a link to the file on google drive or similar?
I think I might have found out the cause for the error.
In mynwbfile
above the TimeSeries
objects for the epochs
are not the same as those located in those available under .acquisition
. Instead, the TimeSeries
object I have associated with the epochs
are a snippet.
When I try to write mynwbfile
but pass the whole TimeSeries
rather than its snippet, I don't get the above RuntimeError: Unable to resolve reference
and the file get written.
I guess that means the TimeSeries
associated with an epoch
must be same as one of the TimeSeries
available in .acquisitions
. It cannot be a snippet. Am I right?
Yes, that's right. In fact, pynwb automatically forms a link from the epochs table to the TimeSeries
objects it references instead of storing that TimeSeries
object twice, so these is no need to store snippets.
Also, the TimeSeries don't need to be .acquisitions
, they can be from any part of the file.
1) Bug
mynwbfile
looks like thisI can access data from
mynwbfile
.Following
io = NWBHDF5IO("test.h5", mode="w")
doingio.write(mynwbfile)
results inEnvironment
Please describe your environment according to the following bullet points.