HenriquesLab / ZeroCostDL4Mic

ZeroCostDL4Mic: A Google Colab based no-cost toolbox to explore Deep-Learning in Microscopy
MIT License
565 stars 129 forks source link

UNET3D prediction problem #296

Closed jinxsfe closed 10 months ago

jinxsfe commented 1 year ago

Describe the bug I use UNET 3D model to segment the 3Dobject, but the 3D visualization of the object is slice by slice, which is not continuous, When I get result for segmentation and open by icy, it has multichannel instead of multi-stack, I open python and save it for io.save.the result visualize at below, how to make them look more continuous, instead of slice by slice To Reproduce Steps to reproduce the behavior: image

Expected behavior

image
jinxsfe commented 1 year ago
Screenshot 2023-10-08 at 10 40 55 AM
esgomezm commented 1 year ago

Hi @jinxsfe I'm not sure what is exactly the issue with the notebook. Could you please, explain it with more details and maybe with screenshots of the notebook's output?

Thank you! Esti

jinxsfe commented 1 year ago

Oh, sorry about my explanation, my question is when I segment the cell based on your algorithms, and I open it image on icy

Screenshot 2023-10-09 at 1 46 15 PM

the result looks like, this, it's multiple channels, instead of multiple stacks, and when I open it by python function and save it again by io. save, the visualization of the image(one of the nucleus) is shown above(red), the surface is not continuous, seems the stack plied with each other.

jinxsfe commented 1 year ago

can you check the code that makes them directly segment and the result is a 3D stack? instead of multiple channels? or can you tell me why this happened?

mdoaskndfweon commented 1 year ago

@esgomezm

mdoaskndfweon commented 1 year ago

I also face the same problems,

mariana-gferreira commented 1 year ago

Hello @jinxsfe, the new version of the U-Net 3D notebook has fixed the issue of saving stacks as channels. Please run the updated version and let us know if you still encounter issues.

Thank you Mariana

esgomezm commented 10 months ago

I'm closing the issue. If the problem still remains, please open it again