Skip to content
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

Compound Datatype #22

Open
jmcous opened this issue Sep 30, 2021 · 3 comments
Open

Compound Datatype #22

jmcous opened this issue Sep 30, 2021 · 3 comments

Comments

@jmcous
Copy link

jmcous commented Sep 30, 2021

First off, thank you for your work on this project. It has been a great help to me!

Secondly, are there any plans to implement the h5 compound datatype? I tried, then was thrown the message "not yet implemented!"

@bmaranville
Copy link
Member

bmaranville commented Sep 30, 2021

The short answer is that I will probably be focusing future development efforts on h5wasm instead of this library. It supports almost all the hdf5 features at some minimal level because it is using the C / C++ API. The way you use h5wasm is very similar to how you use jsfive.

Can you tell me more about how you want to use compound data types? Is it to support complex numbers? If you wouldn't mind uploading (to this comment thread) an example HDF5 file with a compound dataset of the type you're interested in reading, I would appreciate it.

If there is some reason you would strongly prefer to continue using jsfive instead of h5wasm I'd also be curious to hear about that!

@jmcous
Copy link
Author

jmcous commented Sep 30, 2021

I may be able to upload something tomorrow but right now I can tell you that the datatype is Compound and contains members that are, for example, array, single, and uint8. My experience with H5s is minimal so apologies if something I say is confusing haha.

I will check out h5wasm as well.

@bmaranville
Copy link
Member

Ah - I do not have any code for specifically handling "array" datatypes. You should still be able to retrieve the raw bytes for the compound dataset, and you can do slicing in h5wasm. I don't think it would be much work to add handlers for nested datatypes, though they won't be as fast as other types of access since you have to parse the data row-by-row

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants