-
Notifications
You must be signed in to change notification settings - Fork 15
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
OME-NGFF transfer fails #41
Comments
is this on the |
Look like import failed due to missing |
@erickmartins |
and if you unzip it, can you run an |
@erickmartins This fails as below
|
then it's an |
I am afraid I have a counter-example workflow, showing that the problem is either in the
[1] [2] - import of the folder produced by
[3] (import of the folder produced by
transfer-test.zarr.zip (file produced by OMERO.web) test-zarr.tar.gz (file produced by cli-transfer) Edit: I guess a lot would be revealed by comparing those two zips attached to this comment, which should actually be identical imho. One is produced by |
Umm, sorry for the naming of the attached zip files, confusingly, the Thinking about it after re-reading my report, I think we might have problems with naming (which demonstrates in the |
Just double-checking: is the non-pack zip produced by |
I think neither, the precise answer is "Done with OMERO.web, the code is:" #41 (comment) |
What does What it comes down to is: if (if you tried to link to code in the previous post, that has not worked) (well I was typing this while Petr was typing as well. questions answered below) |
@erickmartins Further to your question of
and export
|
ok, thanks. do they work without the |
Yes, they do work both of them
|
hmmm ok. I'll investigate. |
@erickmartins I think I got the cause of the issue. It is a variation of ome/ZarrReader#26 - although the error in ome/ZarrReader#26 and in here is different, the root of the problem is the same - the fact that the "real-to-be-imported" folder
In summary, the issue could be solved by either
|
cc @dgault |
It is, of course, possible to make an exception for zarrs when it comes to the folder naming conventions, but unless any user has a pressing need for Zarr transfers I think I'd rather wait and see if |
See the uploaded tar.gz
This is from the image https://merge-ci.openmicroscopy.org/web/webclient/?show=image-243767, user-3.
I had another failure on OME-NGFF export as well already.
Happy to investigate deeper, if unclear , cc @will-moore @joshmoore
zarr-small.tar.gz
The text was updated successfully, but these errors were encountered: