Troubleshooting¶
Start with the earliest stage that differs from expectation. Changing the final measurement rarely fixes a wrong channel, axis interpretation, threshold mask, or label image.
| Symptom | Start here |
|---|---|
| Wrong objects, counts, channels, units, or stale tables | Common problems |
| Slow interaction or high RAM use | Performance and memory |
| Auto/Prefer GPU/Custom uses CPU, GPU setup fails, or optimizer progress pauses | Choose and verify CPU or GPU compute |
| Installation/plugin discovery problem | Install VIPP |
| Windows setup stops during checks or reports a registration conflict | Installation troubleshooting |
| Question, reproducible bug, or missing behavior | Get help or report a problem |
Before debugging your own file, open the matching bundled example. If the example works, compare source type, axes, scale, dtype, channel mapping, shape, and release version. If the example fails, capture the exact error and version without changing multiple settings at once.
A result appears, but its display reports a problem¶
New in 0.15.0a5: a short Result calculated warning means the calculation finished, but the napari view could not fully update. Reselect the node to retry its display. You do not need to recalculate the mesh just to clear the message.
Use Details… to view and copy the technical message, or Dismiss to hide the warning without changing results or node errors. If it returns, include those details and your VIPP version when reporting the problem.
Repeated layer-list loading errors¶
New in 0.16.0a4: layer-list repaint recovery
VIPP now guards napari's layer-list loading indicator and thumbnail when a
layer row disappears during a display update. This addresses repeated
'NoneType' object has no attribute 'height' errors from
LayerDelegate._paint_loading. It changes display handling only; workflow
parameters and calculated image or mask arrays are unchanged.
If an older version repeatedly shows this error, save the workflow, close VIPP, and reopen it in a build containing the fix. A different traceback, or an error that persists in that build, needs separate investigation. Include the complete traceback and VIPP and napari versions when reporting the problem.