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
Currently when exporting from different backends, i.e HDF5 to Zarr, we run into a dtype conversion from "uint32" to "int32". This should not happen and should remain "uint32".
To reproduce, run the plot_convet_nwb_hdf5.py tutorial.
Is your feature request related to a problem?
No response
What solution would you like?
Explore either the zarr backend or the convert_dtype method in object_mapper.py in HDMF.
Do you have any interest in helping implement the feature?
What would you like to see added to HDMF-ZARR?
Currently when exporting from different backends, i.e HDF5 to Zarr, we run into a dtype conversion from "uint32" to "int32". This should not happen and should remain "uint32".
To reproduce, run the
plot_convet_nwb_hdf5.py
tutorial.Is your feature request related to a problem?
No response
What solution would you like?
Explore either the zarr backend or the
convert_dtype
method in object_mapper.py in HDMF.Do you have any interest in helping implement the feature?
Yes.
Code of Conduct
The text was updated successfully, but these errors were encountered: