Logging parameters and metrics in MLOps - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to log a parameter using MLflow.

MLOps

mlflow.log_param("learning_rate", [1])

Drag options to blanks, or click blank then click option'

A0.01

Blearning_rate

C"0.01"

Dparam

Attempts:

3 left

💡 Hint

Common Mistakes

Putting the number inside quotes makes it a string, which is allowed but not typical for numeric parameters.

Using variable names without defining them causes errors.

The log_param function expects the parameter value, here a float 0.01 is correct.

2fill in blank

medium

Complete the code to log a metric named 'accuracy' with a value of 0.95.

MLOps

mlflow.log_metric("accuracy", [1])

Drag options to blanks, or click blank then click option'

A0.95

Bmetric

Caccuracy

D"0.95"

Attempts:

3 left

💡 Hint

Common Mistakes

Using strings instead of numbers for metric values.

Confusing metric names with values.

The log_metric function expects a numeric value for the metric, so 0.95 is correct.

3fill in blank

hard

Fix the error in logging a parameter where the variable 'lr' holds the learning rate.

MLOps

mlflow.log_param("learning_rate", [1])

Drag options to blanks, or click blank then click option'

Alearning_rate

Blr

C"lr"

DlearningRate

Attempts:

3 left

💡 Hint

Common Mistakes

Passing variable names as strings instead of variables.

Using undefined variable names.

The variable lr holds the value to log, so it should be passed directly without quotes.

4fill in blank

hard

Fill both blanks to log a metric 'f1_score' with value stored in variable 'score'.

MLOps

mlflow.log_metric([1], [2])

Drag options to blanks, or click blank then click option'

A"f1_score"

Bscore

Cf1_score

D"score"

Attempts:

3 left

💡 Hint

Common Mistakes

Using variable names without quotes for metric names.

Putting variable names inside quotes for values.

The metric name must be a string, so "f1_score" is correct. The value is the variable score.

5fill in blank

hard

Fill all three blanks to log parameters and metrics in a run.

MLOps

with mlflow.start_run():
    mlflow.log_param("batch_size", [1])
    mlflow.log_metric("accuracy", [2])
    mlflow.log_metric("loss", [3])

Drag options to blanks, or click blank then click option'

A32

B0.89

C0.12

Dbatch_size

Attempts:

3 left

💡 Hint

Common Mistakes

Using variable names instead of values.

Putting numeric values inside quotes.

Parameters and metrics are logged with their values: batch size as integer 32, accuracy and loss as floats 0.89 and 0.12 respectively.

Practice

1.

What is the main purpose of logging parameters in machine learning experiments?

easy

A. To record the settings used during model training

B. To measure the model's accuracy on test data

C. To save the final trained model file

D. To visualize the model's predictions

Solution

1. Step 1: Understand what parameters are

   Parameters are the settings or configurations used to train a model, like learning rate or number of layers.

2. Step 2: Identify the purpose of logging parameters

   Logging parameters helps keep track of these settings so you can compare different training runs.

3. Final Answer:

   To record the settings used during model training -> Option A

4. Quick Check:

   Logging parameters = record training settings [OK]

Hint: Parameters = training settings, metrics = performance [OK]

Common Mistakes:

• Confusing parameters with metrics
• Thinking logging saves the model file
• Assuming logging is for visualization

2.

Which of the following is the correct way to log a metric named accuracy with value 0.95 using a typical MLOps logging function log_metric?

easy

A. log_metric('accuracy', 0.95)

B. log_metric(accuracy=0.95)

C. log_metric('accuracy': 0.95)

D. log_metric(0.95, 'accuracy')

Solution

1. Step 1: Understand typical function syntax

   Logging functions usually take the metric name as a string first, then the value as a number.

2. Step 2: Check each option's syntax

   log_metric('accuracy', 0.95) uses correct syntax: function name, string key, numeric value. log_metric(accuracy=0.95) uses keyword argument which may not be supported. log_metric('accuracy': 0.95) uses invalid syntax with colon inside parentheses. log_metric(0.95, 'accuracy') reverses arguments incorrectly.

3. Final Answer:

   log_metric('accuracy', 0.95) -> Option A

4. Quick Check:

   Function(metric_name, value) = correct syntax [OK]

Hint: Metric name first as string, then value [OK]

Common Mistakes:

• Using colon instead of comma in function call
• Passing arguments in wrong order
• Using keyword arguments when not supported

3.

Given the following code snippet, what will be the output logged for the metric loss?

log_metric('loss', 0.25)
log_metric('loss', 0.20)
log_metric('loss', 0.15)

medium

A. Only the last value 0.15 is logged for 'loss'

B. An error occurs because 'loss' is logged multiple times

C. All three values 0.25, 0.20, and 0.15 are logged separately

D. The first value 0.25 overwrites the others

Solution

1. Step 1: Understand metric logging behavior

   Most MLOps tools allow logging multiple values for the same metric over time to track progress.

2. Step 2: Analyze the code snippet

   The code logs 'loss' three times with different values. Each call records a new metric value, not overwriting previous ones.

3. Final Answer:

   All three values 0.25, 0.20, and 0.15 are logged separately -> Option C

4. Quick Check:

   Multiple logs for same metric = multiple entries [OK]

Hint: Repeated metric logs add entries, not overwrite [OK]

Common Mistakes:

• Assuming repeated logs overwrite previous values
• Expecting an error on duplicate metric names
• Thinking only one value per metric is allowed

4.

Identify the error in this code snippet for logging a parameter batch_size with value 32:

log_param(batch_size, '32')

medium

A. Function name should be log_metric instead of log_param

B. Value should be a number, not a string

C. No error, the code is correct

D. Parameter name should be a string, not a variable

Solution

1. Step 1: Check parameter name argument

   The parameter name must be a string literal like 'batch_size', not a bare variable name.

2. Step 2: Check value argument

   Value can be string or number depending on context; '32' as string is acceptable here.

3. Final Answer:

   Parameter name should be a string, not a variable -> Option D

4. Quick Check:

   Parameter name = string literal [OK]

Hint: Parameter names must be quoted strings [OK]

Common Mistakes:

• Passing parameter name without quotes
• Confusing log_param with log_metric
• Thinking value must always be numeric

5.

You want to log both parameters and metrics for a training run using the following code:

log_param('learning_rate', 0.01)
log_param('optimizer', 'adam')
log_metric('accuracy', 0.92)
log_metric('loss', 0.1)

Which of these statements is true about the logged data?

hard

A. Metrics record model settings; parameters record model performance

B. Parameters record model settings; metrics record model performance

C. Both parameters and metrics record model performance

D. Both parameters and metrics record model settings

Solution

1. Step 1: Understand the role of parameters

   Parameters like learning rate and optimizer are settings used to train the model.

2. Step 2: Understand the role of metrics

   Metrics like accuracy and loss measure how well the model performs after training.

3. Final Answer:

   Parameters record model settings; metrics record model performance -> Option B

4. Quick Check:

   Parameters = settings, Metrics = performance [OK]

Hint: Parameters = settings, metrics = results [OK]

Common Mistakes:

• Mixing up parameters and metrics roles
• Thinking metrics are settings
• Assuming parameters measure performance