-
Notifications
You must be signed in to change notification settings - Fork 11
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
Usage with custom 2D/3D model #25
Comments
Possibly solved by this image.sc thread |
Hi, the plugin expects a folder that contains a (StarDist-specific) |
Sorry, I was remembering this wrong. You actually need to first convert from the bioimage.io format to the "normal" stardist folder format. Then use that folder for the napari plugin. You can see how to do this here. |
Hey @uschmidt83, should I do something? If I need to fix anything I'll be available over the weekend. If everything is okay then maybe I should put a guide somewhere in the description to show users how to convert. I'll talk to Fynn is there are more generic issues. |
Hi @qin-yu, there's nothing for you to do. The bioimage.io model must be "imported" to create a regular StarDist model folder, as shown in this notebook. It can then be used with the napari plugin. I've also updated the plugin README to document this. |
Describe the bug
I just tried to use the stardist-napari plugin using a custom model from the bioimage model zoo (i.e., this one). I would expect that I'd just have to select Custom 2D/3D in the stardist-napari plugin and navigate to the model weights (they're downloaded as
.h5
) and select them. However, the dialogue only allows to select folders and remains red when I chose the folder containing the weights file.To reproduce
Simply install stardist-napari and download the weights from the link above.
Expected behavior
Weights should be detectable on my filesystem through the openfiledialogue in the plugin. I suspect that there is an
openfolderdialogue
instead of anopenfiledialogue
.Data and screenshots
Environment:
The text was updated successfully, but these errors were encountered: