Weight initialization strategies in TensorFlow - Model Metrics & Evaluation

Metrics & Evaluation - Weight initialization strategies

Which metric matters for Weight Initialization and WHY

Weight initialization affects how well and how fast a model learns. The key metrics to watch are training loss and validation loss. Good initialization helps the model start learning without getting stuck or exploding gradients. If loss decreases smoothly, initialization is likely good.

Confusion Matrix or Equivalent Visualization

Weight initialization itself does not produce a confusion matrix. Instead, we observe training curves showing loss or accuracy over time. For example:

Epoch | Training Loss | Validation Loss
---------------------------------------
  1   |     1.2      |      1.3
  2   |     0.8      |      0.9
  3   |     0.5      |      0.6
  ... 
    

Smoothly decreasing loss means weights started well. If loss stays high or NaN, initialization may be poor.

Tradeoff: Initialization Strategies

Simple random initialization can cause gradients to vanish or explode, slowing learning. Using He initialization or Glorot (Xavier) initialization balances variance of activations and gradients, helping stable training.

For example, He initialization works well with ReLU activations, while Glorot suits sigmoid or tanh. Choosing the wrong one can make training slow or unstable.

Good vs Bad Metric Values for Weight Initialization

Good: Training loss decreases steadily from the first epoch, validation loss follows closely, and accuracy improves smoothly.

Bad: Training loss stays flat or increases, validation loss is erratic, or loss becomes NaN. This suggests poor initialization causing unstable gradients.

Common Pitfalls in Weight Initialization Metrics

• Vanishing gradients: Weights too small cause gradients to shrink, stopping learning.
• Exploding gradients: Weights too large cause gradients to grow uncontrollably.
• Ignoring activation function: Using wrong initialization for activation slows or breaks training.
• Overfitting signs: Good training loss but bad validation loss is not an initialization issue but model complexity.

Self Check

Your model shows training loss stuck at 2.0 and validation loss is NaN from the start. Is your weight initialization good?

Answer: No. This suggests poor initialization causing unstable gradients or numerical issues. Try He or Glorot initialization matching your activation.

Key Result

Good weight initialization leads to smooth, steady decrease in training and validation loss, enabling stable learning.

Practice

1. Which weight initialization strategy is best suited for layers using ReLU activation in TensorFlow?

easy

A. Zeros initializer

B. GlorotUniform initializer

C. RandomNormal initializer with mean 0

D. HeNormal initializer

Solution

1. Step 1: Understand activation and initialization relation

   ReLU activation benefits from initial weights that maintain variance through layers to avoid dying neurons.

2. Step 2: Match initializer to activation

   HeNormal initializer is designed for ReLU, scaling weights to keep variance stable.

3. Final Answer:

   HeNormal initializer -> Option D

4. Quick Check:

   ReLU uses HeNormal [OK]

Hint: Use HeNormal for ReLU activations to keep variance stable [OK]

Common Mistakes:

• Choosing GlorotUniform for ReLU layers
• Using zeros initializer causing no learning
• RandomNormal without scaling causes slow training

2. Which of the following is the correct syntax to initialize weights with GlorotUniform in TensorFlow?

easy

A. tf.keras.initializers.glorot_uniform()

B. tf.initializers.GlorotUniform()

C. tf.keras.initializers.GlorotUniform()

D. tf.keras.initializers.Glorot_uniform()

Solution

1. Step 1: Recall TensorFlow initializer module

   Initializers are accessed via tf.keras.initializers with exact class names.

2. Step 2: Check correct class name and casing

   The correct class name is GlorotUniform with capital G and U, called as a class with parentheses.

3. Final Answer:

   tf.keras.initializers.GlorotUniform() -> Option C

4. Quick Check:

   Correct class name and module path [OK]

Hint: Use exact class name with correct casing and parentheses [OK]

Common Mistakes:

• Using lowercase function names instead of class
• Missing parentheses after class name
• Using wrong module path tf.initializers

3. What will be the output shape and initializer type of the following TensorFlow layer?

layer = tf.keras.layers.Dense(10, kernel_initializer=tf.keras.initializers.HeNormal())
print(layer.kernel_initializer)

medium

A. GlorotUniform initializer object, output shape (None, 10)

B. HeNormal initializer object, output shape (None, 10)

C. HeNormal initializer object, output shape (10, 10)

D. RandomNormal initializer object, output shape (None, 10)

Solution

1. Step 1: Identify initializer and layer output

   The layer uses HeNormal initializer explicitly for kernel weights and has 10 output units.

2. Step 2: Understand output shape of Dense layer

   Dense layers output shape is (batch_size, units), so shape is (None, 10) before input is given.

3. Final Answer:

   HeNormal initializer object, output shape (None, 10) -> Option B

4. Quick Check:

   HeNormal used and output units = 10 [OK]

Hint: Dense output shape is (None, units); initializer matches given class [OK]

Common Mistakes:

• Confusing output shape with kernel shape
• Assuming default initializer instead of HeNormal
• Mixing initializer types

4. You wrote this code to initialize weights but get an error:

layer = tf.keras.layers.Dense(5, kernel_initializer='he_normal')
model = tf.keras.Sequential([layer])
model.build(input_shape=(None, 3))
print(layer.kernel_initializer())

What is the cause of the error?

medium

A. Calling kernel_initializer as a function without arguments

B. Using string 'he_normal' instead of initializer object

C. Not specifying bias_initializer

D. Missing input_shape in layer constructor

Solution

1. Step 1: Understand kernel_initializer attribute type

   kernel_initializer is an initializer object, not a callable function without arguments.

2. Step 2: Identify error cause

   Calling kernel_initializer() without arguments causes error because it expects shape and dtype parameters.

3. Final Answer:

   Calling kernel_initializer as a function without arguments -> Option A

4. Quick Check:

   Initializer needs shape args, can't call empty () [OK]

Hint: Don't call kernel_initializer() without shape and dtype [OK]

Common Mistakes:

• Confusing string initializer with object
• Ignoring required arguments for initializer call
• Assuming bias_initializer causes this error

5. You want to initialize weights for a model with mixed activations: ReLU in some layers and sigmoid in others. Which strategy best improves training speed and accuracy?

hard

A. Use HeNormal for ReLU layers and GlorotUniform for sigmoid layers

B. Use GlorotUniform for all layers regardless of activation

C. Use RandomNormal with mean 0 and stddev 1 for all layers

D. Use Zeros initializer for all layers to start from zero

Solution

1. Step 1: Match initializers to activation functions

   HeNormal suits ReLU to maintain variance; GlorotUniform suits sigmoid/tanh to avoid saturation.

2. Step 2: Understand impact on training

   Proper matching prevents slow or stuck training and improves accuracy by keeping gradients healthy.

3. Final Answer:

   Use HeNormal for ReLU layers and GlorotUniform for sigmoid layers -> Option A

4. Quick Check:

   Match initializer to activation for best training [OK]

Hint: Match HeNormal to ReLU, GlorotUniform to sigmoid/tanh [OK]

Common Mistakes:

• Using same initializer for all activations
• Using zeros initializer causing no learning
• Using RandomNormal without scaling