Lowcarb
A carbon-aware client selection strategy for Flower powered by the Carbon-Aware-SDK.
Enabling privacy-aware and carbon-aware machine learning.
Installation ⚙️
To install lowcarb, simply run
pip install flwr-lowcarb
Tutorial 🌼
To try out our tutorial, clone the repository and run
python -m venv venv # create venv
. venv/bin/activate # activate venv on Linux/Mac
.\venv\Scripts\activate # activate venv on Windows
pip install -r requirements.txt # install dependencies
You can then open the tutorial by running jupyter lab and starting flow_lowcarb_tutorial.ipynb.
Metadata
Release files for flwr-lowcarb 0.1.7
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 |
|---|---|---|---|---|
| flwr-lowcarb-0.1.7.tar.gz | 1.5 MB | Without provenance | Details for flwr-lowcarb-0.1.7.tar.gz |
Release files / flwr-lowcarb-0.1.7.tar.gz
| Download URL | flwr-lowcarb-0.1.7.tar.gz |
|---|---|
| Size | 1.5 MB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
2f52765df5c0544fb270789805d33816600e13656a821474c5b40bc3b448aa0d
|
|
BLAKE2b-256 checksum How to use checksums |
6c13e52658ccaddfe7c4fb933c69928dd2a1ae28107e0c0b37ccc1827185c0c7
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.1 CPython/3.8.12
|
Security for flwr-lowcarb 0.1.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.
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.