Accuracy and loss monitoring in TensorFlow - Model Pipeline Trace

Model Pipeline - Accuracy and loss monitoring

This pipeline shows how a simple neural network learns to classify handwritten digits. It tracks accuracy and loss during training to see how well the model improves over time.

Data Flow - 5 Stages

1Load Data

70000 rows x 28 x 28 pixels→Load MNIST handwritten digits dataset→70000 rows x 28 x 28 pixels

Image of digit '5' represented as 28x28 grayscale pixels

↓

2Preprocessing

70000 rows x 28 x 28 pixels→Normalize pixel values from 0-255 to 0-1→70000 rows x 28 x 28 pixels

Pixel value 150 becomes 0.588

↓

3Train/Test Split

70000 rows x 28 x 28 pixels→Split dataset into training and testing sets→60000 rows x 28 x 28 pixels (train), 10000 rows x 28 x 28 pixels (test)

Training set contains digit images for learning

↓

4Flatten Images

60000 rows x 28 x 28 pixels→Convert 2D images to 1D vectors→60000 rows x 784 columns

28x28 image becomes a 784-length vector

↓

5Model Training

60000 rows x 784 columns→Train neural network with 1 hidden layer→Model weights updated

Weights adjust to better classify digits

Training Trace - Epoch by Epoch

Loss: 0.45 |****      |
Loss: 0.30 |*******   |
Loss: 0.22 |********* |
Loss: 0.18 |**********|
Loss: 0.15 |**********|

Epoch	Loss ↓	Accuracy ↑	Observation
1	0.45	0.85	Model starts learning, accuracy is moderate
2	0.30	0.91	Loss decreases, accuracy improves
3	0.22	0.94	Model continues to improve
4	0.18	0.95	Loss decreases steadily, accuracy high
5	0.15	0.96	Training converges with good accuracy

Prediction Trace - 3 Layers

Layer 1: Input Layer

Layer 2: Hidden Layer (ReLU activation)

Layer 3: Output Layer (Softmax)

Model Quiz - 3 Questions

What does a decreasing loss during training indicate?

A The model is learning and improving

B The model is forgetting data

C The data is getting corrupted

D The training stopped

Key Insight

Monitoring accuracy and loss during training helps us understand if the model is learning well. Decreasing loss and increasing accuracy show the model improves its predictions over time.

Practice

1. What is the main purpose of monitoring accuracy and loss during TensorFlow model training?

easy

A. To change the model architecture automatically

B. To track how well the model is learning and improving

C. To increase the size of the training dataset

D. To speed up the training process by skipping epochs

Solution

1. Step 1: Understand accuracy and loss roles

   Accuracy shows how many predictions are correct, loss shows error size.

2. Step 2: Purpose of monitoring during training

   Tracking these helps see if the model is learning or needs adjustment.

3. Final Answer:

   To track how well the model is learning and improving -> Option B

4. Quick Check:

   Accuracy and loss track learning progress = C [OK]

Hint: Accuracy and loss show model learning quality [OK]

Common Mistakes:

• Thinking accuracy changes dataset size
• Believing monitoring changes model structure
• Assuming monitoring speeds training automatically

2. Which is the correct way to include accuracy monitoring when compiling a TensorFlow model?

easy

A. model.compile(optimizer='adam', loss='sparse_categorical_crossentropy', metrics=['accuracy'])

B. model.compile(optimizer='adam', loss='sparse_categorical_crossentropy')

C. model.compile(optimizer='adam', metrics=['accuracy'])

D. model.compile(loss='sparse_categorical_crossentropy', metrics='accuracy')

Solution

1. Step 1: Check required compile parameters

   Optimizer and loss are required; metrics is optional for monitoring.

2. Step 2: Correct syntax for metrics

   metrics must be a list like ['accuracy'], not a string alone.

3. Final Answer:

   model.compile(optimizer='adam', loss='sparse_categorical_crossentropy', metrics=['accuracy']) -> Option A

4. Quick Check:

   metrics=['accuracy'] in compile = B [OK]

Hint: Use metrics=['accuracy'] inside model.compile [OK]

Common Mistakes:

• Omitting metrics parameter
• Passing metrics as a string instead of list
• Leaving out loss or optimizer

3. Given this code snippet, what will print(history.history['accuracy']) output?

model.compile(optimizer='adam', loss='sparse_categorical_crossentropy', metrics=['accuracy'])
history = model.fit(x_train, y_train, epochs=2)
print(history.history['accuracy'])

medium

A. A list of loss values for each epoch

B. A single float value of final accuracy, e.g. 0.90

C. An error because 'accuracy' is not in history

D. A list of accuracy values for each epoch, e.g. [0.85, 0.90]

Solution

1. Step 1: Understand history.history content

   It stores lists of metric values per epoch, including accuracy if monitored.

2. Step 2: What history.history['accuracy'] returns

   It returns a list of accuracy values, one per epoch, not a single value or error.

3. Final Answer:

   A list of accuracy values for each epoch, e.g. [0.85, 0.90] -> Option D

4. Quick Check:

   history.history['accuracy'] = list per epoch [OK]

Hint: history.history['accuracy'] holds accuracy per epoch list [OK]

Common Mistakes:

• Expecting a single float instead of list
• Confusing accuracy with loss values
• Assuming key 'accuracy' is missing

4. You run this code but get a KeyError when accessing history.history['accuracy']. What is the likely cause?

model.compile(optimizer='adam', loss='sparse_categorical_crossentropy')
history = model.fit(x_train, y_train, epochs=3)
print(history.history['accuracy'])

medium

A. Accuracy was not included in metrics during model.compile

B. The model.fit call is missing the epochs parameter

C. The loss function is incorrect for accuracy monitoring

D. history.history only stores loss, not accuracy

Solution

1. Step 1: Check model.compile parameters

   Accuracy monitoring requires metrics=['accuracy'] in compile, missing here.

2. Step 2: Effect on history.history keys

   Without metrics=['accuracy'], history.history has no 'accuracy' key, causing KeyError.

3. Final Answer:

   Accuracy was not included in metrics during model.compile -> Option A

4. Quick Check:

   Missing metrics=['accuracy'] causes KeyError [OK]

Hint: Always add metrics=['accuracy'] to compile to track accuracy [OK]

Common Mistakes:

• Forgetting to add metrics=['accuracy']
• Assuming loss function controls accuracy keys
• Thinking epochs parameter affects history keys

5. You want to monitor both accuracy and loss during training and plot their progress after training. Which code snippet correctly compiles the model and accesses the data for plotting?

hard

A. model.compile(optimizer='adam', loss='sparse_categorical_crossentropy', metrics='accuracy')
history = model.fit(x_train, y_train, epochs=5)
plt.plot(history['accuracy'])
plt.plot(history['loss'])

B. model.compile(optimizer='adam', loss='sparse_categorical_crossentropy')
history = model.fit(x_train, y_train, epochs=5)
plt.plot(history.history['accuracy'])
plt.plot(history.history['loss'])

C. model.compile(optimizer='adam', loss='sparse_categorical_crossentropy', metrics=['accuracy'])
history = model.fit(x_train, y_train, epochs=5)
plt.plot(history.history['accuracy'])
plt.plot(history.history['loss'])

D. model.compile(optimizer='adam', loss='sparse_categorical_crossentropy', metrics=['accuracy'])
history = model.fit(x_train, y_train, epochs=5)
plt.plot(history['accuracy'])
plt.plot(history['loss'])

Solution

1. Step 1: Check model.compile metrics syntax

   metrics must be a list like ['accuracy']. B omits it, C uses string 'accuracy'.

2. Step 2: Check history access for plotting

   history.history['accuracy'] and history.history['loss'] are correct; history['accuracy'] fails as history object lacks these attributes.

3. Final Answer:

   model.compile(optimizer='adam', loss='sparse_categorical_crossentropy', metrics=['accuracy']) history = model.fit(x_train, y_train, epochs=5) plt.plot(history.history['accuracy']) plt.plot(history.history['loss']) -> Option C

4. Quick Check:

   metrics list + history.history keys = A [OK]

Hint: Use metrics=['accuracy'] and history.history for plotting [OK]

Common Mistakes:

• Passing metrics as string instead of list
• Accessing history keys directly on history object
• Omitting metrics parameter