phenopype-plugins
AI-plugins for phenopype - still under early development.
Currently, plugins for three libraries are available:
ultralytics
- predict_yolo_det (object detection): https://docs.ultralytics.com/tasks/detect/ (fine tuned models only)
- predict_yolo_seg (segmentation): https://docs.ultralytics.com/tasks/segment/ (fine tuned models, and the SAM-family [SAM, SAM2, mobileSAM, FastSAM])
pytorch
- predict_torch_seg (Torchvision segmentation models: https://pytorch.org/vision/main/models.html)
keras
- predict_keras (Keras segmentation models https://keras.io/examples/vision/oxford_pets_image_segmentation/)
Installation
Prior to using the functions with phenopype you need to install the respective dependencies:
1. Install phenopype (see https://www.phenopype.org/docs/installation/phenopype/ for more details):
pip install phenopype
2. Install the plugins module:
pip install phenopype-plugins
3. Install the dependencies
Dependencies
If you have a GPU and the appropriate drivers install, make sure you install a fitting CUDA version first - e.g., v12.1:
mamba install -c nvidia cuda-toolkit==12.1
torch
1. With GPU support:
pip install torch torchvision --index-url https://download.pytorch.org/whl/cu121
2. Without GPU support:
pip install torch torchvision
keras
1. With GPU support:
pip install keras-gpu
-
Without GPU support:
pip install keras-gpu
ultralytics
1. Install Ultralytics BEFORE phenopype due to conflicting opencv-python (ultralytics) and opencv-contrib-python (phenopype) versions (see step 2 for alternatives):
pip install torch torchvision ## needed
pip install ultralytics
2. If you have already installed phenopype and can't or don't want to uninstall it, you can do the following:
pip install ultralytics
## force reinstall opencv-contrib-python
pip install opencv-contrib-python --force-reinstall
Metadata
Release files for phenopype-plugins 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 |
|---|---|---|---|---|
| phenopype_plugins-0.2.0.tar.gz | 22.8 kB | Without provenance | Details for phenopype_plugins-0.2.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| phenopype_plugins-0.2.0-py3-none-any.whl | Python 3 | none | any | Details for phenopype_plugins-0.2.0-py3-none-any.whl |
Total release size: 45.5 kB
Release files / phenopype_plugins-0.2.0.tar.gz
| Download URL | phenopype_plugins-0.2.0.tar.gz |
|---|---|
| Size | 22.8 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
d2a2f1d154761e9da3ccbbbf3ba287566e6fc7f5fb83d3f4b4fe8bbab122b99a
|
|
BLAKE2b-256 checksum How to use checksums |
975a0fff7f10952bf1624bc7e555a137336f46a0f06dd0fda3471b95d14b43ab
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.0.1 CPython/3.11.9
|
Release files / phenopype_plugins-0.2.0-py3-none-any.whl
| Download URL | phenopype_plugins-0.2.0-py3-none-any.whl |
|---|---|
| Size | 22.7 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
d2e6efd0be6318d5087305ae0c716b88c64c0024506b6108b2486a2c7fe1c8fb
|
|
BLAKE2b-256 checksum How to use checksums |
3d3fa811dfd1e3b00fd9828dd1d2e761388fdf4cec10940a7a24b5a94ed5dc2d
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.0.1 CPython/3.11.9
|
Security for phenopype-plugins 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.