You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/source/guides/training_wnet.rst
+5-5Lines changed: 5 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -20,21 +20,21 @@ You may find below some guidelines, based on our own data and testing.
20
20
21
21
The WNet3D is designed to segment objects based on their brightness, and is particularly well-suited for images with a clear contrast between objects and background.
22
22
23
-
The WNet3D is not suitable for images with artifacts, therefore care should be taken that the images are clean and that the objects are at least somewhat distinguishable from the background.
23
+
The WNet3D is not suitable for images with strong noise or artifacts, therefore care should be taken that the images are clean and that the objects are at least somewhat distinguishable from the background.
24
24
25
25
26
26
.. important::
27
27
For optimal performance, the following should be avoided for training:
28
28
29
29
- Images with very large, bright regions
30
-
- Almost-empty and empty images
30
+
- Almost-empty and empty images, especially if noise is present
31
31
- Images with large empty regions or "holes"
32
32
33
-
However, the model may be accomodate:
33
+
However, the model may accomodate:
34
34
35
35
- Uneven brightness distribution
36
36
- Varied object shapes and radius
37
-
- Noisy images
37
+
- Noisy images (as long as resolution is sufficient and boundaries are clear)
38
38
- Uneven illumination across the image
39
39
40
40
For optimal results, during inference, images should be similar to those the model was trained on; however this is not a strict requirement.
@@ -88,7 +88,7 @@ Common issues troubleshooting
88
88
If you do not find a satisfactory answer here, please do not hesitate to `open an issue`_ on GitHub.
89
89
90
90
91
-
- **The NCuts loss "explodes" after a few epochs** : Lower the learning rate, for example start with a factor of two, then ten.
91
+
- **The NCuts loss "explodes" upward after a few epochs** : Lower the learning rate, for example start with a factor of two, then ten.
92
92
93
93
- **Reconstruction (decoder) performance is poor** : First, try increasing the weight of the reconstruction loss. If this is ineffective, switch to BCE loss and set the scaling factor of the reconstruction loss to 0.5, OR adjust the weight of the MSE loss.
0 commit comments