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

resolve h5t native types in hdf5 utils #7

Open
gnwong opened this issue Sep 17, 2018 · 0 comments
Open

resolve h5t native types in hdf5 utils #7

gnwong opened this issue Sep 17, 2018 · 0 comments
Labels

Comments

@gnwong
Copy link
Contributor

gnwong commented Sep 17, 2018

I'm labeling this as a bug even though technically it doesn't break anything for the codes/machines we use.

It would be better for hdf5 utils to always set the datatype for the memspace (during read/write calls) to the native type for the machine. This way we will always be able to read/write from/to both little- and big- endian files regardless of the sex of the machine. As it stands, io ops are only possible if the endianness of the file is the same as the machine itself.

Because hdf5 utils handles io in a type-agnostic way, implementing this requires being able to resolve the h5t native type for any specific user-chosen variable format.

@gnwong gnwong added the bug label Sep 17, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant