In this lab, you’ll build a library called miniflow which will be your own version of TensorFlow! TensorFlow is one of the most popular open source neural network libraries, built by the team at Google Brain just over the last few years. Through building this lab, you’ll be able to better understand backpropagation, the engine behind neural networks. We’ll finally use this library that you built to classify digits in handwriting! This will be a very hands on and interactive experience - let’s get started!

Following this lab, all other neural network type of activities will done with TensorFlow and higher-level APIs in its ecosystem. So why bother with this lab then? Good question, glad you asked!

The goal of this lab is to demystify two concepts at the heart of network networks - backpropagation and differentiable graphs. Backpropagation is the process by which we update the weight of our network over time. You may have seen it in this video in the previous lesson. Differentiable graphs are graphs where the nodes are differentiable functions. They are also very useful as a *visual aid* for understanding and calculating complicated derivatives. This is the fundamental abstraction of TensorFlow, it's a framework for creating these type of graphs. With this understanding, we will be able to create our own nodes and properly compute the derivatives. Even more importantly, we will be able to think and reason in terms of these graphs.

By the end of this lab, miniflow will be able to recognize the digit in an image of handwritten digit. This is a pretty neat result that you’ll build from scratch!

Now. Let's take our first peek under the hood ...

So neural networks sound pretty intimidating right? I mean, it's supposed to be based off our brains, and nobody knows how those things work!

Luckily, neural networks are very loosely based off our brains and the core abstractions behind how they work are actually much simpler than you would think. They look more than this:

So how does a neural network work? Let's first break up the neural network in into components, we have:

**Inputs**. This can be our data(features/labels) and weights**Functions**. The neural network itself is essentially a chain or composition of functions.**Output**. This is the final output of the neural network before it's fed into the loss function. If we're doing classification it's this will be a number signifying the class. If it's regression, this will be a number of some value (ex: house price if we're predicted house prices).**Loss Function**. This function compares our output (3) with the correct label or value and itself returns another number. This number is called the loss. Typically we'll restrict the loss to be either a positive number, in which case we minimize the value, or, a negative number, in which case we maximize. Either way we're approaching 0.

Let's say we want to minimize the loss. How do we do that?

Well, what do we have control of? Our inputs? Nope. Our inputs are the data which itself can vary significantly on the same dataset, but, we could also change our dataset entirely. We need something that sticks around, something stateful that also affects the output.

What about our weights?

Yes, That's exactly it! We can change our weights. They stay static unless we change them. Alright, now we have another question.

How do we alter our weights?

Intuitively we'd like to see what effect a weight had on the loss and make a change based on that. If it played a large role in the error then we should alter it by a large amount. If it didn't play a significant role in the error, then it's probably already set to a good value and we should, for the most part, let it be.

How can we formalize this idea?

Luckily for us, this idea is already well established in mathematical literature where it's known as **reverse-mode differentiation** or **backpropagation**. The name sounds very scary but it's actually not so bad. It essentially boils down to computing derivatives and using the chain rule. For example, say we wanted to compute the gradient of the $loss$ with respect to a weight $W^1_{kj}$. Here $W^1$ is a matrix of weights so $W^1_{kj}$ is an individual weight (number) at row $k$, column $j$ of $W^1$. Let's assume $W^1$ is an input/argument to the function $f_1$, meaning $f_1$ does some computation with $W^1$, the exact computation doesn't matter right now.

$L$ is the loss function.

$$ loss = L(predictions, labels) $$Using the chain rule the computation is:

$$ \frac{\partial L}{\partial W^1_{kj}} = \frac{\partial L}{\partial f_4} \frac{\partial f_4}{\partial f_3} \frac{\partial f_3}{\partial f_2} \frac{\partial f_2}{\partial f_1} \frac{\partial f_1}{\partial W^1_{kj}} $$You may have noticed in the above link they used the following notation:

$$ \frac {d}{dx} f(g(x)) = f'(g(x))g'(x) $$This is equivalent to:

$$ \frac {\partial f}{\partial x} = \frac {\partial f}{\partial g} \frac {\partial g} {\partial x} $$The latter notation is used when we talk about *partial derivatives*, that is, we want measure the effect a specific input had on our output. This is precisely what we're going to be doing throughout this lab so we'll use the latter notation. By the way, the $\partial$ symbol is called a *partial*.

Ok, now back to our our friend $\frac{\partial L}{\partial W^1_{kj}}$. This is mathematical speak for, "what effect did weight $W^1_{kj}$ have on the output $L$?" You might be wondering why we need to know all these other partials. Why can't we just write:

$$ \frac{\partial L}{\partial W^1_{kj}} = \frac{\partial L}{\partial f_1} \frac{\partial f_1}{\partial W^1_{kj}} $$since $W^1_{kj}$ is the input to $f_1$.

If we did that we would miss out on a wealth of information and most likely get an incorrect gradient. Remember that $f_1$ affects $f_2$ and $f_3$ affects $f_4$. Missing out on how all these intermediate functions affect each other won't do us any good and it'll only get worse the more intermediate functions we have.

So in a sense we can write:

$$ \frac{\partial L}{\partial W^1_{kj}} = \frac{\partial L}{\partial f_1} \frac{\partial f_1}{\partial W^1_{kj}} $$but just remember that:

$$ \frac{\partial L}{\partial f_1} = \frac{\partial L}{\partial f_4} \frac{\partial f_4}{\partial f_3} \frac{\partial f_3}{\partial f_2} \frac{\partial f_2}{\partial f_1} $$otherwise we'll have a bad time!

Ok, that's a lot of abstract thinking let's now take a look at a concrete example and practice taking partial derivatives.

$$
mul(x,y) = x * y
$$$$
\frac{\partial mul}{\partial x} = y \hspace{0.5in} \frac{\partial mul}{\partial y} = x
$$

Let's think about this for a bit. What we're saying here is the change of $mul$ with respect to $x$ is $y$ and vice-versa. Remember, if our derivative is with respect to $x$, then we treat $y$ as a constant.

Let's set $y = 10$. Now think about changing $x$ from 3 to 4. Then $mul(3,10) = 30$ and $mul(4, 10) = 40$. That's a change in 10 or $y$! Every time we change $x$ by 1, $mul$ changes by $y$.

Here's a new example:

$$ add(x,y) = x + y $$$$ \frac{\partial add}{\partial x} = 1 \hspace{0.5in} \frac{\partial add}{\partial y} = 1 $$Again, let's think about this. The change in $add$ with respect to $x$ is 1 and same for $y$. This means every time we change $x$ by 1, $add$ will also change by 1. This also shows $x$ and $y$ are independent of each other.

Ok, let's now use this for a simple function.

In [1]:

```
# f(x, y, z) = x * y + (x * z)
# we can split these into subexpressions
# g(x, y) = x * y
# h(x, z) = x * z
# f(x, y, z) = g(x, y) + h(x, z)
# initial values
x = 3
y = 4
z = -5
g = x * y
h = x * z
f = g + h
print(f)
```

-3

Let's take our function $f$ and apply the chain rule to compute the derivatives for $x, y, z$.

$$ \frac{\partial f}{\partial g} = 1 \hspace{0.1in} \frac{\partial f}{\partial h} = 1 \hspace{0.1in} \frac{\partial g}{\partial x} = y \hspace{0.1in} \frac{\partial g}{\partial y} = x \hspace{0.1in} \frac{\partial h}{\partial x} = z \hspace{0.1in} \frac{\partial h}{\partial z} = x $$$$ \frac{\partial f}{\partial x} = \frac{\partial f}{\partial g} \frac{\partial g}{\partial x} + \frac{\partial f}{\partial h} \frac{\partial h}{\partial x} \hspace{0.5in} \frac{\partial f}{\partial y} = \frac{\partial f}{\partial g} \frac{\partial g}{\partial y} \hspace{0.5in} \frac{\partial f}{\partial z} = \frac{\partial f}{\partial h} \frac{\partial h}{\partial z} $$$$ \frac{\partial f}{\partial x} = 1 * y + 1 * z = y + z \hspace{0.5in} \frac{\partial f}{\partial y} = 1 * x = x \hspace{0.5in} \frac{\partial f}{\partial z} = 1 * x = x $$In [2]:

```
# The above in code
x = 3
y = 4
z = -5
dfdg = 1.0
dfdh = 1.0
dgdx = y
dgdy = x
dhdx = z
dhdz = x
dfdx = dfdg * dgdx + dfdh * dhdx
dfdy = dfdg * dgdy
dfdz = dfdh * dhdz
# the output of backpropagation is the gradient
# TODO: what's the gradient?
gradient = [dfdx, dfdy, dfdz]
print(gradient) # should be [-1, 3, 3]
```

[-1.0, 3.0, 3.0]

Here's $f$ visually:

Notice the following expression, specifically the `+`

function:

Think about how $x,y,z$ flow through the graph. Both $y$ and $z$ have 1 output edge and they follow 1 path to the $f$. On the other hand, $x$ has 2 output edges and follows 2 paths to `f`

. Remember, we're calculating **the derivative of f with respect to x**. In order to do this we have to consider all the ways $x$ affects $f$ (all the paths in the graph from $x$ to $f$).

An easy way to see how many paths we have to consider for a node's derivative is to trace all the paths back from the output node to the input node. So if $f$ is the output node and $x$ is the input node, trace all the paths back from $f$ to $x$. It's not always the case that all the output edges of $x$ will lead to $f$, so we shouldn't just assume we have to consider all the output edges of $x$.

Keep these things in mind for the node implementations!

I'd like to draw attention to a few things from the previous section.

- The picture of the broken down expression and subexpressions of $f$ resembles a graph where the nodes are function applications.
- We can use of dynamic programming to make computing backpropagation efficient. Even in our simple example we see the reuse of $\frac{\partial f}{\partial g}$ and $\frac{\partial f}{\partial h}$. As our graph grows in size and complexity, it becomes much more evident how wasteful it is to recompute partials. The cornerstones of dynamic programming are
**solving a large problem through many smaller ones**and**caching**. We'll do both!

In the following exercises that you'll implement the forward and backward passes for the nodes in our graph.

You'll write your code in `miniflow.py`

(same directory), the autoreload extension will automatically reload your code when you make a change!

In [3]:

```
%load_ext autoreload
%autoreload 2
from miniflow import *
```

Implement the `Mul`

node. The `Input`

and `Add`

nodes are already provided. The `Mul`

node represents the multiplication function ($*$) and the `Add`

node the addition function ($+$). You will implement the forward and backward methods.

Let's step through the implementation of the `Input`

and `Add`

nodes to get a feel for the miniflow API.

`Input`

node¶```
class Input(Node):
def __init__(self):
# an Input node has no incoming nodes
# so we pass an empty list
Node.__init__(self, [])
# NOTE: Input node is the only node where the value
# is passed as an argument to forward().
#
# All other node implementations should get the value
# of the previous nodes from self.inbound_nodes
#
# Example:
# val0 = self.inbound_nodes[0].value
def forward(self, value):
self.value = value
def backward(self):
# An Input node has no inputs so we refer to ourself
# for the gradient
self.gradients = {self: 0}
for n in self.outbound_nodes:
self.gradients[self] += n.gradients[self]
```

The Input node is how we feed values to the rest of the nodes in the graph. We'll use Input nodes to pass the data required to train the neural network (features, labels, weights). In the case study above $x, y, z$ are Input nodes.

The Input node is a unique node since it has a slightly different **forward** method. As you can see we pass `value`

as an argument to the forward method and store it in `self.value`

. The rest of the nodes will not take an argument in the forward method but rather use the values of their inbound nodes, so don't worry too much about this subtle difference. We'll see an example of this in the Add node. The **backward** method for the Input node is a little weird because we have no inbound nodes so we just accumulate the gradient of our outbound nodes.

```
for n in self.output_nodes:
self.gradients[self] += n.gradients[self]
```

The main part to pay attention to here is `n.gradients[self]`

. Every node has a `gradients`

attribute, which is a dictionary where the key is a node and the value is the gradient of the loss (final output) with respect to that node. So what `n.gradients[self]`

is saying is get the gradient of the loss with respect to this node (Input node in this case).

`Add`

node¶```
class Add(Node):
def __init__(self, x, y):
Node.__init__(self, [x, y])
def forward(self):
# self.inbound_nodes[0] is x
# self.inbound_nodes[1] is y
self.value = self.inbound_nodes[0].value + self.inbound_nodes[1].value
def backward(self):
self.gradients = {n: 0 for n in self.inbound_nodes}
for n in self.outbound_nodes:
grad = n.gradients[self]
self.gradients[self.inbound_nodes[0]] += 1 * grad
self.gradients[self.inbound_nodes[1]] += 1 * grad
```

The Add node in the **forward** method mimics the behaviour the $+$ function. We take the values of the two inbound nodes and add them together, storing the result in `self.value`

. Ok, let's walkthrough the **backward** method line by line:

```
self.gradients = {n: 0 for n in self.inbound_nodes}
```

Here we set the gradient of the loss with respect to every inbound node to 0. We're going to calculate this value by multiplying (1) the gradient of the current node with respect to the input node with (2) the gradient of the loss with respect to the current node.

```
for n in self.outbound_nodes:
```

We need to consider the gradient for all outbound nodes.

```
grad = n.gradients[self]
```

Get the gradient of the loss with respect to the current node.

```
self.gradients[self.inbound_nodes[0]] += 1 * grad
self.gradients[self.inbound_nodes[1]] += 1 * grad
```

Remember we already computed partial derivatives of each input for the $+$ function and both ended up being 1. So 1 is the gradient of the current node with respect to the inbound node.

We multiply 1 and grad to get the final gradient result and store/accumulate it in the proper key of `self.gradients`

.

Hopefully this walkthrough has given you a feel for the miniflow API. Now it's your turn to finish the forward and backward methods of the Mul node.

- Open up miniflow.py
- Read the Q & A section at the top
- Implement Mul
- Run the code block below and see if it works

In [ ]:

```
# RUN THIS BLOCK TO SEE IF YOUR CODE WORKS PROPERLY
x, y, z = Input(), Input(), Input()
# TODO: implement Mul in miniflow.py
g = Mul(x, y)
h = Mul(x, z)
f = Add(g, h)
# DummyGrad is just here so we can pass a fake gradient backwards.
# It's just used for testing purposes.
dummy = DummyGrad(f)
# values for Input and DummyGrad nodes.
feed_dict = {x: 3, y: 4, z: -5, dummy: 0.5}
loss, grads = value_and_grad(dummy, feed_dict, (x, y, z))
# print(loss, grads)
assert loss == -3
assert grads == [-0.5, 1.5, 1.5]
```

We are now going to take our focus on how we can use differentiable graphs to compute functions for neural networks. Let's assume we have a vector of features $x$, a vector of weights $w$ and a bias scalar $b$. Then to compute output we would perform a linear transform.

$$ o = (\sum_i x_iw_i) + b $$Or more concisely expressed as a dot product:

$$ o = x^Tw + b $$What if we have multiple outputs? Say we have $n$ features and $k$ outputs, then $b$ is a vector of length $k$, $x$ is a vector of length $n$ and $w$ becomes a $n$ by $k$ matrix, which we'll call $W$ from now on (matrices notation is typically a capital letter).

$$ o = x^TW + b $$What if we now have $m$ inputs? This is a common practice to feed in more than 1 input; $m$ would be referred to as the "batch size". Then $x$, which was a vector of length $n$, becomes a matrix of size $m$ by $n$. We'll call this matrix $X$.

$$ o = XW + b $$There we have it - the famous linear transform! This on its own, though, is not all that powerful. It will only do well if the data is linearly separable.

That leads us to nonlinear activations and layer stacking. In fact, even a 2-layer neural network can approximate arbitrary functions. Pretty cool!

There is however, a difference between being able to approximate any function theoretically and actually being able to do it efficiently and effectively in practice. If it were that easy then we wouldn't need the advanced deep learning networks that you'll study later.

In this lab, though, we'll keep it relatively simple. By the end of the lab you'll be able to construct and train a neural network with the following architecture:

**USE numpy FOR THE FOLLOWING EXERCISES**.

`Linear`

Node¶These are the shapes:

- $X$ is $m$ by $n$
- $Z$ is $n$ by $p$
- $b$ has $p$ elements (row vector)
- $Z$ is $m$ by $p$

In this exercise we'll implement the `Linear`

node. This corresponds to the following function:

or more explicitly, $Z$ being the output of $f(X, W, b)$:

$$ Z_{ij} = \sum_{k=1}^n X_{ik}W_{kj} + b_j $$The latter format is very helpful when computing the derivatives. Computing the derivative of a matrix or vector can be intimidating since the computations are much more complex. But, as we've seen, if we're working with scalars the derivatives can be quite simple. The cool thing is computations with matrices and vectors are really just a lot of scalar computations!

Let's walk through an example to walk sure we understand this computation.

$$ X = \left[ \begin{array}{cc} -1 & -2 \\ -1 & -2 \end{array} \right] \hspace{0.3in} % W = \left[ \begin{array}{cc} 2 & -3 \\ 2 & -3 \end{array} \right] \hspace{0.3in} % b = \left[ \begin{array}{cc} -3 & -5 \end{array} \right] \hspace{0.3in} % Z = \left[ \begin{array}{cc} ? & ? \\ ? & ? \end{array} \right] $$So if we want to compute $Z_{11}$ then the equation comes:

$$ Z_{11} = X_{11}W_{11} + X_{12}W_{21} + b_1 = -1 * 2 + -2 * 2 + -3 = -9 $$To start out, try to work through these partials:

$$ \frac {\partial Z_{ij}} {\partial X_{ik}} \hspace{0.5in} \frac {\partial Z_{ij}} {\partial W_{kj}} \hspace{0.5in} \frac {\partial Z_{ij}} {\partial b_{j}} $$Once you have those down see if you can make any generalizations.

Additionally, it may be helpful to visualize the computation. Any duplicates $X, W, b$ nodes are just to make the visual easier, think of these duplicates as one and the same.

We'll now visualize the gradient of the loss with respect to $X_{11}$. We remove the parts of the above image that don't contribute to the gradient. There are two paths back to $X_{11}$ from $Z$. How does the number of paths change as we change the matrix sizes?

**HINT**: The `numpy.dot`

function can be used to multiply matrices

In [ ]:

```
# RUN THIS BLOCK TO SEE IF YOUR CODE WORKS PROPERLY
x_in, w_in, b_in = Input(), Input(), Input()
# TODO: implement Linear in miniflow.py
f = Linear(x_in, w_in, b_in)
dummy = DummyGrad(f)
x = np.array([[-1., -2.], [-1, -2]])
w = np.array([[2., -3], [2., -3]])
b = np.array([-3., -5])
dummy_grad = np.array([[1., 2.], [3, 4]])
feed_dict = {x_in: x, w_in: w, b_in: b, dummy: dummy_grad}
loss, grads = value_and_grad(dummy, feed_dict, (x_in, w_in, b_in))
# print(loss, grads)
assert np.allclose(loss, np.array([[-9., 4.], [-9., 4.]]))
assert np.allclose(grads[0], np.array([[-4., -4.], [-6., -6.]]))
assert np.allclose(grads[1], np.array([[-4., -6.], [-8., -12.]]))
assert np.allclose(grads[2], np.array([[4., 6.]]))
```

In [ ]:

```
# RUN THIS BLOCK TO SEE IF YOUR CODE WORKS PROPERLY
x_in = Input()
# TODO: implement Sigmoid in miniflow.py
f = Sigmoid(x_in)
dummy = DummyGrad(f)
x = np.array([-10., 0, 10])
feed_dict = {x_in: x, dummy: 0.5}
loss, grads = value_and_grad(dummy, feed_dict, [x_in])
# print(loss, grads)
assert np.allclose(loss, np.array([0., 0.5, 1.]), atol=1.e-4)
assert np.allclose(grads, np.array([0., 0.125, 0.]), atol=1.e-4)
```

`CrossEntropyWithSoftmax`

Node¶In this exercise you'll implement the `CrossEntropyWithSoftmax`

node. This corresponds to implementing the softmax and cross entropy functions.

The input to the softmax function is a vector and the output is a vector of normalized probabilities. The input could also be a matrix. In this case each row/example should be treated in isolation. Output in this case would be a matrix of the same shape.

Example:

```
x = [0.2, 1.0, 0.3]
softmax(x) # [0.2309, 0.5138, 0.2551], sum over columns is 1.
```

`numpy.sum`

function will be helpful for implementing both softmax and cross entropy loss, here's how it works.

In [ ]:

```
# RUN THIS BLOCK TO SEE IF YOUR CODE WORKS PROPERLY
import numpy as np
X = np.random.randn(3,5)
# lose the dimension we sum across
# sum across rows
print(np.sum(X, axis=0, keepdims=False).shape)
# sum across columns
print(np.sum(X, axis=1, keepdims=False).shape)
# keep the same number of dimensions
print(np.sum(X, axis=0, keepdims=True).shape)
print(np.sum(X, axis=1, keepdims=True).shape)
```

Before we dive into the math behind the cross entropy loss (CE) let's get an intuition for how it helps our neural network perform better. Let's first think about what the inputs to CE are:

- The probabilities computed from the softmax activation (what we think the output is)
- The labels (what the output actually is)

What are we doing with these inputs?

Fundamentally, we're comparing them, checking how different or similar they are. We want the output of the softmax to be as similar to the label as possible. If this is the case our loss will be low, if not it will be higher. Either way backpropagation will make the appropriate adjustments.

At this point it still may not be clear what is actually being compared. So what is being compared?

Probability distributions! More precisely categorical distributions, where the result can be one of $k$ possible outcomes. Remember the output from the softmax is a probability distribution (that's why it's important we make sure the values sum to 1). The label is a categorical distribution where $k-1$ values are 0 and one value is 1 (still adds up to 1).

This might be strange, but, if I put an apple in front of you, would you say "That's an apple 60% of the time, a banana 10% of the time, and 30% of the time a pineapple". I hope not! You would be 100% certain that's an apple, after all, it can only be one of those things. The former though, may be the softmax output the neural network. In that case the CE would be computed by comparing these two vectors $[0.6, 0.10, 0.30]$ and $[1, 0, 0]$. As the neural network is trained the first vector will look more and more like the second. Alright, time for some math.

$$ cross\_entropy\_loss = \frac {1} {n} -\sum_x P(x) * log(Q(x)) $$$P$ is the true distribution (labels) and $Q$ is the distribution of the neural network softmax. We sum over all the data, $x$ is an individual example, $n$ the number of examples. Let's walk through the example above.

In [ ]:

```
# 60% apple, 10% banana, 25% pineapple ... (crazy or maybe quantum world)
Qx = np.array([0.6, 0.1, 0.30])
# 100% apple
Px = np.array([1., 0, 0])
log_Qx = np.log(Qx)
print(log_Qx)
loss = -np.sum(Px * log_Qx)
print(loss) # only the value multiplied by 1 effects the loss!
# TODO: repeat this below
# we could simplify this to
-log_Qx[0] # 0 is the index where Px is 1
# Feel free to play around with Qx and Px to get a feel for the loss.
```

You'll implement the latter version, where we just index `log_Qx`

. This allows us to represent the label as just 1 number $[0, k-1]$, rather than a vector of $k$ numbers.

Here's the math version:

- $X$ is a matrix from the output of a softmax activation. Each row is a categorical distribution.
- $y$ is a vector of labels $[0, k-1]$, $k$ being the number of classes.
- $n$ is the number of rows of $X$.

Ok, but how will this loss encourage our model to classify correctly?

There are 2 key pieces of information here:

- $probs$ contains values between 0 and 1
- $log(0) = -inf$ and $log(1) = 0$; the possible log values are either negative or 0.

Clearly we'd like the probability of the index of the correct label to be 1 or close to it and if it's close to 0 we'll be heavily penalized and our will loss to shoot up. Note the negative sign sets the problem up nicely for minimizing the loss.

Let's look at some visuals, we're going to stay with the fruit classifier example above. In the following graphs the $x$ values are the input to the softmax function, $z$ values the output of the softmax function which are fed into the cross entropy loss function. So $z_0 = 0.6$, $z_1 = 0.1$, and $z_2 = 0.3$. The label distribution is $[1, 0, 0]$ but remember we can simplify this to just use the index where the probability is 1, so our label is 0.

Notice each $x_i$ is connected to each $z_i$, this is because each $x_i$ plays a role in computing each $z_i$. Hmmm, that's a lot to keep track of for the backward pass.

Remember back when we discovered only one value from the softmax output will effect the loss? Here we see the consequences of that. The only derivative that is not 0, is the derivative of the value that effected the loss, in this case the label was 0 so it corresponds to the $z_0$ node. In addition, we no longer have to consider the gradient of any softmax output node besides $z_0$, this greatly simplifies $\frac {\partial L}{\partial x_i}$!

In [ ]:

```
# RUN THIS BLOCK TO SEE IF YOUR CODE WORKS PROPERLY
x_in = Input()
y_in = Input()
# TODO: implement CrossEntropyWithSoftmax in miniflow.py
# No DummyGrad this time! Guaranteed to be last node in our graph.
f = CrossEntropyWithSoftmax(x_in, y_in)
# values to feed input nodes
x = np.array([[0.5, 1., 1.5]])
# in this example we have a choice 3 classes (x has 3 columns)
# so our label can one of 0,1,2. It's 1 in this case.
y = np.array([1])
feed_dict = {x_in: x, y_in: y}
loss, grads = value_and_grad(f, feed_dict, wrt=[x_in])
# print(loss, grads)
# Look at the expected value of softmax(x) and the expected value of the gradient with
# respect to x
assert np.allclose(f._softmax(x), [[0.1863, 0.3072, 0.5064]], atol=1.e-4)
assert np.allclose(loss, 1.1802, atol=1.e-4)
assert np.allclose(grads, np.array([[0.1863, -0.6928, 0.5064]]), atol=1.e-4)
```

At this point you should have all the nodes implemented and working correctly. Computing those weight gradients is a breeze! Now that we have the gradients what do we do with them?

As it turns out the gradient is analogous to the **steepest ascent direction**. Let's imagine that we are our neural network and we're in a park - not just any park though, a hilly park. We also know that we perform our best when we're on the highest hill, so let's go there!

There are a couple of issues though ... we are:

- Blindfolded
- Dropped randomly somewhere in the park (random weights!). We'd be hard pressed to find the highest hill in our current condition.

Luckily for us, we have a talking bird by our side. Her name is Gradient and she's very good at informing us which direction causes us to ascend the hill the fastest. Unfortunately for Gradient, her vision isn't the greatest and she can only see the local area. It might be the case we get to the top of a hill, but not the highest one.

Typically we're minimizing a function, not maximizing. The above analogy still holds, we're just descending instead of ascending (searching for lowest valley vs. highest hill). Making this adjustment is very simple, just put a negative sign on the gradient.

There's one more thing to think about, we know what direction to step in but how large of a step should we take? Too small a step and it could take a very long time to converge, and too large a step could overshoot the target cause divergence. In practice the most common step sizes are 1e-3 and 1e-4, sometimes 1e-2 and 1e-1 work well too. Note: the *step size* is more commonly known as the *learning rate*.

Here's roughly what SGD looks like with miniflow.

```
f = ... # output node
wrt = [...] # weight input nodes
W = ... # weight for Linear node
b = ... # bias for Linear node
while True:
feed_dict = {...} # new batch of data
loss, grad = value_and_grad(f, feed_dict, wrt)
# get the grad for W and b
dW = grad[...]
db = grad[...]
# descending in the direction of the gradient
W[:] -= step_size * dW
b[:] -= step_size * db
```

You now have all the pieces in place, all that's left to do is fit them together like legos.

TODO: lego picture

Your task is now to classify handwritten digits from the MNIST dataset.

In [ ]:

```
# load MNIST
from tensorflow.examples.tutorials.mnist import input_data
mnist = input_data.read_data_sets("MNIST_data/", one_hot=False)
```

In [ ]:

```
# getting input and label data
X_batch, y_batch = mnist.train.next_batch(128)
print(X_batch.shape, y_batch.shape)
```

In [ ]:

```
X_val = mnist.validation.images
y_val = mnist.validation.labels.astype(np.int8)
X_test = mnist.test.images
y_test = mnist.test.labels.astype(np.int8)
```

You should hit above 90% accuracy on even a 1-layer neural network.

In [ ]:

```
# TODO: initialize weights
# TODO: define architecture, you can use the architecture in the miniflow graph shown earlier
```

In [ ]:

```
# TODO: set step size and batch size
step_size = ...
batch_size = ...
for i in range(10000):
X_batch, y_batch = mnist.train.next_batch(batch_size)
y_batch = y_batch.astype(np.int8)
# TODO: get the loss and grad
loss, grad = value_and_grad(...)
if i % 1000 == 0:
print("Iteration {}".format(i))
print("Loss = {}".format(loss))
# TODO: get the accuracy of the validation dataset
# similar to value_and_grad except there's no wrt list
acc = accuracy(...)
print("Validation Accuracy = {}".format(acc))
print('----------------')
# TODO: SGD updates with gradient
# SGD code goes here ...
# TODO: get the accuracy of the testing dataset
acc = accuracy(...)
print('----------------')
print("Testing Accuracy = {}".format(acc))
```

In this lab you created a library, miniflow, for computing differentiable graphs. Using miniflow, you created a neural network that can classify handwritten digits with high accuracy. Not too shabby! Hopefully you now have a solid grasp of differentiable graphs and backpropagation.

You probably also noticed how tedious all this work can be! It would be nice if someone already had written all this code for us, made it really fast, usable on GPUs, mobile devices and had a gigantic ecosystem around it so we can be assured it'll just get better and better ... Oh wait! It's not a fantasy.

All of that is true and it's called Tensorflow, developed by the fine folks at Google and now a thriving open source project! In the future you'll use TensorFlow, but you can always come back to miniflow if you've grown attached :-)