-
Notifications
You must be signed in to change notification settings - Fork 10
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
Feature request: support for MultiScaleData #212
Comments
In case this is caused by my in-flux dev environment: napari info:
|
Hi @will-moore, Thanks a lot for the feedback and for using the plugin!
Best, |
Thanks for looking at this...
|
Yes, the labels layer is added with code that also adds "features" dataframe, so I've added a "label" column to that (and I also tried it with your code example), but in both cases I get a new error...
|
Ah I see, your labels layer is a multiscale layer in napari. The support of such data is not implemented yet in the clusters-plotter. The plugin expects the image to be a numpy multidimensional array, which is the default data type when you open e.g. tif format image with
And simply adding the conversion of MultiScaleData to a numpy array is not a solution because it ruins the data structure of the image. I will create an issue to implement the support for such data. In the mean time, would it maybe be possible to open your data not as multiscale in napari? |
Hi - thanks for the plugin - looks great!
I've just started looking at this for displaying the features on labels (passed into
napari
as a dataframe using thefeatures
attribute of a new labels layer).The plotting works fine, but I'm missing the extra layer that shows the colors of selected/unselected labels:
This screenshot is with only the original labels layer visible, having made a selection in the plot with the lasso:
From the user guide, I was expecting to see an addition layer with blue/orange labels.
I see this in the Terminal where I launched
napari
:FYI: the data was loaded as described at ome/napari-ome-zarr#85
The text was updated successfully, but these errors were encountered: