nn.GRU layer in PyTorch - Model Metrics & Evaluation

Metrics & Evaluation - nn.GRU layer

Which metric matters for nn.GRU layer and WHY

The nn.GRU layer is used for sequence data, like sentences or time series. The key metrics depend on the task it solves. For classification tasks, accuracy, precision, and recall matter because they show how well the GRU predicts correct classes over time. For regression tasks, mean squared error (MSE) or mean absolute error (MAE) are important to measure how close predictions are to actual values. These metrics help us understand if the GRU is learning useful patterns in sequences.

Confusion matrix example for nn.GRU classification

      Actual \ Predicted | Positive | Negative
      -------------------|----------|---------
      Positive           |    50    |   10    
      Negative           |    5     |   35    
    

This matrix shows 50 true positives (TP), 10 false negatives (FN), 5 false positives (FP), and 35 true negatives (TN). From this, we calculate precision and recall to evaluate the GRU's classification performance.

Precision vs Recall tradeoff with nn.GRU

Imagine a GRU model detecting spam emails. If it has high precision, it means most emails marked as spam really are spam, so good emails are rarely blocked. If it has high recall, it catches almost all spam emails but might wrongly block some good emails. Depending on what matters more (avoiding spam or avoiding blocking good emails), you adjust the GRU's threshold to balance precision and recall.

Good vs Bad metric values for nn.GRU

For classification with GRU:

• Good: Precision and recall above 0.8, accuracy above 0.85, F1 score balanced and high.
• Bad: Precision or recall below 0.5, accuracy close to random guessing (e.g., 0.5 for binary), F1 score very low.

For regression with GRU:

• Good: Low MSE or MAE, showing predictions close to actual values.
• Bad: High MSE or MAE, meaning predictions are far off.

Common pitfalls when evaluating nn.GRU

• Accuracy paradox: High accuracy can be misleading if classes are imbalanced. For example, if 95% of data is one class, predicting that class always gives 95% accuracy but poor real performance.
• Data leakage: If future sequence data leaks into training, the GRU looks better than it really is.
• Overfitting: GRU may memorize training sequences but fail on new data. Watch for big gaps between training and validation metrics.
• Ignoring sequence length: GRU performance can vary with sequence length; metrics should consider this.

Self-check question

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

Answer: No, it is not good. The low recall means the model misses most fraud cases, which is dangerous. High accuracy is misleading here because fraud is rare. For fraud detection, recall is critical to catch as many frauds as possible.

Key Result

For nn.GRU, precision and recall are key for classification tasks to balance correct detection and missed cases; for regression, low error metrics show good performance.

Practice

1. What is the primary purpose of the nn.GRU layer in PyTorch?

easy

A. To reduce the dimensionality of data using PCA

B. To perform image classification using convolution

C. To process sequential data by remembering past information

D. To generate random numbers for initialization

Solution

1. Step 1: Understand the role of GRU

   The GRU (Gated Recurrent Unit) is designed to handle sequences by keeping track of past inputs, which helps in tasks like text or speech processing.

2. Step 2: Compare with other options

   The other options describe unrelated tasks: dimensionality reduction using PCA, image classification using convolution, and random number generation, which are not the purpose of GRU.

3. Final Answer:

   To process sequential data by remembering past information -> Option C

4. Quick Check:

   GRU = sequence memory [OK]

Hint: GRU remembers past inputs in sequences [OK]

Common Mistakes:

• Confusing GRU with convolution layers
• Thinking GRU reduces data dimensions like PCA
• Assuming GRU generates random values

2. Which of the following is the correct way to create a GRU layer with input size 10 and hidden size 20 in PyTorch?

easy

A. nn.GRU(20, 10)

B. nn.GRU(input_size=10, hidden_size=20)

C. nn.GRU(hidden_size=10, input_size=20)

D. nn.GRU(10)

Solution

1. Step 1: Recall GRU constructor parameters

   The correct order and names are input_size first, then hidden_size. So nn.GRU(input_size=10, hidden_size=20) is correct.

2. Step 2: Check other options

   nn.GRU(20, 10) reverses the sizes. nn.GRU(hidden_size=10, input_size=20) swaps parameter names incorrectly. nn.GRU(10) misses the hidden size parameter.

3. Final Answer:

   nn.GRU(input_size=10, hidden_size=20) -> Option B

4. Quick Check:

   Input size first, hidden size second [OK]

Hint: Remember: input_size before hidden_size in nn.GRU [OK]

Common Mistakes:

• Swapping input_size and hidden_size
• Omitting hidden_size parameter
• Using wrong parameter names

3. Given the following code, what is the shape of the output tensor out?

import torch
import torch.nn as nn

gru = nn.GRU(input_size=5, hidden_size=3, batch_first=True)
x = torch.randn(4, 7, 5)  # batch=4, seq_len=7, input_size=5
out, h_n = gru(x)
print(out.shape)

medium

A. (4, 7, 3)

B. (7, 4, 3)

C. (4, 3, 7)

D. (7, 3, 4)

Solution

1. Step 1: Understand batch_first=True effect

   With batch_first=True, input shape is (batch, seq_len, input_size). Output shape matches (batch, seq_len, hidden_size).

2. Step 2: Apply shapes from code

   Input is (4, 7, 5), hidden_size=3, so output out shape is (4, 7, 3).

3. Final Answer:

   (4, 7, 3) -> Option A

4. Quick Check:

   Output shape = (batch, seq_len, hidden_size) [OK]

Hint: batch_first=True means batch is first dimension [OK]

Common Mistakes:

• Confusing batch and sequence dimensions
• Ignoring batch_first parameter
• Mixing hidden_size with input_size

4. Which of the following correctly describes the execution of this code snippet?

import torch
import torch.nn as nn

gru = nn.GRU(input_size=8, hidden_size=4)
x = torch.randn(5, 10, 8)
out, h = gru(x)
print(out.shape)

medium

A. The code runs without errors and prints (5, 10, 4)

B. The hidden_size must be larger than input_size

C. The GRU layer requires batch_first=True for this input shape

D. The input tensor shape is incorrect for default GRU settings

Solution

1. Step 1: Check default GRU input expectations

   By default, GRU expects input shape (seq_len, batch, input_size). Here, input is (5, 10, 8), so seq_len=5, batch=10, input_size=8 which matches default.

2. Step 2: Verify output shape

   Output shape will be (seq_len, batch, hidden_size) = (5, 10, 4).

3. Step 3: Evaluate statements

   The code runs without errors and prints (5, 10, 4). Hidden_size can be smaller than input_size. batch_first=True is not required. Input shape is correct for default settings.

4. Final Answer:

   The code runs without errors and prints (5, 10, 4) -> Option A

5. Quick Check:

   Default GRU input shape = (seq_len, batch, input_size) [OK]

Hint: Default GRU expects seq_len first, batch second [OK]

Common Mistakes:

• Assuming batch is first dimension without batch_first=True
• Thinking hidden_size must be bigger than input_size
• Expecting output shape to swap batch and seq_len

5. You want to build a GRU-based model to process variable-length sequences in a batch. Which approach correctly handles this in PyTorch?

hard

A. Feed raw variable-length sequences directly to nn.GRU without padding

B. Manually truncate all sequences to the shortest length before input

C. Use nn.GRU with batch_first=False and ignore sequence lengths

D. Pad sequences to the same length and use pack_padded_sequence before feeding to nn.GRU

Solution

1. Step 1: Understand variable-length sequence handling

   PyTorch requires sequences in a batch to be the same length or packed. Padding sequences and using pack_padded_sequence allows GRU to ignore padded parts.

2. Step 2: Evaluate options

   Pad sequences to the same length and use pack_padded_sequence before feeding to nn.GRU correctly pads and packs sequences. Feed raw variable-length sequences directly to nn.GRU without padding is invalid because GRU cannot handle raw variable-length sequences. Use nn.GRU with batch_first=False and ignore sequence lengths ignores lengths, causing wrong results. Manually truncate all sequences to the shortest length before input loses data by truncation.

3. Final Answer:

   Pad sequences and use pack_padded_sequence before nn.GRU -> Option D

4. Quick Check:

   Use padding + packing for variable-length sequences [OK]

Hint: Pad then pack sequences before GRU [OK]

Common Mistakes:

• Feeding variable-length sequences without padding
• Ignoring sequence lengths in batch
• Truncating sequences losing data