-
Notifications
You must be signed in to change notification settings - Fork 26
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
Add support for validation of zarr filesets #1281
Comments
|
heh, not sure why I thought that "Closed" meant "Merged" to me ;) Left a question on that PR on what is the destiny/plan there in terms of validation.
that would really make it unlikely to be usable by default... where do they do it? from glancing over https://github.com/ome/ome-zarr-py/pull/142/files#diff-b50d9715cc6e4017cfc055fd0ed73ecb5d9158e17f4d58ca5b3ba08b89c46657R206 I thought it would just validate structure/metadata against some jsonschema. |
@yarikoptic |
I have followed ome/ome-zarr-py#142 (comment) and coded within `/mnt/backup/dandi/dandizarrs/tools/jsonschema-check-zattrs` on drogon:#!/bin/bash
# inspired by https://github.com/ome/ome-zarr-py/pull/142#issuecomment-1517024760
set -eu
#set -x
for z in "$@"; do
zattrs="$z/.zattrs"
if ! /bin/ls "$zattrs" &>/dev/null; then
echo "$z - no .zattrs, skipping"
continue
fi
url=$(git -C "$z" annex whereis .zattrs | grep https://dandiarchive | awk '{print $2;}' | head -n 1)
echo "$z - $url"
check-jsonschema --schemafile /home/dandi/proj/ngff/0.4/schemas/image.schema <(curl --silent "$url") | sed -e 's,^, ,'g
done and got following list of failures http://www.oneukrainian.com/tmp/dandizarrs-jsonschema-checks.out - so the majority of zarrs have
in fact - there is only 137 zarrs which pass validation and over 4k which do not. @slaytonmarx could you please check with similar ( |
I'll check tomorrow morning and let you know! |
I received the same validation errors as Yarik:
|
ATM I believe we are just testing if we can open them and two custom checks (not an empty group and not too deep of hierarchy). Initial validate support, with --strict option. in ome-zarr-py was recently merged so we should make use of it for our ome .zarrs.
The text was updated successfully, but these errors were encountered: