Skip to content

display transformed Segmentations  #106

@martinschorb

Description

@martinschorb

Hi,
probably also a spec issue, but I run into this inconsistency when using MoBIE-Python.

  • I have a segmentation source
  • I transform it -> sourceNamesAfterTransform new source name
  • I transform it another time differently -> sourceNamesAfterTransform yet another source name
  • I like to show these segmentations together

The table data of the two displayed segmentations should stay the same as for the original segmentation source. Now, I run into the problem, that the "new" segmentationDisplays do no longer point to the original table, so the view is not displayed and also validation fails (as expected) with :

ValueError: The table source MSB30_4_derivedsourceblabla is not present in the source metadata.

I thought of just pointing it to the original table but then I am back to:

  File "..../mobie-utils-python/mobie/metadata/view_metadata.py", line 347, in get_view
    assert display_setting["segmentationDisplay"]["name"] == name,\
AssertionError: MSB30_4_spotIDs, MSB30_4_spotIDs_tp_44-to-48

that the names no longer match.

Now, the only solution/workaround I see at the moment is duplicating the tables and creating a new directory for each segmentationDisplay. This can easily become a pain with dozens if not hundreds of duplicate directories.

Also, if something changes in the original table, ideally all derived tables or segmentationDisplays should update accordingly.

So I think we need a thorough re-think of how to deal with these "transient" or "virtual" sources created within a view with sourceNamesAfterTransform.

Or we need to allow linking to another default table for a segmentationDisplay ( and modify these checks in get_view).

Any ideas and thoughts?

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions