-
Notifications
You must be signed in to change notification settings - Fork 241
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
Chunk API: Add new API and functionality for reading and writing chunks #3794
base: develop
Are you sure you want to change the base?
Conversation
This pull request has been mentioned on Image.sc Forum. There might be relevant details there: |
/* @see IFormatWriter#setChunkSize(int[]) */ | ||
@Override | ||
public int[] setChunkSize(int[] chunkSize) throws FormatException { | ||
int[] returnChunkSize = {setTileSizeX(chunkSize[0]), setTileSizeY(chunkSize[1]), 1, 1, 1}; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Back to @melissalinkert's question about what would test this code, this could warn or error if a >2D chunk size were requested.
This pull request has been mentioned on Image.sc Forum. There might be relevant details there: |
Temporarily excluding since this is scheduled for 8.0.0 and conflicts with things scheduled for 7.1.0. |
An initial prototype of potential new API methods for reading and writing N dimensional chunks of data rather than 2d planes/tiles. These new methods currently have default implementations in FormatReader and FormatWriter than pass through to the current 2D API, so they should be useable. This will be accompanied by a PR on ZarrReader which would be the first instance of a Reader which uses the chunk API by default.
The naming and parameters are all open for debate/suggestions, one of the trickier areas with this is how to handle the DimensionOrder going forward. Currently it is reusing the existing 5D dimensionOrder string.