Classification reports in TensorFlow - Model Metrics & Evaluation

Metrics & Evaluation - Classification reports

Which metric matters for Classification Reports and WHY

A classification report summarizes key metrics: precision, recall, and F1-score for each class. These metrics help us understand how well the model predicts each category.

Precision tells us how many predicted positives are actually correct. Recall tells us how many actual positives the model found. F1-score balances precision and recall into one number.

Using these metrics together helps us see if the model is making too many false alarms (low precision) or missing important cases (low recall).

Confusion Matrix Example

      Actual \ Predicted | Positive | Negative
      -------------------|----------|---------
      Positive           |    70    |   30
      Negative           |    10    |   90
    

Here, TP=70, FN=30, FP=10, TN=90. Total samples = 70+30+10+90 = 200.

From this, precision = 70 / (70 + 10) = 0.875, recall = 70 / (70 + 30) = 0.7, F1-score = 2 * (0.875 * 0.7) / (0.875 + 0.7) ≈ 0.778.

Precision vs Recall Tradeoff with Examples

Imagine a spam email filter:

• High precision means most emails marked as spam really are spam. This avoids losing important emails.
• High recall means catching most spam emails, but might mark some good emails as spam.

For a cancer detector:

• High recall is critical to catch as many cancer cases as possible.
• Precision can be lower because false alarms can be checked further.

Classification reports help balance these needs by showing precision and recall per class.

What "Good" vs "Bad" Metric Values Look Like

Good classification report values:

• Precision and recall above 0.8 for important classes.
• F1-score close to 1 means balanced and strong performance.

Bad values:

• Precision or recall below 0.5 means many mistakes.
• Large difference between precision and recall indicates imbalance (e.g., many false positives or false negatives).

Always check metrics per class, especially if classes are imbalanced.

Common Pitfalls in Using Classification Reports

• Accuracy paradox: High accuracy can be misleading if classes are imbalanced.
• Data leakage: If test data leaks into training, metrics look unrealistically good.
• Overfitting: Very high training metrics but poor test metrics show the model memorizes data.
• Ignoring per-class metrics hides poor performance on minority classes.

Self-Check Question

Your model has 98% accuracy but only 12% recall on the fraud class. Is it good for production?

Answer: No. The model misses 88% of fraud cases (low recall), which is dangerous. High accuracy is misleading because fraud is rare. You need to improve recall to catch more fraud.

Key Result

Classification reports provide precision, recall, and F1-score per class to evaluate model performance beyond accuracy.

Practice

1. What does a classification report in TensorFlow typically show?

easy

A. Precision, recall, and F1-score for each class

B. The model's training time

C. The number of layers in the model

D. The size of the input data

Solution

1. Step 1: Understand classification report contents

   A classification report summarizes key metrics like precision, recall, and F1-score for each class predicted by the model.

2. Step 2: Identify what is NOT included

   Training time, model layers, and input size are not part of the classification report.

3. Final Answer:

   Precision, recall, and F1-score for each class -> Option A

4. Quick Check:

   Classification report = precision, recall, F1-score [OK]

Hint: Look for metrics per class, not model structure or time [OK]

Common Mistakes:

• Confusing training time with performance metrics
• Thinking model architecture details are in the report
• Assuming input data size is shown

2. Which code snippet correctly imports the function to generate a classification report in TensorFlow's ecosystem?

easy

A. import classification_report from tensorflow

B. import tensorflow.classification_report as cr

C. from sklearn.metrics import classification_report

D. from tensorflow.metrics import classification_report

Solution

1. Step 1: Recall the source of classification_report

   The classification_report function is part of scikit-learn, not TensorFlow directly.

2. Step 2: Check import syntax correctness

   from sklearn.metrics import classification_report uses correct Python import syntax from sklearn.metrics. Other options are invalid or incorrect.

3. Final Answer:

   from sklearn.metrics import classification_report -> Option C

4. Quick Check:

   Import classification_report from sklearn.metrics [OK]

Hint: classification_report is from sklearn, not tensorflow [OK]

Common Mistakes:

• Trying to import classification_report directly from tensorflow
• Using incorrect import syntax
• Confusing TensorFlow metrics with sklearn metrics

3. Given the following code, what will be the printed output?

from sklearn.metrics import classification_report
true_labels = [0, 1, 0, 1]
pred_labels = [0, 0, 0, 1]
print(classification_report(true_labels, pred_labels))

medium

A. Empty output with no metrics

B. A report showing precision, recall, and F1-score for classes 0 and 1

C. An error because labels are integers

D. Only accuracy score printed

Solution

1. Step 1: Understand input labels and predictions

   Labels are valid integers representing two classes: 0 and 1. Predictions have one mistake at index 1.

2. Step 2: What classification_report prints

   The function prints precision, recall, F1-score, and support for each class, not just accuracy or errors.

3. Final Answer:

   A report showing precision, recall, and F1-score for classes 0 and 1 -> Option B

4. Quick Check:

   classification_report outputs metrics per class [OK]

Hint: classification_report prints detailed metrics, not just accuracy [OK]

Common Mistakes:

• Expecting an error due to integer labels
• Thinking only accuracy is printed
• Assuming no output if predictions differ

4. Identify the error in this code snippet that tries to print a classification report:

from sklearn.metrics import classification_report
true = [1, 0, 1]
pred = [1, 0]
print(classification_report(true, pred))

medium

A. print statement syntax is wrong

B. classification_report is not imported correctly

C. Labels must be strings, not integers

D. The true and pred lists have different lengths

Solution

1. Step 1: Check input list lengths

   True labels list has 3 elements, predicted labels list has 2 elements. They must be the same length.

2. Step 2: Verify other code parts

   Import and print syntax are correct. Labels can be integers.

3. Final Answer:

   The true and pred lists have different lengths -> Option D

4. Quick Check:

   Input lists must match in length [OK]

Hint: Check if true and predicted label lists have same length [OK]

Common Mistakes:

• Ignoring length mismatch
• Thinking labels must be strings
• Assuming import or print is wrong

5. You trained a TensorFlow model for 3 classes: cat, dog, and rabbit. After predictions, you get this classification report:

              precision    recall  f1-score   support

         cat       0.90      0.95      0.92       100
         dog       0.70      0.60      0.65       100
      rabbit       0.50      0.40      0.44       100

    accuracy                           0.68       300
   macro avg       0.70      0.65      0.67       300
weighted avg       0.70      0.68      0.68       300

What should you focus on to improve your model?

hard

A. Improve the model's performance on the rabbit class

B. Increase the support for the cat class

C. Reduce the number of classes

D. Ignore the dog class since it has moderate scores

Solution

1. Step 1: Analyze class-wise metrics

   Rabbit class has the lowest precision (0.50), recall (0.40), and F1-score (0.44), indicating poor performance.

2. Step 2: Decide improvement focus

   Improving rabbit predictions will raise overall accuracy and balance. Increasing support or ignoring classes is not helpful.

3. Final Answer:

   Improve the model's performance on the rabbit class -> Option A

4. Quick Check:

   Lowest metrics class needs improvement [OK]

Hint: Focus on class with lowest F1-score to improve model [OK]

Common Mistakes:

• Trying to increase support instead of improving metrics
• Ignoring poorly performing classes
• Reducing classes without reason