New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
save julia objects as a self contained group in a "normal" hdf5 file #398
Comments
Hi @tkuraku ,
this is already the case. On the more general case: Because I also found this lack of cooperability quite frustrating, I created #388 . This is possible but also a significant undertaking. |
I see, if you don't rely on the hdf5 binary it becomes a very big task indeed. Maybe a alternative for the case when you need cooperability have the jld2 provide a serialization and de-serialization function that can be used in conjunction with HDF5.jl using the hdf5 binaries, and in the case when you don't you can use the jld2 library as is? Maybe something like this:
Just an idea. Thanks for all your hard work! |
Hi, |
functions are the one main thing that JLD2 cannot store. (only by referencing the name...) |
This is a feature request that I had when I was interacting with some hdf5 files that were created from a separate program. With jld2 I can't save a Julia object into an existing hdf5 file because it isn't a "JLD2" file. Instead of making the file a JLD2 file, it would be super useful to have each saved Julia object to be a self contained jld2 group so that they could readily be saved into an existing "normal" hdf5 file. This would be awesome for interoperability for files that don't originate from Julia. In the same vain standard data types such as standard arrays could be transparently written and read like how they are in HDF5.jl, and only more complex Julia objects would need to be serialized into a JLD2 group.
The text was updated successfully, but these errors were encountered: