-
Notifications
You must be signed in to change notification settings - Fork 14
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
macro for slices #4
Comments
Hi Mathieu, thanks for using StarDist! Our Python package can do 3D nuclei segmentation and we would love to bring that also to our Fiji plugin. However, there are unfortunately several technical challenges why this hasn't happened yet. What you are trying to do (segment in 2D and merge) could work for some easier datasets, but is likely not going to work well in general. Hence, we're not pursuing this approach. Hope that helps. Best, |
Hey @uschmidt83, there are some people on the image.sc forum asking for how to run StartDist from ImageJ Macro or having issues in running it from Macro: https://forum.image.sc/t/automation-of-stardist-in-imagej-macros/35611 https://forum.image.sc/t/beginner-in-clij-implementation-for-an-existing-macro/35541 Unfortunately, the Macro recorder just records I would also be happy to help implementing it. Just let me know. ;-) Cheers, |
Hi Robert,
I don't know if/how this is possible (note that StarDist is an ImageJ2 plugin). Best, |
Hi Uwe, cool. ImageJ2 plugins are usually recordable. In this case it's tricky. But I've done it before, so no big deal. I'll send a PR with the recordable plugin soon. Cheers, |
Hi Uwe, |
Hi @matfallet, sorry for the late reply. I don't think you can easily call our python code from within Fiji, let alone a macro. Sorry. |
Hi Uwe,
ok thanks, do you implement just right now image J macro on 2D ?
We have tested the 3D python on our images (KI67proliferative nucleu but also dapi). It doesn't seem to work.
We have questions about it :
- do you implement it on synthetic data only ?
- If our voxel size is quite large (0.8um) for 40x/1.4 objective, is-it a problem with your model?
- Does your model is robust to different parameters, in 2D it works perfect, so why not in 3D ?
Thanks for you reply, maybe i can put the questions on Github ?
Cheers, Mathieu
|
No, the example just uses synthetic data.
I don't understand. Do you mean why the 3D model cannot be applied to other images like yours? |
OK I understand, there is no model cuurently in 3D to detect nuclei like for 2D : versatile (fluo nuclei). I suppose that the 3D model could be trained on 3D image with high voxel size (good sampling) and then we can change the number of slices to train on lower sampling...how many cells do you use to build the 2D model ? Just an idea how long could it takes in 3D.. Thanks Mathieu |
We trained the 2D model on hundreds of images (thousands of cells) of the DSB 2018 nuclei segmentation challenge dataset. That's why it works so well in general. In general, it is very difficult to say how many annotated images/cells are needed to reach results that are good enough for the intended application. It really depends on the appearance variability of the to be segmented cells. The more variability, the more annotated data is required. |
Hi,
Is there a way to put stardist in a macro to apply the segmentation for each slice and recombine them to reconstruct 3D nuclei ?
It would be great, I try but don't find the command to skip the interface :
Thanks so much, the segmentation is amazing in 2D for nuclei, I cannot imagine it was possible to do so good job !
Cheers, Mathieu
The text was updated successfully, but these errors were encountered: