-
Notifications
You must be signed in to change notification settings - Fork 9
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
Update StarDist Plant Nuclei 3D ResNet #649
Conversation
unfortunately it still fails to install the env
|
Hi @FynnBe |
because the weights are specified as pytorch state dict and the corresponding source code depends on the stardist library... |
Ok! I reviewed the model. This model has nothing to do with pytorch at all and you don't need any stardist dependency to run it (unless you want to use it in stardist, i.e. no dependencies except tensorflow needed). The tensorflow version is already specified in the weights. @FynnBe could you please try running the CI without the dependencies or @qin-yu remove stardist and all sorts of unneeded dependencies from the environment? |
|
yes, please upload the new version and click on "update the model" when it suggests that. The system will automatically create a new version. Also, you asked about new DOIs before: yes, a new doi is created because DOIs are unique identifiers of a particular contribution (papers, models or anything with a DOI). If you change the model, even for updating it, a new DOI is assigned because the model is somehow different. |
Thanks @esgomezm Zenodo keeps environment.yaml for me after uploading files without this one. Is it expected? I manually clicked the bin icon next to it in Zenodo interface and clicked "save" then go back to bioimage.io and publish. I hope this time it passes the CI. |
It would be nice if one of you could comment on stardist/stardist#254. Thanks! |
This is an automatic PR created by the @bioimageiobot regarding changes to the resource item 10.5281/zenodo.8421755.
The following version(s) will be added:
Please review the changes and make sure the new item or version(s) pass the following check list:
Maintainers: @qin-yu
Note: If you updated or re-uploaded another version for the current item on Zenodo, this PR won't be changed automatically. To proceed, you can do the following:
status
field asaccepted
, but change thestatus
under the current version toblocked
.Then wait for the CI on the main branch to complete. It should detect the new version(s) and create another PR for the new version(s).
Previous PRs of this resource: #646, #648