napari-maskel
napari plugin for maskel: mask skeletonization and graph-based feature extraction, with interactive visualization of branches and node features.
Installation
uv sync --extra dev # + test tools
napari
Before maskel has its first PyPI release, point uv at a local checkout instead: uv sync --extra dev && uv pip install -e ../maskel (adjust the path), or add a local, untracked uv.toml with a [tool.uv.sources] override for maskel.
Usage
Open a segmentation mask (2D or 3D) as a labels layer, then run Analyze Mask from the Maskel plugin menu. A plain binary mask is treated as a single object; a multi-object instance segmentation map (more than one distinct nonzero label) is skeletonized independently per object — including two objects that touch, which stay correctly separate rather than merging into one skeleton. Every branch, node, and summary point is tagged with the object_id it came from, and the branches layer (the primary visualization — the raw skeleton itself isn't displayed separately) can be colored by object_id or any other branch property (Branch color by dropdown).
Inside the widget, tune extraction settings and use Save Config to export a reusable JSON preset — the same preset the maskel CLI consumes for batch processing (maskel run --config). The widget scrolls, so it's never clipped by the dock panel's height; the less-frequently-used Cleanup and Advanced Features groups are collapsed by default (click their headers to expand).
The Spacing field lets you set the physical pixel/voxel size (comma-separated, one value per axis) so length/radius/area features come out in physical units instead of pixel units. It's pre-filled from the selected layer's own .scale when you pick an image (napari has no convenient numeric field of its own to edit .scale, only an imprecise drag-based Transform tool or the console — this field is the convenient alternative), and you can edit it directly. An invalid value (wrong number of axes for the image, or unparsable text) shows an inline warning and falls back to pixel units for that analysis rather than failing.
Tests
uv sync --extra dev && pytest
License
napari-maskel is released under the MIT License. See LICENSE for details.
Metadata
Release files for napari-maskel 1.0.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| napari_maskel-1.0.0.tar.gz | 19.3 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| napari_maskel-1.0.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 33.9 kB
Release files / napari_maskel-1.0.0.tar.gz
| Download URL | napari_maskel-1.0.0.tar.gz |
|---|---|
| Size | 19.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
9c9c8863590a5496c0fde143f89a673347790186a7c5bb8b3e0efe2efa8f6607
|
|
BLAKE2b-256 checksum How to use checksums |
1e7770d452126f5768cb60cb86ebe3bd87559daab02aebccab74e289eee01e50
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Aug 20, 2026.
Transparency logRelease files / napari_maskel-1.0.0-py3-none-any.whl
| Download URL | napari_maskel-1.0.0-py3-none-any.whl |
|---|---|
| Size | 14.6 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
192f8d0ae06610b6e1f74c6ce4902c69e482176e58b3ede303a2f3aedf68bfe2
|
|
BLAKE2b-256 checksum How to use checksums |
02aa66fba44315d2168604b83554d6a7f915d17c2aa33a69a0eb133454d2e421
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Aug 20, 2026.
Transparency log