Skip to content

Opening of OME Zarr v0.5 datasets due to inconsistency of axes ordering - #49

Closed
stefanhahmann wants to merge 1 commit into
saalfeldlab:mainfrom
stefanhahmann:patch-ome-v05-axes-order
Closed

Opening of OME Zarr v0.5 datasets due to inconsistency of axes ordering#49
stefanhahmann wants to merge 1 commit into
saalfeldlab:mainfrom
stefanhahmann:patch-ome-v05-axes-order

Conversation

@stefanhahmann

Copy link
Copy Markdown
Contributor

This PR fixes the following bug: saalfeldlab/n5-viewer#54

I am a bit unsure, if there are any side effects by only re-ordering the axes in the deseralization step, but not in serialization step. Perhaps it should happen there as well.

OME Zarr v0.5 Metadata deserialization update:

  • Modified MultiscalesAdapter.deserialize to reverse the order of axes when constructing OmeNgffMultiScaleMetadata, ensuring axes are handled in the correct order.

Array reversal utility:

  • Added a generic reversedCopy method to MetadataUtils for creating reversed copies of arrays.

Testing:

  • Added MetadataUtilsTest with unit tests for reversedCopy, covering string, integer, and empty arrays.

* Add a new method reversedCopy() to MetadataUtils
* Add corresponding unit test
@bogovicj

Copy link
Copy Markdown
Collaborator

This is now merged and released, thanks @stefanhahmann

@bogovicj bogovicj closed this Mar 12, 2026
@stefanhahmann
stefanhahmann deleted the patch-ome-v05-axes-order branch March 13, 2026 10:17
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants