Movatterモバイル変換


[0]ホーム

URL:


Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up
Appearance settings

Understanding chunk size for 3D datasets#1400

kushalkolar started this conversation inGeneral
Discussion options

Trying to correctly understand optimal chunk size, from the docs:

The optimal chunk shape will depend on how you want to access the data. E.g., for a 2-dimensional array, if you only ever take slices along the first dimension, then chunk across the second dimenson. If you know you want to chunk across an entire dimension you can use None or -1 within the chunks argument, e.g.:

https://zarr.readthedocs.io/en/stable/tutorial.html#chunk-optimizations

If my data are 3D,[dim0, dim1, dim2], and I only ever slice alongdim0, such asa[0, :, :] ora[0:10, :, :], then would it be optimal to setchunks=(n, None, None) wheren is my typical slice length?

Thanks!

You must be logged in to vote

Replies: 2 comments

Comment options

yep, i think that would be reasonable! I would recommend trying this out with some sample data to see if it's ergonomic.

You must be logged in to vote
0 replies
Comment options

It seems likeNone is no longer used to specify no chunking along a specific dimension is no longer a part of the API. How is this specified with the latest version ofzarr? Thanks!

You must be logged in to vote
0 replies
Sign up for freeto join this conversation on GitHub. Already have an account?Sign in to comment
Category
General
Labels
None yet
2 participants
@kushalkolar@d-v-b

[8]ページ先頭

©2009-2025 Movatter.jp