Support n5 end-chunks with chunksize differing from metadata chunksize #6890
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.
Turns out N5 chunks report their own size, which may differ from the chunk size specified in metadata for end-chunks (like, at the edges of the dataset). This PR introduces code into the wk chunk reading process that handles that.
First I tried reusing the chunkSizeAtIndex from our Neuroglancer Precomputed code, but it turns out that for N5 the bounding box is not a reliable source, chunks may or may not be truncated, so the chunk size mentioned in each chunk header should be used as the source of truth here.
Additionally, I renamed the TypedChunkReader to ChunkTyper, because its job is not actually reading anything, but converting a previously read byte array to a typed multi array.
URL of deployed dev instance (used for testing):
Steps to test:
Issues: