Skip to content
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 HCS export with the --bf flag #85

Open
sbesson opened this issue Sep 23, 2021 · 0 comments
Open

Add support for HCS export with the --bf flag #85

sbesson opened this issue Sep 23, 2021 · 0 comments
Labels
enhancement New feature or request

Comments

@sbesson
Copy link
Member

sbesson commented Sep 23, 2021

See IDR/idr-zarr-tools#1 for the original discussion.

While driving the export of IDR datasets, some wrapper scripts have been written on top of bioformat2raw 0.2.x to handle the bioformats2raw Zarr group layout and only retain the OME-Zarr image and add the OMERO metadata.

In the case of non-HCS data, #75 should have migrated all this logic at the level of this plugin using the command:

omero zarr export --bf Image:xxx

Support for HCS data export as OME-Zarr is the last part to be added. The --bf flag now requires bioformat2raw 0.3.0 which brings native support for HCS support and existing code can be re-used to add omero metadata to each well sample.

Probably the main point of review will be to ensure that the layouts are compatible . ome zarr export Plate:xxx uses the plate/well/row/field of view layout as described in https://ngff.openmicroscopy.org/0.1/ while bioformat2raw retains a flat layout where each field of view is 0-based index for compatibility with METADATA.ome.xml and raw2ometiff. My expectation is that both layouts should be equivalent as long as the correct metadata is filled but this will be a good occasion to compare and test via different downstream clients.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants
@sbesson and others