Skip to content

ngio for fractal-tasks-core: Overview #850

@jluethi

Description

@jluethi

This issue is meant as an overview for the effort to transition fractal-tasks-core to use ngio.

The overall strategy is:

  1. Add an ngio dependency to fractal-tasks-core
  2. Start using ngio in different tasks until all tasks depend on ngio for OME-Zarr reading & writing, label reading & writing & table reading & writing
  3. Deprecate the respective library functions in fractal-tasks-core
  4. Release a fractal-tasks-core 2.0.0 version where we remove those library functions

Nomenclature below: Top-level TODOs are the tasks. Fix sub-items are must fix issues in the task: We want to see that the ngio refactor fixes this issue. Review sub-items are minor issues we may be able to tackle during the refactor.

Tasks to transition to using ngio:

Converters

Tasks that write new OME-Zarr images

Tasks that write tables

Other tasks:

  • Import OME-Zarr
    • In _process_single_image: Replace use of NgffImageMeta usage with ngio
    • In _process_single_image: Replace ROI copying & table writing functionality with ngio

Not a goal for the moment: Handle the well & plate metadata with ngio

Currently blocked because we're waiting for feature X in ngio

Waiting for masking ROI writing

Task with other goals

Additional issues:

Deprecate

Issues Joel needs to review further

Not sure yet what exactly is needed now to close these issues


Issues related to ngio that should get tackled later (e.g. after 2.0.0 release):

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    Status

    TODO

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions