Manage your Machine Learning Lifecycle with MLflow – Part 1
Reproducibility, good management and tracking experiments is necessary for making easy to test other’s work and analysis. In this first part we will start learning with simple examples how to record and query experiments, packaging Machine Learning models so they can be reproducible and ran on any platform using MLflow.
The Machine Learning Lifecycle Conundrum
Machine Learning (ML) is not easy, but creating a good workflow which you can reproduce, revisit and deploy to production is even harder. There has been many advances towards creating a good platform or managing solution for ML. Note that this is not the Data Science (DS) Lifecycle, which is more complex and has many parts.
The ML lifecycle exists inside the DS lifecycle.
You can check some of the projects for creating ML workflows here:
These packages are great, but not so easy to follow. Maybe the solution is a mix of these three, or something like that. But here I’ll present you the latest solution created by Databricks called MLflow.
Getting started with MLflow
MLflow is an open source platform for the complete machine learning lifecycle.
MLflow is designed to work with any ML library, algorithm, deployment tool or language. It is very easy to add MLflow to your existing ML code so you can benefit from it immediately, and to share code using any ML library that others in your organization can run. MLflow is also an open source projectthat users and library developers can extend.
Installing MLflow is very easy, you just have to run:
And this is according to the creators. But I faced several issues while installing it. So here are my recommendations (if you can run mlflow in your terminal after installing ignore ):
From Databricks: MLflow cannot be installed on the MacOS system installation of Python. We recommend installing Python 3 through the Homebrew package manager using
brew install python. (In this case, installing mlflow is now
pip3 install mlflow).
That did not work for me and I got this error:
And the way of solving that was not very easy. I’m using MacOS btw. To solve that I needed to update the protobuf library. To do that I installed the Google’s protobuf library from source:
Download the 3.5.1 version. I had the 3.3.1 before. Follow these steps:
Or try using Homebrew.
If your installation works, run
and you should see this:
Quickstart with MLflow
Now that you have MLflow installed let’s run a simple example.
Save that to train.py and then run with
You will see the following:
And that’s it? Nope. With MLflow you have a UI that you can access easily writing:
And you will see (localhost:5000 by default):
So what have we done so far? If you see the code you’ll se we used two things, a log_param, log_metric and log_artifact. The first one logs the passed-in parameter under the current run, creating a run if necessary, the second one logs the passed-in metric under the current run, creating a run if necessary, and the last one log a local file or directory as an artifact of the currently active run.
So with this simple example we learned how to save the log of params, metrics and files in our lifecycle.
If we click on the date of the run, we can see more about it.
Now if we click the metric, we can see how it got updated through the run:
And if we click the artifact we can see a preview of it:
The MLflow Tracking component lets you log and query experiments using either REST or Python.
Each run records the following information:
Code Version: Git commit used to execute the run, if it was executed from an MLflow Project.
Start & End: TimeStart and end time of the run
Source: Name of the file executed to launch the run, or the project name and entry point for the run if the run was executed from an MLflow Project.
Parameters: Key-value input parameters of your choice. Both keys and values are strings.
Metrics: Key-value metrics where the value is numeric. Each metric can be updated throughout the course of the run (for example, to track how your model’s loss function is converging), and MLflow will record and let you visualize the metric’s full history.
Artifacts: Output files in any format. For example, you can record images (for example, PNGs), models (for example, a pickled SciKit-Learn model) or even data files (for example, a Parquet file) as artifacts.
Runs can optionally be organized into experiments, which group together runs for a specific task. You can create an experiment via the
mlflow.create_experiment(), or via the corresponding REST parameters.
And then you just launch an experiment:
Example of Tracking:
A simple example using the Wine Quality dataset: Two datasets are included, related to red and white vinho verde wine samples, from the north of Portugal. The goal is to model wine quality based on physicochemical tests.
First download this file:
And then in the folder create the file train.py with the content:
Here we will thest MLflow integration for SciKit-Learn too. After running you will see in the terminal this:
And then run the mlflow ui in the same current working directory as the one which contains the
mlruns directory and navigate your browser to http://localhost:5000. You will see:
And you will have this for each run, so you can track everything you do. Also the model have a pkl file and a YAML for deployment, reproduction and sharing.
Stay tuned for more
In the next post I’ll cover the Projects and Models API, where we will be able to run in production these models, also create a full lifecycle.
Make sure to check the MLflow project for more:
Thanks for reading this. I hope you found something interesting here :)
If you have questions just follow me on Twitter
See you there :)
Bio: Favio Vazquez is a physicist and computer engineer working on Data Science and Computational Cosmology. He has a passion for science, philosophy, programming, and music. Right now he is working on data science, machine learning and big data as the Principal Data Scientist at Oxxo. Also, he is the creator of Ciencia y Datos, a Data Science publication in Spanish. He loves new challenges, working with a good team and having interesting problems to solve. He is part of Apache Spark collaboration, helping in MLlib, Core and the Documentation. He loves applying his knowledge and expertise in science, data analysis, visualization, and automatic learning to help the world become a better place.
Original. Reposted with permission.
- My Journey into Deep Learning
- Machine Learning with Optimus on Apache Spark
- Deep Learning With Apache Spark: Part 1
Top Stories Past 30 Days