You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
general question, but what's the scope of support of omero metadata for this napari plugin? I'm thinking for instance of:
channel ID, saved in omero metadata labels that could set the napari layer name
channel color, saved in omero metadata color that sets the napari layer color
there might be more info on rendering that could be used by napari layers (I'd be curious to know which ones).
I think it'd be useful to have a functionality that parse omero metadata and set layer properties in napari accordingly.
The text was updated successfully, but these errors were encountered:
As far as I can tell most info could be used by Napari, if not by layers then by the LayerList.
active (in napari could mean 2 things): viewer.layers[].visible or viewer.layers.selection.active. (latter is whether it is the actively selected layer).
family: either viewer.layers[].interpolation2d or viewer.layers[].interpolation3d.
window: start and end I believe correspond to the contrast limits in napari.
In rdefs the projection can be set in napari as well.
Also you could say that if in rdefs model is set to color and there is a value for EmissionWave in Napari colormaps could be used. For example if the Emissionwave is cy3 this would correspond to orange, if DAPI then blue and so on.
If this were to be implemented then perhaps the easiest would be to use Enums.
general question, but what's the scope of support of omero metadata for this napari plugin? I'm thinking for instance of:
labels
that could set the napari layer namecolor
that sets the napari layer colorthere might be more info on rendering that could be used by napari layers (I'd be curious to know which ones).
I think it'd be useful to have a functionality that parse omero metadata and set layer properties in napari accordingly.
The text was updated successfully, but these errors were encountered: