RFE: relax filename_patterns to read child elements
sbesson opened this issue · 4 comments
The filename_patterns introduced as part of the conversion of this plugin to the npe2 engine allowing to open any OME-NGFF dataset ending with *.zarr
This currently covers all the supported specification e.g. multiscale images
napari https://uk1s3.embassy.ebi.ac.uk/idr/zarr/v0.4/idr0083A/9822152.zarr
or plates
napari https://uk1s3.embassy.ebi.ac.uk/idr/zarr/v0.4/idr0072B/9512.zarr
As it stands, this naming pattern prevents direct access to the leaves of a dataset like the well of a plate
napari https://uk1s3.embassy.ebi.ac.uk/idr/zarr/v0.4/idr0072B/9512.zarr/L/20
the field of view of a plate
napari https://uk1s3.embassy.ebi.ac.uk/idr/zarr/v0.4/idr0072B/9512.zarr/L/20/0
or a label image associated with a multiscales image
https://uk1s3.embassy.ebi.ac.uk/idr/zarr/v0.4/idr0062A/6001247.zarr/labels/0
Using a more permissive pattern e.g. *.zarr* or possibly * as suggested in #42 would relax this constraint and allow direct acces. This is potentially outside the intent of the plugin.
Originally posted by @sbesson in #42 (comment)
Sounds like this might need actioning soon, no? Do we know if those patterns work?
I only tested * and it worked locally at least. You're correct that with ome/ngff#112, being able to access e.g. an image in such a layout will require this rule to be relaxed.