Declair :cake:
Declair is a framework for declaratively defining hyperparameter optimization experiments. It uses Sacred for storing experiment results and supports Hyperopt for optimization.
At its core, Declair provides a YAML/JSON based language for defining parameter spaces for hyperparameter search as well as single experiment runs. These parameter spaces can be easily nested and may include Python objects and outputs of function calls.
Declair is focused on reproducibility and ease of use between machines. By the use of Sacred observers, it ensures that results of experiments are safely stored, together with the source code of all classes and objects used in them, as well as the Declair experiment configuration itself. To make reproduction of experiments easy between machines, it supports environment configuration files which can be used to store variables, like local dataset paths or secret tokens.
It contains various features to make defining experiments ergonomic. These include variable handling as well as configuration inheritance.
Usage
For detailed instructions on how to use Declair, see the documentation.
Installation
You can install Declair via pip.
pip install declair
Running the tests
Go into the root of the repository (i.e. where this README.md is), install pip install pytest and run
python -m pytest
Credits
Declair came about from attempts to recreate DeepSolaris results in PyTorch instead of Keras, with a focus on search experiment definition ergonomics and reproducibility. However, it grew to be a more extensive and general framework than originally planned. Its design based on configuration files was heavily inspired by cbds_common.
It is developed with ❤️ at CBDS.
Metadata
Release files for declair 0.1.5
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 |
|---|---|---|---|---|
| declair-0.1.5.tar.gz | 42.2 kB | Without provenance | Details for declair-0.1.5.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| declair-0.1.5-py3-none-any.whl | Python 3 | none | any | Details for declair-0.1.5-py3-none-any.whl |
Total release size: 96.8 kB
Release files / declair-0.1.5.tar.gz
| Download URL | declair-0.1.5.tar.gz |
|---|---|
| Size | 42.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
2b6c6c49756c7ecd939ceb5ccb37933f264368f018dae2bef0232e7da2cc8962
|
|
BLAKE2b-256 checksum How to use checksums |
d943c04ab48775bb98d02bc63c3bfd630655490c188e0d34b892f0879da51214
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.4.1 importlib_metadata/4.6.1 pkginfo/1.7.1 requests/2.22.0 requests-toolbelt/0.9.1 tqdm/4.46.1 CPython/3.8.10
|
Release files / declair-0.1.5-py3-none-any.whl
| Download URL | declair-0.1.5-py3-none-any.whl |
|---|---|
| Size | 54.6 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
0c90d9beb10c1736d388f22d12e72d1dfd5f27692feec46d670235330ddb9521
|
|
BLAKE2b-256 checksum How to use checksums |
67e54abe6637a65c1b2975785f637e4e0f1d6dfb4cb4d97abc27d685122ba09d
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.4.1 importlib_metadata/4.6.1 pkginfo/1.7.1 requests/2.22.0 requests-toolbelt/0.9.1 tqdm/4.46.1 CPython/3.8.10
|
Security for declair 0.1.5
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.