Skip to content

Loading fields and other custom slices for structured arrays #112

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

Closed
jakirkham opened this issue Feb 10, 2017 · 2 comments · Fixed by #172
Closed

Loading fields and other custom slices for structured arrays #112

jakirkham opened this issue Feb 10, 2017 · 2 comments · Fixed by #172
Labels
enhancement New features or improvements release notes done Automatically applied to PRs which have release notes.
Milestone

Comments

@jakirkham
Copy link
Member

After discussion in issue ( https://github.com/alimanfoo/zarr/issues/110 ), a particular interesting case of slicing structured arrays stored in Zarr came up. In particular, it would be great to be able to slice particular field(s) (e.g. z[:, 'foo']). Related to this, it would be great if a particular range or index could be used (e.g. z[:5, 'foo'] or z[1, 'foo']).

@alimanfoo
Copy link
Member

alimanfoo commented Feb 10, 2017 via email

@jakirkham
Copy link
Member Author

Of course.

An interesting extension to this would be handling slicing of the record too (e.g. z[:5, 'foo', 1]) once issue ( https://github.com/alimanfoo/zarr/issues/111 ) is fixed.

@alimanfoo alimanfoo mentioned this issue Nov 7, 2017
6 tasks
@alimanfoo alimanfoo added this to the v2.2 milestone Nov 20, 2017
@alimanfoo alimanfoo added enhancement New features or improvements release notes done Automatically applied to PRs which have release notes. labels Nov 20, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New features or improvements release notes done Automatically applied to PRs which have release notes.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants