🧬 Tau Fibrils Yolo - Object detection in EM images
We provide a YoloV8 model for the detection of oriented bounding boxes (OBBs) of Tau fibrils in EM images. The model is integrated as a Napari plugin.
[Installation] [Model] [Usage] [Training]
This project is part of a collaboration between the EPFL Center for Imaging and the Laboratory of Biological Electron Microscopy.
Installation
We recommend performing the installation in a clean Python environment. Install the package from PyPi:
pip install tau-fibrils-yolo
or from the repository:
pip install git+https://gitlab.com/center-for-imaging/tau-fibrils-object-detection.git
or clone the repository and install with:
git clone https://github.com/EPFL-Center-for-Imaging/tau-fibrils-yolo.git
cd tau-fibrils-yolo
pip install -e .
Usage
In Napari
To use the model in Napari, start the viewer with
napari -w tau-fibrils-yolo
or open the plugin from Plugins > Tau fibrils detection.
From the command-line
Run inference on an image from the command-line:
tau_fibrils_predict_image -i /path/to/folder/image_001.tif
This command will run the YOLO model and save a CSV file containing measurements next to the image:
folder/
├── image_001.tif
├── image_001_results.csv
Training
The instructions for training the model can be found here.
Issues
If you encounter any problems, please file an issue along with a detailed description.
License
This project is licensed under the AGPL-3 license.
This project depends on the ultralytics package which is licensed under AGPL-3.
Acknowledgements
We would particularly like to thank Valentin Vuillon for annotating the images on which this model was trained, and for developing the preliminary code that laid the foundation for this image analysis project. The repository containing his original version of the project can be found here.
Metadata
Release files for tau-fibrils-yolo 0.2.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 | Provenance | Actions |
|---|---|---|---|---|
| tau_fibrils_yolo-0.2.0.tar.gz | 48.6 MB | Without provenance | Details for tau_fibrils_yolo-0.2.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| tau_fibrils_yolo-0.2.0-py3-none-any.whl | Python 3 | none | any | Details for tau_fibrils_yolo-0.2.0-py3-none-any.whl |
Total release size: 95.0 MB
Release files / tau_fibrils_yolo-0.2.0.tar.gz
| Download URL | tau_fibrils_yolo-0.2.0.tar.gz |
|---|---|
| Size | 48.6 MB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
a4ad931974198075d0da2d7a64e80237b3d10b341aa8783884f55d97356ce66c
|
|
BLAKE2b-256 checksum How to use checksums |
d19184be20eaa9ab84093b3a1d1c59236bd05861a7e27cd628b99cf40ddf5b0c
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.10.21
|
Release files / tau_fibrils_yolo-0.2.0-py3-none-any.whl
| Download URL | tau_fibrils_yolo-0.2.0-py3-none-any.whl |
|---|---|
| Size | 46.4 MB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
51c7a49f53e084164c4549e37c30ef6816a87b389f6c6a503be7874ed9f94d08
|
|
BLAKE2b-256 checksum How to use checksums |
135b5d387eabcf9eb0873e19f5c2a8bb2a649a07f998de634d59ad6831a2930a
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.10.21
|
Security for tau-fibrils-yolo 0.2.0
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.