a2ml - Automation of AutoML
The A2ML ("Automate AutoML") project is a Python API and set of command line tools to automate Automated Machine Learning tools from multiple vendors. The intention is to provide a common API for all Cloud-oriented AutoML vendors. Data scientists can then train their datasets against multiple AutoML models to get the best possible predictive model. May the best "algorithm/hyperparameter search" win. Full documentation for A2ML is available at a2ml.org
The PREDIT Pipeline
Every AutoML vendor has their own API to manage the datasets and create and manage predictive models. They are similar but not identical APIs. But they share a common set of stages:
- Importing data for training
- Train models with multiple algorithms and hyperparameters
- Evaluate model performance and choose one or more for deployment
- Deploy selected models
- Predict results with new data against deployed models
- Review performance of deployed models
Since ITEDPR is hard to remember we refer to this pipeline by its conveniently mnemonic anagram: "PREDIT" (French for "predict"). The A2ML project provides classes which implement this pipeline for various Cloud AutoML providers and a command line interface that invokes stages of the pipeline.
Setup
A2ML is distributed as a python package, so to install it:
$ pip install -U a2ml
It will install Auger provider.
To use Azure AutoML:
Mac:
$ brew install libomp
For Mac OS High Sierra and below:
$ SKLEARN_NO_OPENMP=1 pip install "scikit-learn==0.21.3"
$ pip install "a2ml[azure]" --ignore-installed onnxruntime onnx nimbusml
Linux:
$ apt-get update && apt-get -y install gcc g++ libgomp1
$ pip install "a2ml[azure]"
To use Google Cloud:
$ pip install "a2ml[google]"
To install everything including testing and server code:
$ pip install "a2ml[all]"
Development
To release a new version the flow should be:
-
Change the
__version__variable ina2ml/__init__.pyto match what you want to release, minus the "v". By default it would be ".dev0", for example "0.3.0.dev0". This ensures we don’t accidentally release a dev version to pypi.org. So for when we’re ready to release 0.3.0, the__version__variable should simply be "0.3.0". -
Commit and push the changes above.
git tag v<the-version> (for example: git tag v0.3.0)
git push --tags
- verify circleci build passed and docker image tag exists:
pip install -U a2ml==0.3.0
docker pull augerai/a2ml:v0.3.0
- Increment the
__version__variable ina2ml/__init__.pyto the next version in the current milestone. For example, "0.3.1.dev0"
3 maintainers
Metadata
3 maintainers
Release files for a2ml 1.1.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 | |
|---|---|---|---|
| a2ml-1.1.0.tar.gz | 141.7 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| a2ml-1.1.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 330.9 kB
Release files / a2ml-1.1.0.tar.gz
| Download URL | a2ml-1.1.0.tar.gz |
|---|---|
| Size | 141.7 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
49ae779f15b5413fe76124537cd2c2c7fad9576cb3892cf58bb969bee58b026d
|
|
BLAKE2b-256 checksum How to use checksums |
329694e52f5c23a9b84fead53ba7067ec0190fb76c1261f401b2e46b782632b8
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.0.1 CPython/3.11.11
|
Release files / a2ml-1.1.0-py3-none-any.whl
| Download URL | a2ml-1.1.0-py3-none-any.whl |
|---|---|
| Size | 189.2 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
00b606e14efaae4c10d51784de6d51aeacabf0922fe93e77632420daefdf00a1
|
|
BLAKE2b-256 checksum How to use checksums |
460f7a9776385f6c3cd361545a18e9637b587e38cc77070287aaed6b13a03149
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.0.1 CPython/3.11.11
|
