configurable generic hdf5 readers #760
Draft
Conversation
This file contains 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
An idea how to make a configurable file reader in a way that it would be easy to add new hdf5 formats. We would need to specify which parts of the hdf5 file to read into which part of the Orange.data.Table. I know this is still a specific solution but maybe can be further generalized. Or we could go with several generic readers like spectral series, 2D maps, etc.
Also, we should think about better checks, like the silx project does to identify Nexus files.
@markotoplak and @stuart-cls it would be great if you could comment / improve on this idea and once the backend is worked out we could work on a configuration widget / menu.