-
Notifications
You must be signed in to change notification settings - Fork 11
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
Detection of files not inside the zarr folder if nested into another .zarr folder #26
Comments
cc @sbesson @joshmoore cf. discussion this morning |
@pwalczysko: can you try this in a subdirectory that has no parents ending in |
I was about to say part of the concern is redundant with #25 around defining precisely how much should be detected/discovered by the reader. |
I think I am starting to understand - but see above, the options are limited to have a better situation, not sure why admin cannot move the folder. Edit: |
Indeed, the move of the
|
The removal of the |
This problem is resurfacing in ome/omero-cli-transfer#41 (comment) - I would claim that it shows that the issue here is actually caused by the naming of the enclosing folder, and it is less marginal (as shown by the fact that the |
Note: The problem described below is only occurring if the
petr-test
folder is nested into another .zarr folder, such as/uod/idr-scratch/test.zarr/petr-test/multifile-Z1.ome.zarr
. If this nesting is removed, the problem does not occurr, and the resulting import does consit of 1 image with 5 z planes as expected.Have an ome.zarr folder inside a subfolder called
petr-test
, e.g.In this case, the importer detects the zarr files to import as follows:
Now, have following 5 files inside the
petr-test
folder as well next to theome.zarr
folder (not inside the ome.zarr) such asThe importer is detecting the ome.tiff files as well, although pointed only and directly at the ome.zarr
The text was updated successfully, but these errors were encountered: