napari-epyseg
Plugin to run EpySeg directly in Napari. Can handle temporal data (movie) or single time point (image).
Installation
To install it from Napari, go into the Plugins menu, select Install/Uninstall Plugins.. and look for napari-epyseg in the plugins list.
To install it directly outside of napari, create/reuse and activate a python environement, e.g epyseg_env and install it with pip:
pip install napari-epyseg
[!IMPORTANT]
epysegis compatible until python 3.10 (included), but not for versions of python above. Thus,napari-epysegis also compatible with python versions until 3.10
Usage
In Napari, go to Plugins>napari-epyseg to start it.
It will open an interface in the left part of the main window.
You must select the layer (image or movie, single color channel) on which to run EpySeg.
For this, in the Pick an Image parameter, select the corresponding layer (you should open the image/movie independantly of the plugin).
To run EpySeg with default parameters, press directly Segment once you have selected the image.
When processing is finished, a new layer called Segmentation will be added in the right panel of the interface.
You can save the result with the Save segmentation button that appears on the left part of the interface.
Choose where to save the file and the file name with the Segmentation filename parameter, and click the button to save it.
Remark
This plugin was tested on python 3.10, with epyseg version 0.1.52, napari version 0.4.19, tensorflow 2.14
Troubleshooting
- On Linux Ubuntu, python 3.10, epyseg don't run with tensorflow 2.15 and output the error:
DNN not found. Downgrading tensorflow to 2.14 worked. tifffile versionscompability: some versions of tifffile where not compatible with epyseg, but recent versions are now fine.tifffile <= 2021.11.2are fine andtifffile==2025.1.10also.
License
This plugin is distributed under the BDS-3 license.
If you use this plugin, please cite Epyseg and the plugin with its doi:
Metadata
Release files for napari-epyseg 0.0.14
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_epyseg-0.0.14.tar.gz | 302.8 kB | Without provenance | Details for napari_epyseg-0.0.14.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| napari_epyseg-0.0.14-py3-none-any.whl | Python 3 | none | any | Details for napari_epyseg-0.0.14-py3-none-any.whl |
Total release size: 312.9 kB
Release files / napari_epyseg-0.0.14.tar.gz
| Download URL | napari_epyseg-0.0.14.tar.gz |
|---|---|
| Size | 302.8 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
2bab13c1a036f74ffbb6d399c233a60ef072b26a8ae7cb4a6c2e196cfe4bcbbd
|
|
BLAKE2b-256 checksum How to use checksums |
29a82c92fd030149a92a5074a18c8c94aa199c2282fcf8839c354e321225f02f
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.0.0 CPython/3.10.12
|
Release files / napari_epyseg-0.0.14-py3-none-any.whl
| Download URL | napari_epyseg-0.0.14-py3-none-any.whl |
|---|---|
| Size | 10.1 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
1717c7e1d1ff239733fdfa5bfbcaf7a72bdb3a5ec1a0e7b4c2175860a756d43d
|
|
BLAKE2b-256 checksum How to use checksums |
25a8f60b64247b192277eedc00e078e1415ed43adb0fb7cd36bed7ba458ca168
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.0.0 CPython/3.10.12
|
Security for napari-epyseg 0.0.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.
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.