This release is a pre-release and may not be stable for production use.
mlpipeline
This is a simple framework to organize you machine learning workflow. It automates most of the basic functionalities such as logging, a framework for testing models and gluing together different steps at different stages. This project came about as a result of me abstracting the boilerplate code and automating different parts of the process.
The aim of this simple framework is to consolidate the different sub-problems (such as loading data, model configurations, training process, evaluation process, exporting trained models, etc.) when working/researching with machine learning models. This allows the user to define how the different sub-problems are to be solved using their choice of tools and mlpipeline would handle piecing them together.
Core operations
This framework chains the different operations (sub-problems) depending on the mode it is executed in. mlpipeline currently has 3 modes:
- TEST mode: When in TEST mode, it doesn't perform any logging or tracking. It creates a temporary empty directory for the experiment to store the artifacts of an experiment in. When developing and testing the different operations, this mode can be used.
- RUN mode: In this mode, logging and tracking is performed. In addition, for each experiment run (referred to as a experiment version in mlpipeline) a directory is created for artifacts to be stored.
- EXPORT mode: In this mode, the exporting related operations will be executed instead of the training/evaluation related operations.
In addition to providing different modes, the pipeline also supports logging and recording various details. Currently mlpipeline records all logs, metrics and artifacts using a basic log files as well using mlflow <https://github.com/databricks/mlflow>_.
The following information is recorded:
- The scripts that were executed/imported in relation to an experiment.
- The any output results
- The metrics and parameters
Documentation
The documentation is hosted at ReadTheDocs <https://mlpipeline.readthedocs.io/>_.
Installing
Can be installed directly using the Python Package Index using pip::
pip install mlpipeline
Usage
work in progress
Metadata
Release files for mlpipeline 2.0a7.post1
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 |
|---|---|---|---|---|
| mlpipeline-2.0a7.post1.tar.gz | 26.6 kB | Without provenance | Details for mlpipeline-2.0a7.post1.tar.gz |
Release files / mlpipeline-2.0a7.post1.tar.gz
| Download URL | mlpipeline-2.0a7.post1.tar.gz |
|---|---|
| Size | 26.6 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
10d0df79ff72987cf5825e0b94060c80e8c0e07baf5192bfd6b155daafdb0e2b
|
|
BLAKE2b-256 checksum How to use checksums |
35e4b042535df64d8e4e95686878bf3e7e382019256d55ef894f2d1f39961bb5
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.2.0 pkginfo/1.6.1 requests/2.25.0 setuptools/50.3.2 requests-toolbelt/0.9.1 tqdm/4.54.1 CPython/3.8.6
|
Security for mlpipeline 2.0a7.post1
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.