runyard (Python client)
See the main README.
Optional extras: images (numpy, Pillow), system (GPU, CPU and RAM usage), video (imageio-ffmpeg: frames
become an H.264 mp4 instead of a GIF) and tensorboard (for runyard watch DIR, which sends TensorBoard event
files: one run per directory, --once to import and exit). runyard --help lists the commands.
Framework adapters
runyard.integrations.<module> imports its framework, which you install yourself. Keyword arguments other than
project and name go to runyard.init (tags, notes, system, ...).
| Module | One line | Run, config, metrics |
|---|---|---|
hf |
Trainer(..., callbacks=[RunyardCallback()]) |
per training; TrainingArguments and model config; train/, eval/ by global step |
accelerate |
Accelerator(log_with=[RunyardTracker(project=...)]) |
per init_trackers; its config; accelerator.log() |
lightning |
Trainer(logger=RunyardLogger(project=...)) |
per Trainer call; hyperparameters; logged metrics by global step |
keras |
model.fit(..., callbacks=[RunyardCallback(project=...)]) |
per fit; fit params and parameter count; train/, val/ by epoch, batch/ with log_every_n_batches |
xgboost |
xgb.train(..., callbacks=[RunyardCallback(project=...)]) |
per training; booster training params; <eval name>/<metric> by iteration |
lightgbm |
lgb.train(..., callbacks=[runyard_callback(project=...)]) |
per training; params; <valid name>/<metric> by iteration |
sklearn |
autolog(project=...); autolog(disable=True) undoes it |
per outer fit(), named after the class; get_params(deep=False); fit_seconds, train/score |
torchtune |
metric_logger: {_component_: runyard.integrations.torchtune.RunyardLogger, project: ...} |
per recipe; resolved recipe config; the recipe's metrics by step |
On macOS, xgboost and lightgbm need brew install libomp, and they crash if torch was imported first: import them
before torch.
1 maintainer
Metadata
1 maintainer
Release files for runyard 0.4.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 |
|---|---|---|---|---|
| runyard-0.4.0.tar.gz | 33.6 kB | With provenance | Details for runyard-0.4.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| runyard-0.4.0-py3-none-any.whl | Python 3 | none | any | Details for runyard-0.4.0-py3-none-any.whl |
Total release size: 65.9 kB
Release files / runyard-0.4.0.tar.gz
| Download URL | runyard-0.4.0.tar.gz |
|---|---|
| Size | 33.6 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
d9b2b489fadace6bbc9781bb89100b5a44496e4665984ba877d70c91db80b08b
|
|
BLAKE2b-256 checksum How to use checksums |
56c8962e71c23c613295223e573ad8d703f8afcd5b974265c7362fe444ccab06
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
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 Oct 31, 2026.
Transparency logRelease files / runyard-0.4.0-py3-none-any.whl
| Download URL | runyard-0.4.0-py3-none-any.whl |
|---|---|
| Size | 32.3 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
059bb1546257006e5b1ef703ddda84272ed49eee64b762f653d1eb504a835fd8
|
|
BLAKE2b-256 checksum How to use checksums |
6ee2863a06b4dc0dce4626f05f8aae7c10ab0b97e285246cfc5c424ca704fb71
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
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 Oct 31, 2026.
Transparency logSecurity for runyard 0.4.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.
Full provenance
Both files in this release have been uploaded with provenance metadata.
Attestation for runyard-0.4.0.tar.gz
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 Oct 31, 2026.
Transparency logA 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.
