Deferred Initialization

:label:sec_deferred_init

So far, it might seem that we got away with being sloppy in setting up our networks. Specifically, we did the following unintuitive things, which might not seem like they should work:

  • We defined the network architectures without specifying the input dimensionality.
  • We added layers without specifying the output dimension of the previous layer.
  • We even “initialized” these parameters before providing enough information to determine how many parameters our models should contain.

You might be surprised that our code runs at all. After all, there is no way the deep learning framework could tell what the input dimensionality of a network would be. The trick here is that the framework defers initialization, waiting until the first time we pass data through the model, to infer the sizes of each layer on the fly.

Later on, when working with convolutional neural networks, this technique will become even more convenient since the input dimensionality (i.e., the resolution of an image) will affect the dimensionality of each subsequent layer. Hence, the ability to set parameters without the need to know, at the time of writing the code, what the dimensionality is can greatly simplify the task of specifying and subsequently modifying our models. Next, we go deeper into the mechanics of initialization.

Instantiating a Network

To begin, let us instantiate an MLP.

```{.python .input} from mxnet import init, np, npx from mxnet.gluon import nn npx.set_np()

def get_net(): net = nn.Sequential() net.add(nn.Dense(256, activation=’relu’)) net.add(nn.Dense(10)) return net

net = get_net()

  2. ```{.python .input}
  3. #@tab tensorflow
  4. import tensorflow as tf
  6. net = tf.keras.models.Sequential([
  7.     tf.keras.layers.Dense(256, activation=tf.nn.relu),
  8.     tf.keras.layers.Dense(10),
  9. ])

At this point, the network cannot possibly know the dimensions of the input layer’s weights because the input dimension remains unknown. Consequently the framework has not yet initialized any parameters. We confirm by attempting to access the parameters below.

```{.python .input} print(net.collect_params) print(net.collect_params())

  2. ```{.python .input}
  3. #@tab tensorflow
  4. [net.layers[i].get_weights() for i in range(len(net.layers))]

:begin_tab:mxnet Note that while the parameter objects exist, the input dimension to each layer is listed as -1. MXNet uses the special value -1 to indicate that the parameter dimension remains unknown. At this point, attempts to access net[0].weight.data() would trigger a runtime error stating that the network must be initialized before the parameters can be accessed. Now let us see what happens when we attempt to initialize parameters via the initialize function. :end_tab:

:begin_tab:tensorflow Note that each layer objects exist but the weights are empty. Using net.get_weights() would throw an error since the weights have not been initialized yet. :end_tab:

```{.python .input} net.initialize() net.collect_params()

  2. :begin_tab:`mxnet`
  3. As we can see, nothing has changed.
  4. When input dimensions are unknown,
  5. calls to initialize do not truly initialize the parameters.
  6. Instead, this call registers to MXNet that we wish
  7. (and optionally, according to which distribution)
  8. to initialize the parameters.
  9. :end_tab:
  11. Next let us pass data through the network
  12. to make the framework finally initialize parameters.
  14. ```{.python .input}
  15. X = np.random.uniform(size=(2, 20))
  16. net(X)
  18. net.collect_params()

```{.python .input}

@tab tensorflow

X = tf.random.uniform((2, 20)) net(X) [w.shape for w in net.get_weights()] ```

As soon as we know the input dimensionality, 20, the framework can identify the shape of the first layer’s weight matrix by plugging in the value of 20. Having recognized the first layer’s shape, the framework proceeds to the second layer, and so on through the computational graph until all shapes are known. Note that in this case, only the first layer requires deferred initialization, but the framework initializes sequentially. Once all parameter shapes are known, the framework can finally initialize the parameters.

Summary

  • Deferred initialization can be convenient, allowing the framework to infer parameter shapes automatically, making it easy to modify architectures and eliminating one common source of errors.
  • We can pass data through the model to make the framework finally initialize parameters.

Exercises

  1. What happens if you specify the input dimensions to the first layer but not to subsequent layers? Do you get immediate initialization?
  2. What happens if you specify mismatching dimensions?
  3. What would you need to do if you have input of varying dimensionality? Hint: look at the parameter tying.

:begin_tab:mxnet Discussions :end_tab:

:begin_tab:tensorflow Discussions :end_tab: