-
Notifications
You must be signed in to change notification settings - Fork 5
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
display transformed Segmentations #106
Comments
Hi Martin, |
The following procedure generates a view that cannot be reproduced in mobie:
This view "twoseg_fromMoBIE" shows both segmentations at the same position, because the transform has no When I manually add the The project can be found in |
|
Hi,
probably also a spec issue, but I run into this inconsistency when using MoBIE-Python.
sourceNamesAfterTransform
new source namesourceNamesAfterTransform
yet another source nameThe 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"
segmentationDisplay
s do no longer point to the original table, so the view is not displayed and also validation fails (as expected) with :I thought of just pointing it to the original table but then I am back to:
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
segmentationDisplay
s 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 inget_view
).Any ideas and thoughts?
The text was updated successfully, but these errors were encountered: