What would you like to see added to MatNWB?
When reading an NWB file with nwbRead, all datasets of the file will be represented via the utility types DataStub or DataPipe, which provides a "memory map" interface to the actual data, i.e the actual data is not read into computer memory.
If an in-memory version of an NwbFile object obtained via nwbRead is exported to a new file, any DataPipe object will fail to transfer to the new file due to a limitation in the DataPipe interface.
See issue #713 for more details.
Is your feature request related to a problem?
Yes. Currently there is no easy way to "repack" a file that is imported with DataPipe objects
What solution would you like?
Implement method on bound DataPipe object to facilitate transferring data into a new file.
Do you have any interest in helping implement the feature?
Yes.
Code of Conduct
What would you like to see added to MatNWB?
When reading an NWB file with
nwbRead, all datasets of the file will be represented via the utility typesDataStuborDataPipe, which provides a "memory map" interface to the actual data, i.e the actual data is not read into computer memory.If an in-memory version of an
NwbFileobject obtained vianwbReadis exported to a new file, any DataPipe object will fail to transfer to the new file due to a limitation in theDataPipeinterface.See issue #713 for more details.
Is your feature request related to a problem?
Yes. Currently there is no easy way to "repack" a file that is imported with
DataPipeobjectsWhat solution would you like?
Implement method on bound
DataPipeobject to facilitate transferring data into a new file.Do you have any interest in helping implement the feature?
Yes.
Code of Conduct