Closed constantinpape closed 2 years ago
Ups! I was confused with the data for the 3D UNet. I should be able to update it by clicking on the edit button, but I don't see the model on the webpage
Ups! I was confused with the data for the 3D UNet. I should be able to update it by clicking on the edit button, but I don't see the model on the webpage
Yes, @oeway is aware of that issue and currently fixing it.
@esgomezm could you try the preview version here: https://github.com/bioimage-io/bioimage.io/pull/228
So, the page works and I can click on edit, but then, i cannot update the model card, at the end of the process. It just allows me to upload a new deposit
So, the page works and I can click on edit, but then, i cannot update the model card, at the end of the process. It just allows me to upload a new deposit
OK, I will check that.
@esgomezm @constantinpape I just did a preliminary fix for the edit button, but I cannot test it since it requires existing items. could you try with 0.4.5 (refresh here: https://bioimage.io/#/about until you see 0.4.5)?
Yes, it's working now :).
@esgomezm and @constantinpape Do we have a plan on updating this model, I still see "mitochondria" in the model description.
As we discussed during the meeting @esgomezm wanted to check if update via the upload still works.
Hey! I'm trying model edition and it goes well until the update button but then it complains about a field called rdf_source
.
@esgomezm Thanks for the report, it should been fixed now in 0.4.7 (https://bioimage.io/#/about), please refresh the page and try it again.
Done! now should I see any PR?
Done! now should I see any PR?
Yes, I think it's this one: https://github.com/bioimage-io/collection-bioimage-io/pull/265
I have merged #265 and this is fixed now.
The model name for https://github.com/bioimage-io/collection-bioimage-io/blob/main/collection/10.5281/zenodo.5817052/resource.yaml is wrong: this is not a mitochondria segmentation model, but a neuron segmentation model. See
This looks pretty bad because it is the first model on the website and clearly wrong.... We could try fixing this on the fly by changing the name in the yaml in this repo or we need to update the version via the website / zenodo.
cc @esgomezm