HDF5 engine / remote, small arrays #4609
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
eisenhauer
approved these changes
Aug 11, 2025
…tored locally. Read them locally in the HDF5 engine instead going remote. - Add DestructorClose() to HDF5 engine like other engines to avoid unnecessary warning from ~Engine()
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
HDF5 files in campaign version 0.5 has arrays with <=128 elements stored locally. Read them locally in the HDF5 engine instead going remote.
Add DestructorClose() to HDF5 engine like other engines to avoid unnecessary warning from ~Engine()