🌊 napari-floodfill
Interactive object annotation in Napari using a flood fill tool. This tool is based on the flood function of Scikit-image.
Installation
You can install napari-floodfill via pip:
pip install napari-floodfill
Usage
- Select the plugin from the
Pluginsmenu of Napari. - Open an image to annotate (2D, RGB, 2D+t, or 3D).
- Click on the button "Start flood fill" or press
S. A newLabelslayer Flood fill (current edit) should appear. - With the Flood fill layer selected, move your cursor arounda nd click on the image to annotate objects.
- Double-click to confirm the annotation of an object and move to the next.
Options and parameters
- Auto-increment label index: Tick this option to increment the label index every time a new object is annotated (e.g. if you are annotating multiple objects).
- Intensity range: Pixels outside of this range will not trigger the flood fill computation. The extremities of the range represent the absolute minimum and maximum of the image. Set the range somewhere to the left if you are annotating dark objects on a bright background, or to the right if you are annotating bright objects.
- Flood fill tolerance: Controls the extent of the flood fill. A higher value will fill more pixels. The value selected is relative to the image intensity range.
Contributing
Contributions are very welcome. Please get in touch if you'd like to be involved in improving or extending the package.
License
Distributed under the terms of the BSD-3 license, "napari-floodfill" is free and open source software
Issues
If you encounter any problems, please file an issue along with a detailed description.
This napari plugin was generated with Cookiecutter using @napari's cookiecutter-napari-plugin template.
Metadata
Release files for napari-floodfill 0.0.1
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| napari-floodfill-0.0.1.tar.gz | 8.2 kB | Without provenance | Details for napari-floodfill-0.0.1.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| napari_floodfill-0.0.1-py3-none-any.whl | Python 3 | none | any | Details for napari_floodfill-0.0.1-py3-none-any.whl |
Total release size: 15.6 kB
Release files / napari-floodfill-0.0.1.tar.gz
| Download URL | napari-floodfill-0.0.1.tar.gz |
|---|---|
| Size | 8.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
157cd9cb77ad518bc57aff447e4a01f52ea4dfb9a00beee792f8c4b9a676288a
|
|
BLAKE2b-256 checksum How to use checksums |
be4bd321be39317148154759982f9c05f7a89568791f2195b8a134b0da5a0fd0
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.2 CPython/3.9.18
|
Release files / napari_floodfill-0.0.1-py3-none-any.whl
| Download URL | napari_floodfill-0.0.1-py3-none-any.whl |
|---|---|
| Size | 7.3 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
1f7d38a63bf117eeb13e9bc16e4ac4a2cd8f6088e94b95b7871f88e54f44989e
|
|
BLAKE2b-256 checksum How to use checksums |
3e7cb5f1abfd7d511fee6daa0023a8a4a3bbff2fdb883ac218173dc91d0ccfdf
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.2 CPython/3.9.18
|
Security for napari-floodfill 0.0.1
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.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.