PumaGuard
Introduction
Please visit http://pumaguard.rtfd.io/ for more information.
Get PumaGuard
GitHub Codespaces
If you do not want to install any new software on your computer you can use GitHub Codespaces, which provide a development environment in your browser.
Local Development Environment
A local development environment can be created by using the poetry tool,
which can be installed with
sudo apt install python3-poetry
Run
poetry install
To install all of the necessary Python modules.
Running the scripts on colab.research.google.com
Google Colab offers runtimes with GPUs and TPUs, which make training a model much faster. In order to run the training script in Google Colab, do the following from the terminal:
git clone https://github.com/PEEC-Nature-Youth-Group/pumaguard.git
cd pumaguard
scripts/train.py --help
For example, if you want to train the model from row 1 in the notebook,
scripts/train.py --notebook 1
Running the server
The pumaguard-server watches a folder and classifies new files as they are
added to that folder. Run with
poetry run pumaguard-server FOLDER
Where FOLDER is the folder to watch.
Training new models
For reproducibility, training new models should be done via the train script and all necessary data, i.e. images, and the resulting weights and history should be committed to the repository.
-
Get a TPU instance on Colab or run the script on your local machine.
-
Open a terminal and run
git clone https://github.com/PEEC-Nature-Youth-Group/pumaguard.git cd pumaguard
-
Get help on how to use the script
On Colab, run
./scripts/pumaguard --help ./scripts/pumaguard train --help
On your local machine, run
sudo apt install nvidia-cudnn poetry install poetry run pumaguard --help poetry run pumaguard train --help
-
Train the model from scratch
./scripts/pumaguard train --no-load --settings pumaguard-models/model_settings_6_pre-trained_512_512.yaml
1 maintainer
Metadata
1 maintainer
Release files for pumaguard 20.post48
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| pumaguard-20.post48.tar.gz | 291.3 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| pumaguard-20.post48-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 590.8 kB
Release files / pumaguard-20.post48.tar.gz
| Download URL | pumaguard-20.post48.tar.gz |
|---|---|
| Size | 291.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
e94d9de4b7f02cfeae4a86a7e574d7850a40065d7cc566cd257efc37ed5ed178
|
|
BLAKE2b-256 checksum How to use checksums |
5a4c426d27bf4783763ca4c11d95dc3ba0b08bb78760817ae048abd4b30d88c0
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.7
|
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 Nov 13, 2025.
Transparency logRelease files / pumaguard-20.post48-py3-none-any.whl
| Download URL | pumaguard-20.post48-py3-none-any.whl |
|---|---|
| Size | 299.4 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
2b5520dacf193fef6540cee9c389e043b2215fe98d90394fde72e6e3b02f0933
|
|
BLAKE2b-256 checksum How to use checksums |
745bc142f52a83df7e626562e6fc1860e1e115bfe157960af98fbb1c2f34dfcb
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.7
|
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 Nov 13, 2025.
Transparency log
