Weights and Biases overview in MLOps - Cheat Sheet & Quick Revision

Recall & Review

beginner

What is Weights and Biases (W&B)?

Weights and Biases is a tool that helps track machine learning experiments, visualize results, and collaborate with teams easily.

beginner

How does W&B help in machine learning projects?

W&B helps by logging metrics, saving model versions, visualizing training progress, and sharing results with others.

beginner

What is a W&B run?

A run is a single execution of a machine learning experiment tracked by W&B, including parameters, metrics, and outputs.

beginner

Name one way W&B integrates with your code.

You can integrate W&B by adding a few lines of code to initialize W&B and log metrics during training.

beginner

Why is collaboration easier with W&B?

Because W&B stores all experiment data in the cloud, teams can view, compare, and discuss results in one place.

What does a W&B run represent?

A A cloud server instance

B A saved model file

C A dataset version

D A single machine learning experiment execution

A W&B run tracks one experiment execution including parameters and metrics.

Which of these is NOT a feature of W&B?

A Experiment tracking

B Model versioning

C Cloud storage for datasets

D Visualizing training metrics

W&B focuses on experiment tracking and model versioning, but does not provide cloud storage for datasets.

How do you start tracking an experiment with W&B in your code?

A Initialize W&B with wandb.init()

B Upload your code to W&B website

C Run a special W&B command in terminal

D Create a new dataset in W&B

You start tracking by calling wandb.init() in your training script.

What benefit does W&B provide for team projects?

A Centralized experiment sharing and comparison

B Automatic code debugging

C Free cloud GPU access

D Dataset labeling tools

W&B allows teams to share and compare experiments easily in one place.

Which metric can W&B help you visualize?

A Number of CPU cores

B Training loss over time

C Disk space usage

D Network bandwidth

W&B helps visualize training metrics like loss and accuracy during model training.

Explain how Weights and Biases helps in managing machine learning experiments.

Think about how you keep notes and share progress with friends.

Describe the steps to integrate W&B into a machine learning training script.

It's like adding a helper to watch and record your work.

Practice

1. What is the main purpose of Weights and Biases (W&B) in machine learning?

easy

A. To deploy machine learning models to production automatically

B. To write machine learning algorithms from scratch

C. To replace the need for training data

D. To track experiments, log metrics, and visualize results

Solution

1. Step 1: Understand W&B's role

   W&B is designed to help track experiments and log metrics during ML development.

2. Step 2: Identify main features

   It provides visualization and comparison of results in a dashboard, not algorithm creation or deployment.

3. Final Answer:

   To track experiments, log metrics, and visualize results -> Option D

4. Quick Check:

   W&B tracks and visualizes experiments [OK]

Hint: Remember W&B is for tracking and visualizing experiments [OK]

Common Mistakes:

• Confusing W&B with model deployment tools
• Thinking W&B writes ML algorithms
• Assuming W&B replaces training data

2. Which of the following is the correct command to initialize a W&B run in Python?

easy

A. wandb.init(project="my-project")

B. wandb.start(project="my-project")

C. wandb.run(project="my-project")

D. wandb.create(project="my-project")

Solution

1. Step 1: Recall W&B initialization syntax

   The correct function to start a run is wandb.init() with project name as argument.

2. Step 2: Check other options

   Functions like start(), run(), or create() do not exist in W&B API for initialization.

3. Final Answer:

   wandb.init(project="my-project") -> Option A

4. Quick Check:

   Use wandb.init() to start runs [OK]

Hint: Use wandb.init() to start tracking runs [OK]

Common Mistakes:

• Using wandb.start() instead of wandb.init()
• Confusing run() or create() as initialization methods
• Missing the project argument

3. Given this Python snippet using W&B:

import wandb
wandb.init(project="test")
for epoch in range(2):
    wandb.log({"accuracy": 0.8 + 0.1 * epoch})

What will be the logged accuracy values after the loop?

medium

A. [0.9, 1.0]

B. [0.8, 0.9]

C. [0.8, 0.85]

D. [0.7, 0.8]

Solution

1. Step 1: Analyze the loop iterations

   The loop runs for epoch = 0 and epoch = 1 (2 iterations).

2. Step 2: Calculate logged accuracy values

   For epoch 0: 0.8 + 0.1*0 = 0.8; for epoch 1: 0.8 + 0.1*1 = 0.9.

3. Final Answer:

   [0.8, 0.9] -> Option B

4. Quick Check:

   Accuracy logged = [0.8, 0.9] [OK]

Hint: Calculate values for each epoch carefully [OK]

Common Mistakes:

• Miscomputing the accuracy formula
• Confusing loop range endpoints
• Assuming only one iteration

4. You wrote this code snippet to log loss values with W&B but no data appears in the dashboard:

import wandb
wandb.init(project="demo")
for i in range(3):
    loss = 0.5 / (i+1)
    wandb.log(loss)

What is the error?

medium

A. wandb.log() requires a dictionary, not a single value

B. wandb.init() is missing the entity parameter

C. The loop range should start from 1, not 0

D. loss variable is not defined before wandb.log()

Solution

1. Step 1: Check wandb.log() usage

   wandb.log() expects a dictionary with metric names as keys, not a single float value.

2. Step 2: Identify correct logging format

   It should be wandb.log({"loss": loss}) to log the loss metric properly.

3. Final Answer:

   wandb.log() requires a dictionary, not a single value -> Option A

4. Quick Check:

   Always log metrics as dict in wandb.log() [OK]

Hint: Log metrics as dictionaries: wandb.log({"metric": value}) [OK]

Common Mistakes:

• Passing a float directly to wandb.log()
• Forgetting to name the metric in a dict
• Assuming wandb.init() needs entity always

5. You want to compare two models' training runs side-by-side using W&B. Which approach best helps you achieve this?

hard

A. Use separate projects for each model and avoid comparing runs

B. Train models without logging and manually compare saved files

C. Log both models in the same project and use the W&B dashboard to compare runs

D. Log only the best model to reduce clutter

Solution

1. Step 1: Understand W&B project and run organization

   Logging both models in the same project allows easy side-by-side comparison in the dashboard.

2. Step 2: Evaluate other options

   Not logging or using separate projects makes comparison harder; logging only one model loses data.

3. Final Answer:

   Log both models in the same project and use the W&B dashboard to compare runs -> Option C

4. Quick Check:

   Same project logging enables run comparison [OK]

Hint: Use one project for related runs to compare easily [OK]

Common Mistakes:

• Not logging runs for comparison
• Using separate projects unnecessarily
• Logging only one model run