Skip to content

VIPP 0.16.0a7

VIPP 0.16.0a7 fixes initial source loading and recovered automatic results, and adds a choice of relative or absolute paths when saving workflows. Scientific algorithms, image interpretation, compute policy and schema numbers are unchanged. Unfinished AI assistant, agent, MCP and webhook features are not included.

Use the canonical GitHub release for the exact wheel, source archive, unsigned Windows installer, separate CPU-only unsigned/unnotarized macOS packages and matching checksums, or the exact PyPI version. Follow the installation instructions.

See the initial and recovered results

  • The starter sample loads when VIPP opens, including when an interrupted workspace is available for recovery. Keep for later no longer leaves the starter sample blank.
  • Opening an ordinary saved workflow loads its bound sources. If its saved selection is a manual step without a result, the initial image view shows an available source without calculating that manual step. Calculate all also works on a workflow with no calculated results, without a parameter edit first.
  • Recover selected loads available samples or verified files and rebuilds automatic processing results, such as Gaussian Blur and Otsu Threshold. These are newly calculated results, not restored cached arrays. Missing or changed inputs are reported rather than silently replaced.

Recovered manual steps remain paused even when their saved Auto Recalculate setting is on. File-writing nodes and steps depending on paused nodes also wait. A manual step's Calculate action runs that step without enabling unrelated writers. Calculate all releases the recovery restriction: check output paths first, because enabled auto-save nodes can then write. Recovery still creates new unsaved copies and does not restore Batch configuration, Undo history, source data or calculated caches. See workflow recovery.

Choose how workflow paths are saved

Under Settings → Workflow paths, choose:

  • Relative to workflow file (default) when moving the workflow and data together, preserving their folder structure.
  • Absolute file locations when the data stays in place and only the workflow JSON may move.

The choice applies to later workflow saves, including an attached batch configuration. To move only a relative-path workflow, open it while its sources still resolve, choose absolute locations, then save before moving it. Changing the choice cannot repair an unknown original location after a workflow has already moved. Neither choice copies data or changes the separate Export Python… and Batch Save config actions. See path choices.

Limits and compatibility

Workflow, batch-config and manifest schemas remain 6. The operation catalogue, scientific kernels, GPU admission, installer engines and dependency pins are unchanged. Preserve original workflows/data, regenerate Python exports with the installed version, and recheck representative outputs.

The qualification declaration separates changed-domain checks from carried-forward evidence. Automatic recalculation is not recovery of cached results or proof of scientific validity; focused source checks do not establish a full fresh-user installer lifecycle, every reader or complete cross-platform GUI coverage.

Full source comparison: 0.16.0a6 → 0.16.0a7