Closed will-moore closed 3 weeks ago
@will-moore: can you look at my few extra commits? This now saves the labels details as well so that they can be edited. e.g.:
diff -C 3 <(jq . < /tmp/6001240.config) /tmp/6001240.config.fixed
*** /dev/fd/63 Tue Aug 20 14:58:11 2024
--- /tmp/6001240.config.fixed Tue Aug 20 14:55:27 2024
***************
*** 74,82 ****
],
"shards": [
1,
! 236,
! 275,
! 271
]
},
"zarr/v0.4/idr0062A/6001240.zarr/labels/0/1": {
--- 74,82 ----
],
"shards": [
1,
! 59,
! 69,
! 136
]
},
"zarr/v0.4/idr0062A/6001240.zarr/labels/0/1": {
***************
*** 94,102 ****
],
"shards": [
1,
! 236,
! 137,
! 135
]
},
"zarr/v0.4/idr0062A/6001240.zarr/labels/0/2": {
--- 94,102 ----
],
"shards": [
1,
! 118,
! 69,
! 68
]
},
"zarr/v0.4/idr0062A/6001240.zarr/labels/0/2": {
Worked fine for me: 👍
$ ome2024-ngff-challenge /Users/wmoore/Desktop/ZARR/data/6001240.zarr 6001240_details.json --output-write-details
$ code 6001240_details.json
$ ome2024-ngff-challenge /Users/wmoore/Desktop/ZARR/data/6001240.zarr 6001240_from_details.zarr --output-read-details=6001240_details.json
Great. Moving forward with the next release then.
Fixes #19
NB: we need to specify shards & chunks for the label conversion (making sure that shards/chunks gives whole numbers) since if we don't then it tries to use the input chunks for labels
[1,59,69,136]
and the whole array as shard[1,236,275,271]
and these are not compatible.This isn't needed for the image itself, since the chunk shapes for the image are the same as the whole array shape.
Tested on
pilot-zarr3-dev
withUploaded:
Available at https://deploy-preview-36--ome-ngff-validator.netlify.app/?source=https://uk1s3.embassy.ebi.ac.uk/idr/share/ome2024-ngff-challenge/0.0.5/6001240_labels.zarr