Experiment tracking (MLflow) in ML Python - Cheat Sheet & Quick Revision

Recall & Review

beginner

What is MLflow in the context of machine learning?

MLflow is a tool that helps you keep track of your machine learning experiments. It records details like parameters, code versions, and results so you can compare and reproduce your work easily.

intermediate

Name the four main components of MLflow.

The four main components of MLflow are: 1) Tracking - logs experiments, 2) Projects - packages code, 3) Models - manages and deploys models, 4) Model Registry - central store for models.

beginner

How does MLflow Tracking help in machine learning projects?

MLflow Tracking helps by automatically saving parameters, metrics, and artifacts during training. This makes it easy to compare different runs and find the best model.

beginner

What is an artifact in MLflow Tracking?

An artifact is a file or output saved during an experiment, like a model file, a plot, or a data file. MLflow stores these so you can review or reuse them later.

beginner

Why is experiment tracking important in machine learning?

Experiment tracking is important because it helps you organize your work, avoid repeating mistakes, and share results with others. It makes your machine learning process clear and repeatable.

What does MLflow Tracking primarily record during an experiment?

A Database schemas

B Only the final model

C Parameters, metrics, and artifacts

D User interface designs

MLflow Tracking records parameters, metrics, and artifacts to help track experiments.

Which MLflow component helps package your code for sharing and reproducibility?

A Projects

B Tracking

C Models

D Registry

MLflow Projects packages your code so others can run it easily.

What is an artifact in MLflow?

A A saved file like a model or plot

B A type of parameter

C A metric value

D A user login

Artifacts are files saved during experiments, such as models or plots.

Why should you use experiment tracking in machine learning?

A To speed up the computer

B To organize and compare experiments

C To write code faster

D To create user interfaces

Experiment tracking helps organize and compare different runs to find the best results.

Which MLflow component manages model deployment and versioning?

A Tracking

B Registry

C Projects

D Models

MLflow Models manages model packaging and deployment.

Explain how MLflow Tracking helps you manage machine learning experiments.

Think about what details you want to save when training a model.

Describe the four main components of MLflow and their roles.

Each component has a specific job in the ML workflow.

Practice

1. What is the main purpose of using MLflow in machine learning projects?

easy

A. To write machine learning algorithms from scratch

B. To visualize data without any coding

C. To track and manage machine learning experiments

D. To deploy machine learning models to mobile apps

Solution

1. Step 1: Understand MLflow's role

   MLflow is designed to help track experiments by logging parameters, metrics, and models.

2. Step 2: Compare options

   Options A, C, and D describe tasks outside MLflow's main purpose.

3. Final Answer:

   To track and manage machine learning experiments -> Option C

4. Quick Check:

   MLflow = experiment tracking [OK]

Hint: MLflow is for tracking experiments, not coding models [OK]

Common Mistakes:

• Confusing MLflow with model building libraries
• Thinking MLflow is only for visualization
• Assuming MLflow deploys models directly

2. Which MLflow function is used to start a new experiment run in Python?

easy

A. mlflow.init_experiment()

B. mlflow.start_run()

C. mlflow.create_run()

D. mlflow.begin_experiment()

Solution

1. Step 1: Recall MLflow run start syntax

   The correct function to start a run is mlflow.start_run().

2. Step 2: Check other options

   Functions like init_experiment, create_run, and begin_experiment do not exist in MLflow API.

3. Final Answer:

   mlflow.start_run() -> Option B

4. Quick Check:

   Start run = mlflow.start_run() [OK]

Hint: Use start_run() to begin tracking an experiment run [OK]

Common Mistakes:

• Using non-existent MLflow functions
• Confusing experiment and run functions
• Misspelling function names

3. What will be the output of this MLflow code snippet?

import mlflow
with mlflow.start_run():
    mlflow.log_param('alpha', 0.1)
    mlflow.log_metric('accuracy', 0.95)
    run_info = mlflow.active_run().info
print(run_info.run_id is not None)

medium

A. True

B. False

C. None

D. Error

Solution

1. Step 1: Understand mlflow.start_run() context

   The code starts a run, logs parameters and metrics, then gets the active run info.

2. Step 2: Check run_id existence

   Inside the run context, run_id is assigned and not None, so print(run_info.run_id is not None) outputs True.

3. Final Answer:

   True -> Option A

4. Quick Check:

   Active run has run_id = True [OK]

Hint: Active run always has a run_id during context [OK]

Common Mistakes:

• Assuming run_id is None before logging
• Confusing run info with experiment info
• Expecting print to show run_id string

4. Identify the error in this MLflow code snippet:

import mlflow
mlflow.log_param('learning_rate', 0.01)
with mlflow.start_run():
    mlflow.log_metric('loss', 0.2)

medium

A. log_param called outside a run context

B. start_run() missing parentheses

C. log_metric called before log_param

D. No error, code runs fine

Solution

1. Step 1: Check order of MLflow calls

   log_param is called before starting a run, which is not allowed.

2. Step 2: Validate run context requirement

   MLflow requires logging functions inside a run context started by start_run().

3. Final Answer:

   log_param called outside a run context -> Option A

4. Quick Check:

   Logging outside run = error [OK]

Hint: Always log params and metrics inside start_run() [OK]

Common Mistakes:

• Calling log_param before start_run()
• Ignoring run context for logging
• Assuming log_metric order matters

5. You want to compare two ML models' performance using MLflow. Which steps correctly describe this process?

hard

A. Only log parameters for both models, metrics are not needed for comparison

B. Log both models' metrics in the same run, then compare metrics manually

C. Use mlflow.log_artifact() to save models, no need to log metrics or parameters

D. Run each model in separate mlflow.start_run() blocks, log metrics, then use MLflow UI to compare

Solution

1. Step 1: Understand MLflow run separation

   Each model should be run and logged in its own mlflow.start_run() block to keep results separate.

2. Step 2: Use MLflow UI for comparison

   After logging metrics and parameters, MLflow UI allows easy comparison of runs.

3. Final Answer:

   Run each model in separate mlflow.start_run() blocks, log metrics, then use MLflow UI to compare -> Option D

4. Quick Check:

   Separate runs + UI = compare models [OK]

Hint: Use separate runs and MLflow UI to compare models easily [OK]

Common Mistakes:

• Logging multiple models in one run
• Skipping metric logging
• Ignoring MLflow UI for comparison